Peter Hansen schrieb:
> Peter Maas wrote:
>> But sitecustomize.py changes the Python installation, doesn't it?
>> This wouldn't be an advantage over putting a .pth file into
>> .../site-packages.
>
>
> You can have a local sitecustomize.py in the current directory, which
> wouldn't change the Py
Michael Ekstrand schrieb:
> If top/ is the working directory for your Python interpreter, the
> problem is solved automatically. Python puts the current working
> directory in the default search path. So, if you run
IIS sets the the site path as working directory. So I would probably
have to chang
Peter Maas wrote:
> Peter Hansen schrieb:
>> generally such non-standard sys.path and .pth manipulations are best
>> handled by a sitecustomize.py file, possibly which makes its own calls
>> to site.addsitedir() and such. Try "help(site)" for more.
>
> But sitecustomize.py changes the Python in
On Wed, 31 Aug 2005 15:07:41 +0200
Peter Maas <[EMAIL PROTECTED]> wrote:
> I want a tree
>
> top/
> install.py
> sub1/
> __init__.py
> mod1.py
> sub2/
> mod2.py
>
> where I can do "from sub1 import mod1" in mod2.py no matter what the
> absolute path of to
Peter Hansen schrieb:
> Not sure from the above description exactly what it is you want,
I want a tree
top/
install.py
sub1/
__init__.py
mod1.py
sub2/
mod2.py
where I can do "from sub1 import mod1" in mod2.py no matter what the
absolute path of top is. T
Peter Maas wrote:
> My goal is to have the top level of a directory tree in the Python
> path without touching anything outside the directory. I tried to
> create .pth files with the top level path in every subdirectory
> but this doesn't work despite working directory being part of the
> Python pa
My goal is to have the top level of a directory tree in the Python
path without touching anything outside the directory. I tried to
create .pth files with the top level path in every subdirectory
but this doesn't work despite working directory being part of the
Python path.
Creating the pth file i
