Arana, please feel free to ask here about any questions building distributable apps with PyQt - I'm currently working on this and I might be able to share some workarounds I've had to use.
Also, I'd suggest you use the current development version of py2app, which has some related changes. For example, see an earlier thread about needing to create a qt.conf file in the app bundle to avoid plugin warnings and potential crashes: http://mail.python.org/pipermail/pythonmac-sig/2012-May/023569.html -mike On Mon, Jul 16, 2012 at 3:51 PM, Arana Fireheart <aranafirehe...@mac.com> wrote: > Charlie, > > Thanks for the response. Part of the reason I was trying to use > virtualenv was to 'disconnect' from a few years of builds (some successful/ > some unsuccessful). I was hoping to avoid doing a 'clean install' of my > machine and reinstall of of the apps etc. > > The latest attempt is to perform a 'new' install of PyQT and then > copy the site-packages directory into the virtual environment (or possibly > sym link it). I think this one shows the most promise for getting an > environment that will not only run my PyQT apps but allow me to build a > distribution version with py2app (which I have NEVER managed to be able to > do!!) > > I'll let you all know how it goes, Iv'e got my finger's crossed! > > Arana > > > > On Jul 12, 2012, at 6:00 AM, pythonmac-sig-requ...@python.org wrote: > >> Am 11.07.2012, 14:41 Uhr, schrieb Arana Fireheart <aranafirehe...@mac.com>: >> >>> Charlie, >>> I tried virtualenv after reading lots of people extolling it's >>> virtues. Having had little luck with other methods I thought I would give >>> it a try. I have managed to get this all built on my MacBookPro which is >>> running Snow Leopard, but not on my desktop machine (iMac). HomeBrew lists >>> PyQT as installed, but when I try to run some code it fails with a "can't >>> find module". >>> What I don't get is why python can't locate the installed modules. Do >>> you have any hints as to how I can track this down? >> >> Hi Arana, >> >> virtualenv's are indeed a great idea. They allow you to isolate the >> libraries for different projects from each other. However, if you are >> using libraries that need compiling then it can be better to use "system" >> libraries. You can do this in a virtualenv with the switch >> "--system-site-packages" >> >> Charlie >> -- >> Charlie Clark >> Managing Director >> Clark Consulting & Research >> German Office >> Kronenstr. 27a >> Düsseldorf >> D- 40217 >> Tel: +49-211-600-3657 >> Mobile: +49-178-782-6226 >> >> >> >> unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
