On 10/13/2011 09:50 AM, Durrieu Jean-Louis wrote: > Hi Eric, Fernando, > > thanks for your answers! > > On Oct 13, 2011, at 8:47 PM, Eric Firing wrote: > >> On 10/12/2011 10:47 PM, Durrieu Jean-Louis wrote: >> >> There is no compiled qt4 code, so installation should not require >> pyqt4--and I don't think it does. What led to your conclusion that >> you needed it to install from source? >> > > It s just that when I type "python setup.py build/--help/install", > depending on whether pyqt4 is installed or not, the script detects > that Qt is present or not (respectively), and pyside does not change > that behaviour. I must admit I did not try to run my script even when > Qt was not detected, maybe it works... But I guess there is a > consequence to the detection of Qt at the build step? > > Sorry for not providing the exact output of the build step, I m on > another computer. On my mac, the section of interest is: OPTIONAL > BACKEND DEPENDENCIES libpng: 1.5.2 Tkinter: Tkinter: version not > identified, Tk: 8.5, Tcl: 8.5 Gtk+: no * Building for Gtk+ requires > pygtk; you must be able * to "import gtk" in your build/install > environment Mac OS X native: yes Qt: no Qt4: Qt: 4.7.3, PyQt4: 4.8.5 > Cairo: no > > Here, it detected my pyqt4. But when it s not there, even if pyside > is installed, I get a "Qt4: no" instead... Do you mean that it's > still going to work, even it was not detected there?
Yes, it should work fine; as far as I know, nothing depends on the outcome of that auto-detection for qt4. The pyside support is always included in backend_qt4.py and backend_qt4agg.py, which are pure python, and are present regardless of whether pyqt4 itself is detected. Eric > >> This does not make sense to me. Assuming you are using bash, put >> this in your .bashrc file: >> >> export QT_API=pyside >> >> Anything you execute in a terminal window opened after that change >> should find the new environment variable. >> > > Oh, sorry for that! I must have been confused, I think I only typed > "QT_API=pyside" at the prompt, so I guess without the "export" > (doh!), that was useless... Since the doc (somewhere) talked about > "ETS environment variables", I thought there was something else to > it. If not, then I ll have to learn my bash again :-) > > Not a big issue, anyway! > > Cheers! > > Jean-Louis > ------------------------------------------------------------------------------ > > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and > makes sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ Matplotlib-users > mailing list Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
