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 wrote:

> 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. Because started from a
> cmd, the python test script works just fine.
>
> OK, well thanks for taking it that far.

-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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

2014-03-05 Thread Alexandre Feblot 
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. Because started from a cmd,
the python test script works just fine.


2014-03-05 19:16 GMT+01:00 Gary Oberbrunner :

>
> On Wed, Mar 5, 2014 at 12:13 PM, Alexandre Feblot wrote:
>
>> 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 called
> script.  You might try one with each python to narrow down where it's going
> wrong.
>
>
> --
> Gary
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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 wrote:

> 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 called
script.  You might try one with each python to narrow down where it's going
wrong.


-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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

2014-03-05 Thread William Deegan 
Alex,

Perhaps file a bug with active state?

-Bill
On Mar 5, 2014, at 9:13 AM, Alexandre Feblot  wrote:

> I tested the latest ActivePython (2.7.5.6) to make sure: it's buggy too.
> 
> 
> 2014-03-05 17:57 GMT+01:00 Gary Oberbrunner :
> 
> 
> On Wed, Mar 5, 2014 at 11:46 AM, Alexandre Feblot  wrote:
> Right, that was it. It behaves properly with the official 2.7.6.
> 
> I'm surprised actually; I thought ActiveState python should be pretty close 
> to python.org python, with extra stuff (like pywin32).
>  
> On the other hand, the official distrib doesn't package winerror, win32api 
> and win32con modules which I am using.
> 
> I usually just install those afterward.
> 
> -- 
> Gary
> 
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
> 
> 
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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

2014-03-05 Thread Alexandre Feblot 
I tested the latest ActivePython (2.7.5.6) to make sure: it's buggy too.


2014-03-05 17:57 GMT+01:00 Gary Oberbrunner :

>
>
> On Wed, Mar 5, 2014 at 11:46 AM, Alexandre Feblot wrote:
>
>> Right, that was it. It behaves properly with the official 2.7.6.
>>
>
> I'm surprised actually; I thought ActiveState python should be pretty
> close to python.org python, with extra stuff (like pywin32).
>
>
>> On the other hand, the official distrib doesn't package winerror,
>> win32api and win32con modules which I am using.
>>
>
> I usually just install those afterward.
>
> --
> Gary
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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

2014-03-05 Thread Gary Oberbrunner 
On Wed, Mar 5, 2014 at 11:46 AM, Alexandre Feblot wrote:

> Right, that was it. It behaves properly with the official 2.7.6.
>

I'm surprised actually; I thought ActiveState python should be pretty close
to python.org python, with extra stuff (like pywin32).


> On the other hand, the official distrib doesn't package winerror, win32api
> and win32con modules which I am using.
>

I usually just install those afterward.

-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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

2014-03-05 Thread Alexandre Feblot 
Right, that was it. It behaves properly with the official 2.7.6.
On the other hand, the official distrib doesn't package winerror, win32api
and win32con modules which I am using.
Choice time...
Thanks again.


