Just FYI in that case :

E:\Documents and Settings\Nico>python
ActivePython 2.4.1 Build 247 (ActiveState Corp.) based on
Python 2.4.1 (#65, Jun 20 2005, 17:01:55) [MSC v.1310 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import imp
>>> imp.find_module('',None)
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named
>>>

2006/1/13, Jim Gallacher <[EMAIL PROTECTED]>:
> Graham Dumpleton wrote:
> > Jim Gallacher wrote ..
> >
> >>It's a strange one. When I move site-packages/PIL to
> >>site-packages/PIL.bak (leaving PIL.pth as is) and run the tests I get
> >>the same output as Graham and Nicolas. I'm just going to ignore this for
> >>the time being and go with a refactored unit test.
> >
> >
> > I am making a guess that it is because of the following:
> >
> > ~ [510]$ touch .py
> > ~ [511]$ python
> > Python 2.3 (#1, Sep 13 2003, 00:49:11)
> > [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
> > Type "help", "copyright", "credits" or "license" for more information.
> >
> >>>>import imp
> >>>>imp.find_module('',None)
> >
> > (<open file '.py', mode 'U' at 0x602e0>, '.py', ('.py', 'U', 1))
> >
> > Ie., look for a ".py" file in PIL.
>
> There is no .py in site-packages/PIL/ but it does look like the problem
> is PIL related.
>
>  >>> import imp
>  >>> imp.find_module('',None)
> (None, '/usr/lib/python2.3/site-packages/PIL/', ('', '', 5))
>
> I've changed the unit test to avoid the problem so I don't think it's
> worth wasting any more time.
>
> Jim
>
>
>

Reply via email to