This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author techtonik
Recipients amaury.forgeotdarc, techtonik
Date 2013-06-25.15:33:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372174385.69.0.84405834023.issue18298@psf.upfronthosting.co.za>
In-reply-to
Content
It is not about modifying Python in general, it is about patching pythonw.exe or subprocess or documenting how to make subprocess calls compatible with pythonw.exe


"don't use pythonw.exe in a console"

And how to debug the issue? Maybe the only solution in not using pythonw.exe at all if you want *windows* app solution, and do custom management of hidden windows.

http://code.google.com/p/spyderlib/source/browse/CHANGELOG
http://code.google.com/p/spyderlib/source/browse/spyderlib/utils/windows.py
History
Date User Action Args
2013-06-25 15:33:05techtoniksetrecipients: + techtonik, amaury.forgeotdarc
2013-06-25 15:33:05techtoniksetmessageid: <1372174385.69.0.84405834023.issue18298@psf.upfronthosting.co.za>
2013-06-25 15:33:05techtoniklinkissue18298 messages
2013-06-25 15:33:05techtonikcreate