Francesco Bochicchio wrote:
[...]
> AFAIK, PYTHONPATH only works for the imported modules. For the main
> module, you have to do give the full path.
> OR you could try out the new flag -m, which allows to run directly a
> module from the standard library and - I guess - also user modules if
> PYTHO
Morgul Banner Bearer wrote:
> Hi Everybody,
>
> I was using the O'Reilly book from 1999 to look into Python and ran
> into a problem with
> the use of Pythonpath.
>
> I have Python installed under c:\python26.
> I have the module "Brian.py" that i want to run installed under c
> \python26\work
>
> In Windows Vista, I have set an environment variable "Pythonpath"
> equal to c:\python26\work
> (by using the "My computer", "Properties", "Advanced", "Environment
> Variables".
I always thought pythonpath was only for imports, try adding the
location to the regular path variable.
Andrew
--
http
On Sun, 04 Jan 2009 04:56:51 -0800, Morgul Banner Bearer wrote:
> Hi Everybody,
>
...
>
>
> The behaviour of the program is as follows :
> In a Dos Box, the program executes nicely when i type :
> "c\python26>python c:\python26\work\brian.py".
>
> Now i understand that- because I set the Pytho
Hi Everybody,
I was using the O'Reilly book from 1999 to look into Python and ran
into a problem with
the use of Pythonpath.
I have Python installed under c:\python26.
I have the module "Brian.py" that i want to run installed under c
\python26\work
In Windows Vista, I have set an environment var
