New submission from Mark Summerfield: I have a Python Windows GUI application (using PySide) that uses multiprocessing.
When I freeze the application I get error messages, in particular that mulitprocessing cannot call flush on a null object. ISTM That in a Windows GUI application, sys.stdout and sys.stderr may well be None since there is no attached console. So, I added guards to accesses to sys.stdout and sys.stderr and the problems went away. I'm not used to creating patch diffs but hopefully the attached (with just a few lines of changes) will be easy to understand. ---------- components: Windows files: multiprocessing.diff keywords: patch messages: 211089 nosy: mark priority: normal severity: normal status: open title: multiprocessing cx_Freeze windows GUI bug (& easy fixes) versions: Python 3.3 Added file: http://bugs.python.org/file34060/multiprocessing.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20607> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
