anatoly techtonik added the comment: On Sun, Sep 29, 2013 at 8:53 PM, Richard Oudkerk <rep...@bugs.python.org> wrote: > > Richard Oudkerk added the comment: > >> 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.
Visual Studio 10+ ? Is it available somewhere for a reference? >> 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. I value your expert opinion, but to increase the bus factor, I can not leave it without asking for reasons. Have you tried to run examples provided by MSDN - do they exhibit the same behavior as Python script I attached earlier and described in the first message? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19124> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
