> Thoughts?
Apparently, there are at least two "users" of SystemRoot:
- side-by-side (fusion?) apparently uses it to locate the WinSxS
folder, at least on some Windows releases,
- certain registry keys contain SystemRoot, in particular the
path names of crypto providers (this apparently is XP
On 05/12/2011 08:10, "Martin v. Löwis" wrote:
I agree with Nick that we shouldn't do anything except perhaps
for documentation changes. There are many other environment variables
whose absence could also cause failures to run the executable,
such as PATH, LD_LIBRARY_PATH, etc. Even not passing DI
On Mon, Dec 5, 2011 at 7:01 PM, Tim Golden wrote:
> We could probably do with a HOWTO (or blog post or whatever) on using
> subprocess on Windows, not least because a fair amount of the docs
> are Unix-centric and actually very slightly confusing for naive
> Windows-based developers.
>
> I think m
Hi Zbyszek,
See below my comment.
2011/11/26 Zbigniew Jędrzejewski-Szmek :
> Hi,
> I apologize in advance for the length of this mail.
>
> sys.path
>
> When a script or a module is executed by invoking python with proper
> arguments, sys.path is extended. When a path to script is given
