On Mar 6, 4:53 pm, Chris Rebert <c...@rebertia.com> wrote: > On Sat, Mar 6, 2010 at 4:42 PM, Isaac Gouy <igo...@yahoo.com> wrote: > > On Mar 6, 4:02 pm, Chris Rebert <c...@rebertia.com> wrote: > >> On Sat, Mar 6, 2010 at 3:53 PM, Isaac Gouy <igo...@yahoo.com> wrote: > >> > At the command prompt: > > >> > python b.py 8 > >> > works fine on both XP and Vista > > >> > python b.python 8 > >> > works on XP (and Linux) > > >> > but on Vista > > >> > python b.python 8 > > >> > ImportError: No module named b > > >> > ? > > >> Code please. > > > It's the same code in both cases, I simply renamed "b.python" as > > "b.py" as a test. > > The code in b.py matters. I /suspect/ it's importing itself somehow > (probably indirectly), and Python doesn't look for ".python" files > when importing, so it fails with an ImportError. But since you haven't > shown the code, I can only guess.
Yes the code in b.py matters. Why it matters is that there was another difference between XP and Vista - the XP machine was single core but the Vista machine was multi core - and the code behaves differently in each case. Thanks. -- http://mail.python.org/mailman/listinfo/python-list