2014-03-05 17:12 GMT+01:00 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 :
>
> Your example works OK for me; this is only the printpath.py part:
>>
>> scons: Reading SConscript files ...
>> C:\tmp\printpath.py
>> C:\Program Files (x86)\Microsoft Visual Studio
>> 11.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files
>> (x86)\Microsoft Visual Studio
>> 11.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v4.0.30319;c:\Windows\Microsoft.NET\Framework64\v3.5;C:\Program
>> Files (x86)\Microsoft Visual Studio 11.0\VC\VCPackages;C:\Program Files
>> (x86)\Microsoft Visual Studio 11.0\Common7\IDE;C:\Program Files
>> (x86)\Microsoft Visual Studio 11.0\Common7\Tools;C:\Program Files
>> (x86)\Microsoft Visual Studio 11.0\Team Tools\Performance
>> Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 11.0\Team
>> Tools\Performance Tools;C:\Program Files (x86)\Windows
>> Kits\8.0\bin\x64;C:\Program Files (x86)\Windows Kits\8.0\bin\x86;C:\Program
>> Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\x64;C:\Program
>> Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\x64;C:\Program Files
>> (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools;C:\Program Files
>> (x86)\Microsoft
>> SDKs\Windows\v7.0A\bin\;C:\Windows\System32;C:\XX
>>
>> Are you using cygwin python or real python?  I suggest trying real (
>> python.org) python if you're using cygwin.  There are some oddities with
>> cygwin python.
>>
>>
>>
>> On Wed, Mar 5, 2014 at 10:31 AM, Alexandre Feblot wrote:
>>
>>> 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'
>>> env.Execute(File('#/printpath.py').abspath)
>>> env.Execute(File('#/printpath.pl').abspath)
>>>
>>> printpath.pl:
>>> #!/usr/bin/perl
>>> print "$ENV{PATH}\n";
>>>
>>> printpath.py:
>>> #!/usr/bin/python
>>> import os
>>> print os.environ['PATH']
>>>
>>> On windows (server 2008R2), with python 2.7.2, the result is:
>>> scons: Reading SConscript files ...
>>> C:\bug\printpath.py
>>> C:\Python27\
>>> C:\bug\printpath.pl
>>> c:\Program Files (x86)\Microsoft Visual Studio
>>> 9.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v3.5;c:\Windows\Microsoft.NET\Framework64\v3.5\Microsoft
>>> .NET Framework 3.5 (Pre-Release
>>> Version);c:\Windows\Microsoft.NET\Framework64\v2.0.50727;c:\Program Files
>>> (x86)\Microsoft Visual Studio 9.0\VC\VCPackages;c:\Program Files
>>> (x86)\Microsoft Visual Studio 9.0\Common7\IDE;c:\Program Files
>>> (x86)\Microsoft Visual Studio 9.0\Common7\Tools;c:\Program Files
>>> (x86)\Microsoft Visual Studio 9.0\Common7\Tools\bin;C:\Program
>>> Files\Microsoft SDKs\Windows\v6.0A\bin\x64;C:\Program Files\Microsoft
>>> SDKs\Windows\v6.0A\bin\win64\x64;C:\Program Files\Microsoft
>>> SDKs\Windows\v6.0A\bin;C:\Windows\System32;C:\XX
>>> scons: done reading SConscript files.
>>> scons: Building targets ...
>>> scons: `.' is up to date.
>>> scons: done building targets.
>>>
>>> Thanks
>>>
>>>
>>> ___
>>> Scons-dev mailing list
>>> Scons-dev@scons.org
>>> http://two.pairlist.net/mailman/listinfo/scons-dev
>>>
>>>
>>
>>
>> --
>> Gary
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> http://two.pairlist.net/mailman/listinfo/scons-dev
>>
>>
>
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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 :

> Your example works OK for me; this is only the printpath.py part:
>
> scons: Reading SConscript files ...
> C:\tmp\printpath.py
> C:\Program Files (x86)\Microsoft Visual Studio
> 11.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files
> (x86)\Microsoft Visual Studio
> 11.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v4.0.30319;c:\Windows\Microsoft.NET\Framework64\v3.5;C:\Program
> Files (x86)\Microsoft Visual Studio 11.0\VC\VCPackages;C:\Program Files
> (x86)\Microsoft Visual Studio 11.0\Common7\IDE;C:\Program Files
> (x86)\Microsoft Visual Studio 11.0\Common7\Tools;C:\Program Files
> (x86)\Microsoft Visual Studio 11.0\Team Tools\Performance
> Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 11.0\Team
> Tools\Performance Tools;C:\Program Files (x86)\Windows
> Kits\8.0\bin\x64;C:\Program Files (x86)\Windows Kits\8.0\bin\x86;C:\Program
> Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\x64;C:\Program
> Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\x64;C:\Program Files
> (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools;C:\Program Files
> (x86)\Microsoft
> SDKs\Windows\v7.0A\bin\;C:\Windows\System32;C:\XX
>
> Are you using cygwin python or real python?  I suggest trying real (
> python.org) python if you're using cygwin.  There are some oddities with
> cygwin python.
>
>
>
> On Wed, Mar 5, 2014 at 10:31 AM, Alexandre Feblot wrote:
>
>> 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'
>> env.Execute(File('#/printpath.py').abspath)
>> env.Execute(File('#/printpath.pl').abspath)
>>
>> printpath.pl:
>> #!/usr/bin/perl
>> print "$ENV{PATH}\n";
>>
>> printpath.py:
>> #!/usr/bin/python
>> import os
>> print os.environ['PATH']
>>
>> On windows (server 2008R2), with python 2.7.2, the result is:
>> scons: Reading SConscript files ...
>> C:\bug\printpath.py
>> C:\Python27\
>> C:\bug\printpath.pl
>> c:\Program Files (x86)\Microsoft Visual Studio
>> 9.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v3.5;c:\Windows\Microsoft.NET\Framework64\v3.5\Microsoft
>> .NET Framework 3.5 (Pre-Release
>> Version);c:\Windows\Microsoft.NET\Framework64\v2.0.50727;c:\Program Files
>> (x86)\Microsoft Visual Studio 9.0\VC\VCPackages;c:\Program Files
>> (x86)\Microsoft Visual Studio 9.0\Common7\IDE;c:\Program Files
>> (x86)\Microsoft Visual Studio 9.0\Common7\Tools;c:\Program Files
>> (x86)\Microsoft Visual Studio 9.0\Common7\Tools\bin;C:\Program
>> Files\Microsoft SDKs\Windows\v6.0A\bin\x64;C:\Program Files\Microsoft
>> SDKs\Windows\v6.0A\bin\win64\x64;C:\Program Files\Microsoft
>> SDKs\Windows\v6.0A\bin;C:\Windows\System32;C:\XX
>> scons: done reading SConscript files.
>> scons: Building targets ...
>> scons: `.' is up to date.
>> scons: done building targets.
>>
>> Thanks
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> http://two.pairlist.net/mailman/listinfo/scons-dev
>>
>>
>
>
> --
> Gary
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

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

2014-03-05 Thread Gary Oberbrunner 
Your example works OK for me; this is only the printpath.py part:

scons: Reading SConscript files ...
C:\tmp\printpath.py
C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files
(x86)\Microsoft Visual Studio
11.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v4.0.30319;c:\Windows\Microsoft.NET\Framework64\v3.5;C:\Program
Files (x86)\Microsoft Visual Studio 11.0\VC\VCPackages;C:\Program Files
(x86)\Microsoft Visual Studio 11.0\Common7\IDE;C:\Program Files
(x86)\Microsoft Visual Studio 11.0\Common7\Tools;C:\Program Files
(x86)\Microsoft Visual Studio 11.0\Team Tools\Performance
Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 11.0\Team
Tools\Performance Tools;C:\Program Files (x86)\Windows
Kits\8.0\bin\x64;C:\Program Files (x86)\Windows Kits\8.0\bin\x86;C:\Program
Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\x64;C:\Program
Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\x64;C:\Program Files
(x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools;C:\Program Files
(x86)\Microsoft
SDKs\Windows\v7.0A\bin\;C:\Windows\System32;C:\XX

Are you using cygwin python or real python?  I suggest trying real (
python.org) python if you're using cygwin.  There are some oddities with
cygwin python.



On Wed, Mar 5, 2014 at 10:31 AM, Alexandre Feblot wrote:

> 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'
> env.Execute(File('#/printpath.py').abspath)
> env.Execute(File('#/printpath.pl').abspath)
>
> printpath.pl:
> #!/usr/bin/perl
> print "$ENV{PATH}\n";
>
> printpath.py:
> #!/usr/bin/python
> import os
> print os.environ['PATH']
>
> On windows (server 2008R2), with python 2.7.2, the result is:
> scons: Reading SConscript files ...
> C:\bug\printpath.py
> C:\Python27\
> C:\bug\printpath.pl
> c:\Program Files (x86)\Microsoft Visual Studio
> 9.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v3.5;c:\Windows\Microsoft.NET\Framework64\v3.5\Microsoft
> .NET Framework 3.5 (Pre-Release
> Version);c:\Windows\Microsoft.NET\Framework64\v2.0.50727;c:\Program Files
> (x86)\Microsoft Visual Studio 9.0\VC\VCPackages;c:\Program Files
> (x86)\Microsoft Visual Studio 9.0\Common7\IDE;c:\Program Files
> (x86)\Microsoft Visual Studio 9.0\Common7\Tools;c:\Program Files
> (x86)\Microsoft Visual Studio 9.0\Common7\Tools\bin;C:\Program
> Files\Microsoft SDKs\Windows\v6.0A\bin\x64;C:\Program Files\Microsoft
> SDKs\Windows\v6.0A\bin\win64\x64;C:\Program Files\Microsoft
> SDKs\Windows\v6.0A\bin;C:\Windows\System32;C:\XX
> scons: done reading SConscript files.
> scons: Building targets ...
> scons: `.' is up to date.
> scons: done building targets.
>
> Thanks
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
>
>


-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

[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'
env.Execute(File('#/printpath.py').abspath)
env.Execute(File('#/printpath.pl').abspath)

printpath.pl:
#!/usr/bin/perl
print "$ENV{PATH}\n";

printpath.py:
#!/usr/bin/python
import os
print os.environ['PATH']

On windows (server 2008R2), with python 2.7.2, the result is:
scons: Reading SConscript files ...
C:\bug\printpath.py
C:\Python27\
C:\bug\printpath.pl
c:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\BIN\amd64;c:\Windows\Microsoft.NET\Framework64\v3.5;c:\Windows\Microsoft.NET\Framework64\v3.5\Microsoft
.NET Framework 3.5 (Pre-Release
Version);c:\Windows\Microsoft.NET\Framework64\v2.0.50727;c:\Program Files
(x86)\Microsoft Visual Studio 9.0\VC\VCPackages;c:\Program Files
(x86)\Microsoft Visual Studio 9.0\Common7\IDE;c:\Program Files
(x86)\Microsoft Visual Studio 9.0\Common7\Tools;c:\Program Files
(x86)\Microsoft Visual Studio 9.0\Common7\Tools\bin;C:\Program
Files\Microsoft SDKs\Windows\v6.0A\bin\x64;C:\Program Files\Microsoft
SDKs\Windows\v6.0A\bin\win64\x64;C:\Program Files\Microsoft
SDKs\Windows\v6.0A\bin;C:\Windows\System32;C:\XX
scons: done reading SConscript files.
scons: Building targets ...
scons: `.' is up to date.
scons: done building targets.

Thanks
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev