Message198616
> Where did you get that info? MSDN is silent about that.
> http://msdn.microsoft.com/en-us/library/886kc0as(v=vs.90).aspx
Reading the source code for the C runtime included with Visual Studio.
> The problem is not in what I should or should not use. The problem
> that existing scripts that work on Unix and use os.execv() to launch
> interactive scripts, on Windows behave absolutely weird and unusable
> behavior. I previously experienced this with SCons, but couldn't get
> the reason. Now I experience this with basic Android development tools
> and dug down to this. It is clearly a big mess from this side of
> Windows.
As said before (more than once), os.exec*() is useless on Windows: just use subprocess. |
|
Date |
User |
Action |
Args |
2013-09-29 17:53:56 | sbt | set | recipients:
+ sbt, techtonik |
2013-09-29 17:53:56 | sbt | set | messageid: <1380477236.73.0.592881006747.issue19124@psf.upfronthosting.co.za> |
2013-09-29 17:53:56 | sbt | link | issue19124 messages |
2013-09-29 17:53:56 | sbt | create | |
|