Instead of trying to dig into the PyInstaller internals at this point, why not just delete (or move) the offending file from the dist directory, and then try to run the project? This would tell you if these near-duplicates are causing a problem or not.
This has happened to me a couple of times with PIL, and having both copies there didn't cause me any problems. On Fri, Apr 12, 2013 at 12:21 PM, dbv <[email protected]> wrote: > In --onedir mode, the COLLECT.toc and /dist folder show: > > "numpy.random.mtrand" and "random.mtrand" > > > Both are .pyd files. > > It is possible that "random.mtrand" is causing problems in my project and > so tried to exclude this module with: > > coll = COLLECT(exe, >> a.binaries + [...] - [('random.mtrand.pyd', None, None)], > > > But, COLLECT.toc and /dist still show the module. > > Also tried: > >> [('random.mtrand', None, None) > > and > >> [('random.mtrand.pyd', "", "") > > > but with no luck. > > How are modules excluded? > > -- > You received this message because you are subscribed to the Google Groups > "PyInstaller" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/pyinstaller?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Daniel Hyams [email protected] -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
