Stuart Mentzer <s...@objexx.com> added the comment: Further experimentation revealed that freeze_support() works properly and the proposed patch is not necessary or desirable for the general freeze case. In the case of an embedded app that calls set_executable() it seems that the "else" block calling _python_exe should be taken but won't be, so I still think there may be a problem here.
In our situation it turned out that an imported module was grabbing the command line arguments before freeze_support() was called and when that was addressed the need for a separate python executable and calling set_executable() was eliminated. I suggest that the documentation for freeze_support() make it clear that it must get called before an application processes the arguments or that the application must allow a --multiprocessing-fork option with a string value so that the initialization continues until freeze_support() is called. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6461> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
