Lorenz Quack <d...@amberfisharts.com> added the comment:

I thought that the CamelCase C-functions like PyUnicode_AsUnicode would check 
for errors like this and if you don't want error checking you can use the 
capitalized versions like PyUnicode_AS_UNICODE.
I just looked at the code for PyFloat_AsDouble and it checks for NULL pointers. 
so does PyInt_AsLong. 
OTOH, PyString_As<whatever> does not.
I didn't check on any other types.

So if it is not considered a bug then I just want to point out the 
inconsistency.

IMHO, the C-API documentation lacks information on how it behaves in error 
conditions (this might be a bit over generalized). Would there be interest in 
documentation patches in these cases or are developers expected to look at the 
actual source code for this kind of information?

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8113>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to