On 17 September 2010 21:12, Dan Halbert <[email protected]> wrote: > Maybe Raoul, who has the same kind of error, has a simpler one. I haven't > succeeded yet in creating one. I will work on it. I reread the trace module > doc and may be able to pinpoint where the R6034 happens, which is after a > bunch of Python runs.
I'm afraid I don't have a simple test case - I also have a rather large application. Piled on top of that, we're about to make another release (it's an open source app) in a week's time, so I don't really have time *right* now to figure much more out. Perhaps after the release I can do a bit of playing around. I wonder though, if it is not perhaps a particular library or set of libraries that is helping cause this. My application is written in PyQt4, so I'm wondering if it's not something like that. Dan, what other compiled libraries are you using? -- Raoul Snyman B.Tech Information Technology (Software Engineering) E-Mail: [email protected] Web: http://www.saturnlaboratories.co.za/ Blog: http://blog.saturnlaboratories.co.za/ Mobile: 082 550 3754 Registered Linux User #333298 (http://counter.li.org) -- 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.
