Yes, I think it's the same bug. Is there quick way to fix it? The Pyinstaller Team will fix it in 2.1 branch, and finish all of 2.1 at 12/31 on schedule. It's bit long :-(
在 2012年8月27日星期一UTC+8下午11时48分21秒，DwigAtWork写道： > > > On 8/22/12 10:36 PM, jun xie wrote: > > I have tow programs packed by pyinstaller2.0 running on windows, and I > want one of them start by another and detach from it. > > > > I used this code to start a detached subprocess: > > > > subprocess.Popen(command, stdin=None, stdout=None, stderr=None, > close_fds=True, > > creationflags=0x00000008) > > > > It works well when call every program from a python scripy, and call a > normal program from program which pyinstaller packed, but it doesn't work > when call a pyinstaller packed one from other programs pyinstaller packed. > > This sounds like it might be related to > http://www.pyinstaller.org/ticket/569, which I submitted. As the > description says, I worked around it by "merging" two branches of > PyInstaller in my working copy. If it does look like what you're > experiencing, add a comment on the ticket. > > -- > > Don Dwiggins > Advanced Publishing Technology > > > -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyinstaller/-/mrAMZ3ykQF8J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
