Daniel added the comment:
Here are some solutions which might help you until MS fixed the bug.
1) Even if the subsystem is Windows one solution is to call AllocConsole()
before Py_Initialize() to create a console.
2) Second Solution: If you don't want to open a console and your application
has its own output window you could redirect stdout/stderr/stdin with freopen
to a temp file first. (e.g: freopen("file.txt","w",stdout);) Call freopen for
all std handles before you call Py_Initialize(). You can keep the redirection
to the file or after Py_Initialize() succeeded you change the redirection now
in Python by redirect sys.stdout to the place you want.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue17797>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
