the PYCObject's destructor, the pointer is for the constant
"foo", not the memory I initially allocated.
I only posted this to help people searching, sorry for the noise.
Tom Conneely
--
http://mail.python.org/mailman/listinfo/python-list
d; some will simply set
> it aside for the next allocation.
> Another possible (and related) issue is memory fragmentation. Again, it
> depends on the memory allocator.
Yes, I know that's the case but the "freed" memory should be used for
the
next allocation, or atleas
I'm attempting to write a library for reading data via USB from a
device and processing the data to display graphs. I have already
implemented parts of this code as pure python, as a proof of concept
but I have now moved on to implementing the functions in a C
extension.
My original plan was to ha
