Command-line option equiv of PYTHONPATH

[Rajesh]

Hi,

The '-I<path>' option adds the path to the list of directories that
contains modules that can be included in a script. I can use it as "#!/
usr/bin/perl -I<path_to_my_modules>" thereby not asking the user of
the script to set the <path_to_my_modulesin their environment.

Is there any equivalent command-line option to the python binary or a
command-line version of PYTHONPATH?

Regards
Rajesh

[James Stroud]

Rajesh wrote:

Hi,

The '-I<path>' option adds the path to the list of directories that
contains modules that can be included in a script. I can use it as "#!/
usr/bin/perl -I<path_to_my_modules>" thereby not asking the user of
the script to set the <path_to_my_modulesin their environment.

Is there any equivalent command-line option to the python binary or a
command-line version of PYTHONPATH?

Regards
Rajesh

Why not just modify sys.path within the actual script?

James

[=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=]

The '-I<path>' option adds the path to the list of directories that

contains modules that can be included in a script. I can use it as "#!/
usr/bin/perl -I<path_to_my_modules>" thereby not asking the user of
the script to set the <path_to_my_modulesin their environment.

Is there any equivalent command-line option to the python binary or a
command-line version of PYTHONPATH?

To rephrase James Stroud's remark: The equivalent to

#/usr/bin/perl -I<path_to_my_modules>
TEXT

is

#/usr/bin/python
import sys
sys.path.append(path_to_my_modules)
TEXT

HTH,
Martin

[Antoon Pardon]

On 2007-04-27, James Stroud <js*****@mbi.ucla.eduwrote:

Rajesh wrote:

>Hi,

The '-I<path>' option adds the path to the list of directories that
contains modules that can be included in a script. I can use it as "#!/
usr/bin/perl -I<path_to_my_modules>" thereby not asking the user of
the script to set the <path_to_my_modulesin their environment.

Is there any equivalent command-line option to the python binary or a
command-line version of PYTHONPATH?

Regards
Rajesh

Why not just modify sys.path within the actual script?

Maybe because he has multiple versions of modules he wants to test his
script against.

--
Antoon Pardon

[Harry George]

Antoon Pardon <ap*****@forel.vub.ac.bewrites:

On 2007-04-27, James Stroud <js*****@mbi.ucla.eduwrote:

Rajesh wrote:

Hi,

The '-I<path>' option adds the path to the list of directories that
contains modules that can be included in a script. I can use it as "#!/
usr/bin/perl -I<path_to_my_modules>" thereby not asking the user of
the script to set the <path_to_my_modulesin their environment.

Is there any equivalent command-line option to the python binary or a
command-line version of PYTHONPATH?

Regards
Rajesh

Why not just modify sys.path within the actual script?

Maybe because he has multiple versions of modules he wants to test his
script against.

--
Antoon Pardon

Here are some approaches we've used:

1. Write a small script which sets PYTHONPATH and then calls the app.
Make a different script for each setup you need.

2. Use a small script to set a couple of envvars, which in turn are
used to find the right config file, which has all the config
decisions you want.

archtool_path= os.getenv('ARCHTOOL_PATH')
archtool_cfg = os.getenv('ARCHTOOL_CFG')
sys.path.insert(0,archtool_path)
import archtool
exec "import archtool.%s as cfg" % archtool_cfg
--
Harry George
PLM Engineering Architecture

[=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=]

>Why not just modify sys.path within the actual script?

Maybe because he has multiple versions of modules he wants to test his
script against.

See the original post: 'I can use it as "#!/usr/bin/perl
-I<path_to_my_modules>"' so clearly his intention is modify
the script.

Martin