On Sat, 2010-11-20 at 08:12 -0800, dhyams wrote: > When I start up the code, though (at which time I also spawn the > processes), I get the attached stack trace (at bottom of email). I > think what is going on is that each process is trying to unpack to the > same spot, but I'm not sure how to adjust where things are being > unpacked to. The _MEIPASS2 variable seems to be just one to inform, > not adjust...I presume that the deciding on where to unpack is > determined in the bootloader. > > Further evidence that it's a 'unpackaging collision' is that it's not > the same module that fails every time....it's just a random one in my > list of imports. > > Is there a workaround for this?
Not really. What you say should not happen because the bootloader removes the _MEIPASS2 variable after it's used and before the application starts (see launch.c, and search for MEIPASS2). It's still visible at the Python level though (and used by rthooks and people wanting to know where DATA files have been unpacked), for reasons that elude me right now. So there is surely something weird going on here. -- Giovanni Bajo :: [email protected] Develer S.r.l. :: http://www.develer.com My Blog: http://giovanni.bajo.it Last post: Compile-time Function Execution in D -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. 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.
