[ZODB-Dev] _PyImport_FixupExtension: module ZODB.TimeStamp not loaded

Christian Reis kiko@async.com.br
Mon, 7 Oct 2002 12:18:09 -0300


On Sun, Oct 06, 2002 at 07:46:51AM -0400, Guido van Rossum wrote:
> Does it also do this with Python 2.1.3?  I've tested with 2.1.3, 2.2
> and 2.3, and I didn't see this.

You were right. It's a problem only with 2.1.1. Now what?

blackjesus% python2.1.1
Python 2.1.1 (#5, Aug 23 2001, 01:38:34) 
[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import ZODB
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/local/lib/python2.1/site-packages/ZODB/__init__.py", line 18, in ?
    import cPersistence, Persistence
SystemError: _PyImport_FixupExtension: module ZODB.TimeStamp not loaded
>>> 

blackjesus% ./python2.1.3 
Python 2.1.3 (#5, Oct  7 2002, 12:14:14) 
[GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import ZODB
>>> 

> I made a change in cPersistence.c: PyImport_Import() is now called
> with ZODB.TimeStamp rather than TimeStamp as the argument, to avoid
> relative imports from inside extensions, which doesn't work when
> __import__ is redefined in Python -- this made it impossible to use
> pychecker.

Well, you can release-note the change or hack in a workaround. I don't
care myself, but maybe some other users of ZODB don't want to upgrade
Python?

> But I've not seen your SystemError.

And yet, it exists :)

Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL