programmaticall y manipulation environment variables of the callingshell

[Maxim Veksler]

Hello list,

I'm trying to write a python script that would allow me to manipulate
shell variables of the calling shell. I'm trying to write some logic
that would know to add LD_LIBRARY_PATH to the users environment.

In bash this is done with "export", can I do this with python? (If at
all possible because python is actually a sub process of bash).

Thank you,
Maxim.

--
Cheers,
Maxim Veksler

"Free as in Freedom" - Do u GNU ?

[Diez B. Roggisch]

Maxim Veksler wrote:

Hello list,

I'm trying to write a python script that would allow me to manipulate
shell variables of the calling shell. I'm trying to write some logic
that would know to add LD_LIBRARY_PATH to the users environment.

In bash this is done with "export", can I do this with python? (If at
all possible because python is actually a sub process of bash).

It's not possible, OS restrictions - you are not allowed to alter the
environment of a parent process.

Diez

[Gerard Flanagan]

On Mar 12, 11:33 am, "Maxim Veksler" <hq4e...@gmail. comwrote:

Hello list,

I'm trying to write a python script that would allow me to manipulate
shell variables of the calling shell. I'm trying to write some logic
that would know to add LD_LIBRARY_PATH to the users environment.

In bash this is done with "export", can I do this with python? (If at
all possible because python is actually a sub process of bash).

The Popen class from the subprocess module takes an optional 'env'
parameter, which defines environment variables for the child process
created by Popen, if that helps.

Gerard

[Michal 'vorner' Vaner]

Hello,

On Mon, Mar 12, 2007 at 11:40:11AM +0100, Diez B. Roggisch wrote:

Maxim Veksler wrote:

I'm trying to write a python script that would allow me to manipulate
shell variables of the calling shell. I'm trying to write some logic
that would know to add LD_LIBRARY_PATH to the users environment.

It's not possible, OS restrictions - you are not allowed to alter the
environment of a parent process.

Actually, you are able to modify only your own environment (and call a
new process with any possible environment). And the restrictions seem to
me rather technical - the process would have to change its behaviour
each time it changes.

With regards

--
grep me no patterns and I'll tell you no lines.

Michal 'vorner' Vaner

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)

iD8DBQBF9TG+7/oWwynB3bIRAt2xA J99VglXt7xFFqRh bo1DTPLvNYdaUAC cCH5M
kZ1RRYyLO5UtPAl BdAARNU4=
=f68I
-----END PGP SIGNATURE-----

[Diez B. Roggisch]

Michal 'vorner' Vaner wrote:

Hello,

On Mon, Mar 12, 2007 at 11:40:11AM +0100, Diez B. Roggisch wrote:

>Maxim Veksler wrote:

I'm trying to write a python script that would allow me to manipulate
shell variables of the calling shell. I'm trying to write some logic
that would know to add LD_LIBRARY_PATH to the users environment.

It's not possible, OS restrictions - you are not allowed to alter the
environment of a parent process.

Actually, you are able to modify only your own environment (and call a
new process with any possible environment). And the restrictions seem to
me rather technical - the process would have to change its behaviour
each time it changes.

Not only technical - they are important security-wise - you could try and
make a parent process use a modified library that would e.g. authenticate
users without passwords.

Diez

[Diez B. Roggisch]

Dennis Lee Bieber wrote:

On Mon, 12 Mar 2007 12:33:58 +0200, "Maxim Veksler" <hq*****@gmail. com>
declaimed the following in comp.lang.pytho n:

>Hello list,

I'm trying to write a python script that would allow me to manipulate
shell variables of the calling shell. I'm trying to write some logic
that would know to add LD_LIBRARY_PATH to the users environment.

In bash this is done with "export", can I do this with python? (If at
all possible because python is actually a sub process of bash).

"calling shell"... Only OS I've encountered that allowed for a form
of that was AmigaOS, which differentiated between "shell specific"
(local) environment variables:

set lev "A Local Environment Variable"

and "system-wide" (global) ones:

setenv gev "Global Stuff"

The latter statement creates a file "env:gev" with "Global Stuff" as
the contents ("env:" was a logical name for a system environment
directory -- sys:env/ where sys: was a logical for the boot drive).

As files, system environment variables could be manipulated by
almost anything...

Lacking memory protection, actually anything of anything could me
manipulated... and it was a _great_ OS, really loved it!

Diez