This is not a proper reply in terms of e-mail but I registered just a second
ago just to write this post. So, here goes, replying to Frederik's message from
Thu Apr 08 15:01:06 2010:
Are you using some virtual env thing that might move modules around,
btw? I tried messing with the path to see
2010/4/18 Łukasz Langa luk...@langa.pl:
This is not a proper reply in terms of e-mail but I registered just a second
ago just to write this post. So, here goes, replying to Frederik's message
from Thu Apr 08 15:01:06 2010:
Are you using some virtual env thing that might move modules around,
Fredrik Lundh fred...@pythonware.com wrote:
The error should only occur if the C module's initialization function
is called twice. That shouldn't happen under normal use of Python
(and if it happens anyway, it invariably results in resource leaks for
many modules, and potentially also more
Fredrik Lundh fred...@pythonware.com wrote:
Are you using some virtual env thing that might move modules around,
btw? I tried messing with the path to see if I could trick Python
into importing the same thing twice on Windows, but failed under 2.6.
No, but I am doing something somewhat
The idea is that add_item should only be called once for each mode
(see ImagingAccessInit). What did you do to trick Python into calling
the module initializer multiple times?
/F
On Mon, Apr 5, 2010 at 4:41 AM, Bill Janssen jans...@parc.com wrote:
Seems to me that in libImaging,
Fredrik Lundh fred...@pythonware.com wrote:
The idea is that add_item should only be called once for each mode
(see ImagingAccessInit). What did you do to trick Python into calling
the module initializer multiple times?
I was using epydoc and docutils 0.5 to build my documentation. Epydoc
The error should only occur if the C module's initialization function
is called twice. That shouldn't happen under normal use of Python
(and if it happens anyway, it invariably results in resource leaks for
many modules, and potentially also more serious issues -- the C module
interface doesn't
Are you using some virtual env thing that might move modules around,
btw? I tried messing with the path to see if I could trick Python
into importing the same thing twice on Windows, but failed under 2.6.
/F
On Thu, Apr 8, 2010 at 9:06 PM, Fredrik Lundh fred...@pythonware.com wrote:
The error
Seems to me that in libImaging, Access.c:add_item should really read
static ImagingAccess
add_item(const char* mode)
{
UINT32 i = hash(mode);
/* printf(hash %s = %d\n, mode, i); */
if (access_table[i].mode (strcmp(mode, access_table[i].mode) != 0)) {
fprintf(stderr,
