[Scons-dev] Strange behavior of env.Execute(python script) on Windows

2014-03-05 Thread Alexandre Feblot
Hi, Would any of you have an idea on the behavior of printpath.py in the small test below? What happens to the PATH? Other variables are transfered properly. The similar perl test shows the PATH as expected. Sconstruct: env = Environment() env['ENV']['PATH'] += ';C:\\XX'

Re: [Scons-dev] Strange behavior of env.Execute(python script) on Windows

2014-03-05 Thread Alexandre Feblot
I'm using Active State ActivePython 2.7.2.5. I'm going to try the official python, then. Thanks. 2014-03-05 17:07 GMT+01:00 Gary Oberbrunner ga...@oberbrunner.com: Your example works OK for me; this is only the printpath.py part: scons: Reading SConscript files ... C:\tmp\printpath.py

Re: [Scons-dev] Strange behavior of env.Execute(python script) on Windows

2014-03-05 Thread Gary Oberbrunner
On Wed, Mar 5, 2014 at 12:13 PM, Alexandre Feblot alexan...@feblot.frwrote: I tested the latest ActivePython (2.7.5.6) to make sure: it's buggy too. If you're interested in pursuing it, you have two python invocations in your test: the python that runs SCons, and the python that runs your

Re: [Scons-dev] Strange behavior of env.Execute(python script) on Windows

2014-03-05 Thread Gary Oberbrunner
On Wed, Mar 5, 2014 at 1:31 PM, Alexandre Feblot alexan...@feblot.frwrote: I'll file a bug with ActiveState, but I'll stop here. And will start using the official python. I don't even know if they'll be able to investigate this without scons. And if they can't, maybe they'll just blame scons.