[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Changes by Christian Häggström : -- nosy: +chn ___ Python tracker <http://bugs.python.org/issue6531> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3905] subprocess failing in GUI applications on Windows

Changes by Christian Häggström : -- nosy: +chn ___ Python tracker <http://bugs.python.org/issue3905> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12607] subprocess(stdout=..., stderr=sys.stdout) breaks stderr for child

Christian Häggström added the comment: Thanks for the patch, I haven't tried it (I'm still on Python 2.7) but it looks very special-cased to my case. I can think about exotic cases like stdin = sys.stderr, stdout = sys.stdin, stderr = sys.stdout It can happen in reality if a d

[issue12607] subprocess(stdout=..., stderr=sys.stdout) breaks stderr for child

Christian Häggström added the comment: I expect that 'ls' print the error message on its stderr, which would be redirected to stdout of the test Python program. If I had been using stderr = subprocess.STDOUT, I can agree with you that both output streams would go to

[issue12607] subprocess(stdout=..., stderr=sys.stdout) breaks stderr for child

New submission from Christian Häggström : I hit a variant of issue #12251, namely when you redirect both stdout and stderr of a child process and one of them uses a low fd. Testcase: import subprocess, sys subprocess.call(["ls", "asda"], stderr = sys.stdout, stdout = o

[issue3426] os.path.abspath with unicode argument should call os.getcwdu

New submission from Christian Häggström <[EMAIL PROTECTED]>: If current working directory contains non-ascii characters, calling os.path.abspath(u".") will result in an error. I expect it to call the underlying os.getcwdu() in this case. >>> import os >>> os.