Fredrik Lundh wrote:
> what part of your observations makes you think that the environment isn't
> "captured" (i.e. > copied from the process environment) when the os module is
> imported ?
Answer: the part that was informed by a fundamental misunderstanding on
my part of how the os module obtai
[EMAIL PROTECTED] wrote:
> Do these observations fit with what is stated in section 6.1.1 of the
> Python Library Reference?
yes. what part of your observations makes you think that the
environment isn't "captured" (i.e. copied from the process environ-
ment) when the os module is imported ?
(h
hat the PATH variable was, in fact, changed)
5) in interactive window, del os
6) in interactive window, import os
7) os.environ['PATH'] - presents the same value as in #3
I also observed that if I exit the interactive window, and then go back
into the interactive window, the os.environ[&#
[EMAIL PROTECTED] wrote:
> O/S: Win2K
> Vsn of Python:2.4
>
> Based on a search of other posts in this group, it appears as though
> os.environ['PATH'] is one way to obtain the PATH environment variable.
>
> My questions:
> 1) is it correct that os.environ[&#x
[EMAIL PROTECTED] wrote:
> Based on a search of other posts in this group, it appears as though
> os.environ['PATH'] is one way to obtain the PATH environment variable.
>
> My questions:
> 1) is it correct that os.environ['PATH'] contains the PATH environmen
O/S: Win2K
Vsn of Python:2.4
Based on a search of other posts in this group, it appears as though
os.environ['PATH'] is one way to obtain the PATH environment variable.
My questions:
1) is it correct that os.environ['PATH'] contains the PATH environment
variable?
2) are
