Thomas Heller wrote: > Can anyone explain why calling this code in a C extension > > static PyObject * > test(PyObject *self, PyObject *arg) > { > PyErr_SetString(PyExc_UnicodeDecodeError, "blah blah"); > return NULL; > } > > PyMethodDef module_methods[] = { > {"test", test, METH_NOARGS}, > {NULL, NULL} > }; > > > does this (same in 2.3.4, and 2.4 current CVS): > > >>>>from somewhere import test >>>>test() > > Traceback (most recent call last): > File "<stdin>", line 1, in ? > TypeError: function takes exactly 5 arguments (1 given) > See Python/exceptions.c: PyObject * PyUnicodeDecodeError_Create( const char *encoding, const char *object, int length, int start, int end, const char *reason) { return PyObject_CallFunction(PyExc_UnicodeDecodeError, "ss#iis", encoding, object, length, start, end, reason); } This exception is thrown by codecs that want to signal a decoding error. It includes the context of the problem as well as the reason string. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Sep 15 2004) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4