In article <[EMAIL PROTECTED]>,
Steve Holden <[EMAIL PROTECTED]> wrote:
> Just to make things simpler, and (;-) to appeal to a wider audience,
> here is a program that doesn't use database at all (it loads the entire
> standard library into a dict) and still shows the error.
>
> What *I* would
Steve Holden wrote:
Peter Otten wrote:
Steve Holden wrote:
This is even stranger: it makes it if I import the module a second time:
[second import seems to succeed]
Maybe you are experiencing some version confusion? What you describe
looks
much like the normal Python 2.3 behaviour (with no impor
Peter Otten wrote:
Steve Holden wrote:
This is even stranger: it makes it if I import the module a second time:
[second import seems to succeed]
Maybe you are experiencing some version confusion? What you describe looks
much like the normal Python 2.3 behaviour (with no import hook involved)
wher
Steve Holden wrote:
> This is even stranger: it makes it if I import the module a second time:
[second import seems to succeed]
Maybe you are experiencing some version confusion? What you describe looks
much like the normal Python 2.3 behaviour (with no import hook involved)
whereas you seem to
This is even stranger: it makes it if I import the module a second time:
import dbimp as dbimp
import sys
if __name__ == "__main__":
dbimp.install()
#k = sys.modules.keys()
#k.sort()
#for kk in k:
#print kk
#import bsddb.db
import a.b.c.d
import smtplib
import f
