Re: my parser.py isn't imported

On Aug 27, 7:33 pm, Lawrence D'Oliveiro <[EMAIL PROTECTED] central.gen.new_zealand> wrote: > In message <[EMAIL PROTECTED]>, Torsten Bronger wrote: > > > So I'd like to know a means to tell *explicitly* what I want to > > import. Maybe I could use the imp module but that's ugly. > > That seems to

Re: my parser.py isn't imported

Hallöchen! John Machin writes: > Torsten Bronger wrote: > >> I have a module parser.py in the same directory as the main >> module. In the main module, I import "parser". On Linux, this >> works as expected, however on Windows, it imports the stdlib >> parser module. sys.path[0] points to the

Re: my parser.py isn't imported

In message <[EMAIL PROTECTED]>, Torsten Bronger wrote: > So I'd like to know a means to tell *explicitly* what I want to > import. Maybe I could use the imp module but that's ugly. That seems to be the standard Python-provided way to explicitly import the file you want from the place you want.

Re: my parser.py isn't imported

Hallöchen! John Machin writes: > On Aug 27, 1:36 am, Torsten Bronger <[EMAIL PROTECTED]> > wrote: > >> I have a module parser.py in the same directory as the main >> module. In the main module, I import "parser". On Linux, this >> works as expected, however on Windows, it imports the stdlib >>

Re: my parser.py isn't imported

On Aug 27, 1:36 am, Torsten Bronger <[EMAIL PROTECTED]> wrote: > Hallöchen! > > I have a module parser.py in the same directory as the main module. > In the main module, I import "parser". On Linux, this works as > expected, however on Windows, it imports the stdlib parser module. > sys.path[0] po

my parser.py isn't imported

Hallöchen! I have a module parser.py in the same directory as the main module. In the main module, I import "parser". On Linux, this works as expected, however on Windows, it imports the stdlib parser module. sys.path[0] points to the directory of my parser.py in both cases. What went wrong here?