Re: [boost] [gil] Ok to merge new gil's extension to release branch?

Subject: Re: [boost] [gil] Ok to merge new gil's extension to release branch?
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2013-04-13 11:36:26

AMDG

On 04/13/2013 08:16 AM, Christian Henning wrote:
> On Sat, Apr 13, 2013 at 10:44 AM, Steven Watanabe <watanabesj_at_[hidden]>wrote:
> 
> According to the output the error happens testcmd.py at line 409. I added
> some debug code:
> 
> sys.stdout.write( "CHH: " + str( cmd ) + "\n")
> sys.stdout.write( "CHH: " + chdir + "\n")
> sys.stdout.write( "CHH: " + str( universal_newlines ) + "\n")
> 
> and the output is:
> c:\boost\tools\build\v2\test>python core_language.py
> CHH: ['c:\\boost\\tools\\build\\v2\\test\\..\\engine\\bin.ntx86\\bjam',
> '-sBOOST
> _BUILD_PATH="c:\\boost\\tools\\build\\v2\\test/.."', '-d0', '--quiet',
> '-ftest.j
> am', '--test-config="c:\\boost\\tools\\build\\v2\\test\\test-config.jam"',
> '--ig
> nore-toolset-requirements']
> CHH: c:\users\chhenn~1\appdata\local\temp\tmpnz6dv4
> CHH: True
> 
> Does that look reasonable?
> 

The command looks okay.  The only thing I can think
of is that Python doesn't like the short path
for chdir.  What happens if you change the argument
of Popen to cwd=os.path.realpath(chdir)?

In Christ,
Steven Watanabe