> The purpose is to dump the contents of a Python extension type to disk
> as binary data using C's fwrite() function.
This isn't really possible anymore - the Python IO library has stopped
using stdio. There are a couple of alternatives:
1. don't use fwrite(3) to write the binary data, but inste
En Fri, 29 May 2009 23:24:32 -0300, Benjamin Peterson
escribió:
Gabriel Genellina yahoo.com.ar> writes:
But you have to import the io module first, don't you? That's not
usually
necesary for most built in types -- e.g. PyFloat_Check just checks for a
float object.
Well, in 3.x, file is
Gabriel Genellina yahoo.com.ar> writes:
> But you have to import the io module first, don't you? That's not usually
> necesary for most built in types -- e.g. PyFloat_Check just checks for a
> float object.
Well, in 3.x, file is not longer a builtin type.
--
http://mail.python.org/mailma
En Fri, 29 May 2009 08:48:26 -0300, Benjamin Peterson
escribió:
Joachim Dahl gmail.com> writes:
How do I perform type checking for such an object in the extension
module,
and how do I extract a FILE * object from it? I browsed the C API
documentation, but
couldn't find an answer.
You u
En Fri, 29 May 2009 06:52:15 -0300, Joachim Dahl
escribió:
In Python2.x, I used PyFile_Check(obj) to check if a parameter was a
file object.
Now, in Python3.0 the same object (obtained as open('file.bin','wb'))
is an
io.BufferedWriter object.
How do I perform type checking for such an objec
Joachim Dahl gmail.com> writes:
>
> How do I perform type checking for such an object in the extension
> module,
> and how do I extract a FILE * object from it? I browsed the C API
> documentation, but
> couldn't find an answer.
You use PyObject_IsInstance to test if the object is an instance
In Python2.x, I used PyFile_Check(obj) to check if a parameter was a
file object.
Now, in Python3.0 the same object (obtained as open('file.bin','wb'))
is an
io.BufferedWriter object.
How do I perform type checking for such an object in the extension
module,
and how do I extract a FILE * object f
