Saving parameters between Python applications?

[Stodge]

I'm trying to do the following. I have a Python application that is
run:

python app1.py --location=c:\tes t1

What I want to do is save the location parameter, so I can then do (in
the same window):

python app2.py

And have app2.py automatically have access to the value of "location".

Now, the difficult part is, that in another window I want to do:

python app1.py --location=c:\tes t2
python app2.py

And have app2.py automatically get c:\test2 as the location. So the
two windows (consoles) are isolated from each other.

I thought I could use os.environ, but that doesn't save the variable
for applications that are run afterwards in the same window.

Any suggestions?

Thanks

[Sebastian Bassi]

On 9/16/07, Stodge <st****@gmail.c omwrote:

python app1.py --location=c:\tes t1
What I want to do is save the location parameter, so I can then do (in
the same window):
python app2.py
And have app2.py automatically have access to the value of "location".

Do app1.py to save a pickle of the value you want app2 to read.

--
Sebastián Bassi (ã‚»ãƒ�ステ゠£ã‚¢ãƒ³). Diplomado en Ciencia y TecnologÃ*a.
Curso Biologia molecular para programadores: http://tinyurl.com/2vv8w6
GPG Fingerprint: 9470 0980 620D ABFC BE63 A4A4 A3DE C97D 8422 D43D

[Stodge]

Good idea, but I can't guarantee that the two scripts will be run from
the same directory - so where to store the pickle?

On Sep 16, 5:25 pm, "Sebastian Bassi" <sba...@clubdel arazon.org>
wrote:

On 9/16/07, Stodge <sto...@gmail.c omwrote:

python app1.py --location=c:\tes t1
What I want to do is save the location parameter, so I can then do (in
the same window):
python app2.py
And have app2.py automatically have access to the value of "location".

Do app1.py to save a pickle of the value you want app2 to read.

--
Sebastián Bassi ( ). Diplomado en Ciencia y Tecnología.
Curso Biologia molecular para programadores:http://tinyurl.com/2vv8w6
GPG Fingerprint: 9470 0980 620D ABFC BE63 A4A4 A3DE C97D 8422 D43D

[Sebastian Bassi]

On 9/17/07, Stodge <st****@gmail.c omwrote:

Good idea, but I can't guarantee that the two scripts will be run from
the same directory - so where to store the pickle?

It doesn't matter if is the same directory or not, as long as both
programs has access to the pickle file (one program should have write
access and the other program should have at least read access).

--
Sebastián Bassi (ã‚»ãƒ�ステ゠£ã‚¢ãƒ³). Diplomado en Ciencia y TecnologÃ*a.
Curso Biologia molecular para programadores: http://tinyurl.com/2vv8w6
GPG Fingerprint: 9470 0980 620D ABFC BE63 A4A4 A3DE C97D 8422 D43D

[Laurent Pointal]

Stodge a écrit :

I'm trying to do the following. I have a Python application that is
run:

python app1.py --location=c:\tes t1

What I want to do is save the location parameter, so I can then do (in
the same window):

python app2.py

And have app2.py automatically have access to the value of "location".

Now, the difficult part is, that in another window I want to do:

python app1.py --location=c:\tes t2
python app2.py

And have app2.py automatically get c:\test2 as the location. So the
two windows (consoles) are isolated from each other.

I thought I could use os.environ, but that doesn't save the variable
for applications that are run afterwards in the same window.

Any suggestions?

May use simple file in known place:
$HOME/.myprefs
$HOME/.conf/myprefs

Or host specific configuration API:
WindowsRegistry HKEY_CURRENT_US ER\Software\MyS ociety\MyApp\my prefs
See os.getenv, and _winreg Windows specific module.
See also standard ConfigParser module
Hope you know how to read/write files.

[Bruno Desthuilliers]

Stodge a écrit :

I'm trying to do the following. I have a Python application that is
run:

python app1.py --location=c:\tes t1

What I want to do is save the location parameter, so I can then do (in
the same window):

python app2.py

And have app2.py automatically have access to the value of "location".

Now, the difficult part is, that in another window I want to do:

python app1.py --location=c:\tes t2
python app2.py

And have app2.py automatically get c:\test2 as the location. So the
two windows (consoles) are isolated from each other.

I thought I could use os.environ, but that doesn't save the variable
for applications that are run afterwards in the same window.

Any suggestions?

Yes : pass the same arg to both app1.py and app2.py !-)

Braindead, I know, but still the simplest solution.

[Stodge]

You're probably right!

Thanks all. :)

On Sep 17, 10:15 am, Bruno Desthuilliers <bruno.
42.desthuilli.. [e-mail] ro.oops.comwrot e:

Stodge a écrit :

I'm trying to do the following. I have a Python application that is
run:

python app1.py --location=c:\tes t1

What I want to do is save the location parameter, so I can then do (in
the same window):

python app2.py

And have app2.py automatically have access to the value of "location".

Now, the difficult part is, that in another window I want to do:

python app1.py --location=c:\tes t2
python app2.py

And have app2.py automatically get c:\test2 as the location. So the
two windows (consoles) are isolated from each other.

I thought I could use os.environ, but that doesn't save the variable
for applications that are run afterwards in the same window.

Any suggestions?

Yes : pass the same arg to both app1.py and app2.py !-)

Braindead, I know, but still the simplest solution.

[bryanjugglercryptographer]

On Sep 17, 6:39 am, Laurent Pointal

May use simple file in known place:
$HOME/.myprefs
$HOME/.conf/myprefs

Or host specific configuration API:
WindowsRegistry HKEY_CURRENT_US ER\Software\MyS ociety\MyApp\my prefs

See os.getenv, and _winreg Windows specific module.
See also standard ConfigParser module

Also, os.path offers expanduser(). The following is reasonably
portable:

import os

user_home_dir = os.path.expandu ser("~")
--
--Bryan

[Stodge]

os.path.expandu ser isn't an option; I need each console/window to
maintain different values which I wouldn't get from saving to a user's
home directory. Unless I used a different file for each console/window
but that just gets me into the same situation I'm already in. I think
the only option is to set environment variables using another script.
I'm really surprised and disapponited by this.

One option I thought of but haven't investigated, is the ability to
get the parent (i.e. console's) process id and use that to create a
file somewhere. Not sure if this is even possible.

On Sep 17, 4:29 pm, bryanjugglercry ptograp...@yaho o.com wrote:

On Sep 17, 6:39 am, Laurent Pointal

May use simple file in known place:
$HOME/.myprefs
$HOME/.conf/myprefs

Or host specific configuration API:
WindowsRegistry HKEY_CURRENT_US ER\Software\MyS ociety\MyApp\my prefs

See os.getenv, and _winreg Windows specific module.
See also standard ConfigParser module

Also, os.path offers expanduser(). The following is reasonably
portable:

import os

user_home_dir = os.path.expandu ser("~")

--
--Bryan

[Bruno Desthuilliers]

Stodge a écrit :

os.path.expandu ser isn't an option; I need each console/window to
maintain different values which I wouldn't get from saving to a user's
home directory. Unless I used a different file for each console/window
but that just gets me into the same situation I'm already in. I think
the only option is to set environment variables using another script.
I'm really surprised and disapponited by this.

Note that it's *not* a Python issue. You'd have the same problem with
any other language.