Thanks again. Will do some reading on the matter. On Monday, March 26, 2012 6:25:23 PM UTC+1, rasky wrote: > > Il giorno 26/mar/2012, alle ore 18:38, Niall ha scritto: > > Thanks for the reply. > > That fixed it alright. I had to modify my project to the django layout, > and do the bootstrap thing too. > > The thing is though, my project isn't a django project... what reasons > might pyinstaller think it is? > > > It happens because somebody is importing django. It might be a third-party > library you are using, and it might be a code-path that you are not > actually executing (eg: you configured at runtime not to use django, but > PyInstaller can't know that). > > If you don't need Django, then you don't need the above fixes either, and > the simplest solution is to exclude django from the deployment (see the > manual on how to modify the spec file to exclude a specific package). > > If you are curious you can bump the log verbosity; at some point, it will > start dumping all modules that it analyzes, so that you can find where > django is being imported. > -- > Giovanni Bajo :: [email protected] > Develer S.r.l. :: http://www.develer.com > > My Blog: http://giovanni.bajo.it > > > > > > >
-- 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/-/FqfRrGPcE0cJ. 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.
