Re: [PyQt] SIP, PyQt compatibility with QT version
On Tuesday 14 June 2011, 07:09:27 Vivek Narvekar wrote: > Hello, > > > > I was previously using SIP 3.3 and PyQt 3.3 versions with Qt 3.0.8. > > Now I am planning to migrate to QT 3.3.6-8. This might work, but nobody will care, if it doesn't. > Can you please tell me if SIP 3.3 and PyQt 3.3 version are compatible > with QT 3.3.6-8 ? Well, being backwards isn't a crime per se, but for your own safety, I would strongly advise to use the the latest sip and PyQt3 releases: sip: 4.12.3 PyQt3: 3.18.1 That way, your PyQt3 code has good chances of still working properly, and you have the foundation for using PyQt4 in parallel, too. Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] SIP, PyQt compatibility with QT version
Be careful, I think using PyQt3 3.18.1 with SIP 4.12.1 introduces memory leaks (these are the versions on latest Debian unstable). Don't know about using SIP 4.12.3. Check my post here: http://old.nabble.com/Simple-usage-of-QListView-seems-to-leak-memory-in-PyQt-3.18.1-td31812404.html Saludos, Nahuel Greco. On Tue, Jun 14, 2011 at 6:28 AM, Hans-Peter Jansen wrote: > On Tuesday 14 June 2011, 07:09:27 Vivek Narvekar wrote: >> Hello, >> >> >> >> I was previously using SIP 3.3 and PyQt 3.3 versions with Qt 3.0.8. >> >> Now I am planning to migrate to QT 3.3.6-8. > > This might work, but nobody will care, if it doesn't. > >> Can you please tell me if SIP 3.3 and PyQt 3.3 version are compatible >> with QT 3.3.6-8 ? > > Well, being backwards isn't a crime per se, but for your own safety, I would > strongly advise to use the the latest sip and PyQt3 releases: > > sip: 4.12.3 > PyQt3: 3.18.1 > > That way, your PyQt3 code has good chances of still working properly, and > you have the foundation for using PyQt4 in parallel, too. > > Pete > ___ > PyQt mailing list PyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Fwd: PyQt-mac-gpl-snapshot-4.8.5 fails to compile on Mac Pro under 10.6.7
Hi all, I got the point : successful install by upgrading to Python 2.6.7! Cheers JB Début du message réexpédié : > De : Jean-Baptiste Marquette > Date : 14 juin 2011 07:10:09 UTC+10:00 > À : pyqt@riverbankcomputing.com > Objet : [PyQt] PyQt-mac-gpl-snapshot-4.8.5 fails to compile on Mac Pro under > 10.6.7 > > Dear PyQt gurus, > > I try to install the latest PyQt4 snapshot on my Mac Pro, and got the > following error: > > ld: warning: ignoring file /Library/Frameworks//Python.framework/Python, > missing required architecture x86_64 in file > Undefined symbols for architecture x86_64: > "_PyImport_ImportModule", referenced from: > PyCustomWidgets::getModuleAttr(char const*, char const*)in pluginloader.o > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyErr_Print", referenced from: > PyCustomWidgets::getModuleAttr(char const*, char const*)in pluginloader.o > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyObject_GetAttrString", referenced from: > PyCustomWidgets::getModuleAttr(char const*, char const*)in pluginloader.o > "_Py_IsInitialized", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_Py_Initialize", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyString_FromString", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyList_Append", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyModule_GetDict", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyType_IsSubtype", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyObject_CallObject", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyObject_CallFunctionObjArgs", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyLong_AsVoidPtr", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > "_PyDict_Next", referenced from: > PyCustomWidgets::PyCustomWidgets(QObject*)in pluginloader.o > ld: symbol(s) not found for architecture x86_64 > collect2: ld returned 1 exit status > make[1]: *** [libpythonplugin.bundle] Error 1 > make: *** [all] Error 2 > > This is quite strange as the same install succeeds on my MacBook Pro under > (hopefully...) the same configuration. > > Any hint welcome, thanks for your help. > > Cheers, > Jean-Baptiste > > > ___ > PyQt mailing listPyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] SIP, PyQt compatibility with QT version
On Tuesday 14 June 2011, 14:49:16 Nahuel Greco wrote: > Be careful, I think using PyQt3 3.18.1 with SIP 4.12.1 introduces > memory leaks (these are the versions on latest Debian unstable). Don't > know about using SIP 4.12.3. Check my post here: > > http://old.nabble.com/Simple-usage-of-QListView-seems-to-leak-memory-in-P >yQt-3.18.1-td31812404.html I noticed your post on this list and can confirm your findings. It might be worth to convert your memory leak exploit into C++ just to rule out a Qt bug. Otherwise, this is Phils call (IFAICT, please understand, that PyQt3 bugs are handled with very low priority only, if at all). Pete > Saludos, > Nahuel Greco. > > On Tue, Jun 14, 2011 at 6:28 AM, Hans-Peter Jansen wrote: > > On Tuesday 14 June 2011, 07:09:27 Vivek Narvekar wrote: > >> Hello, > >> > >> > >> > >> I was previously using SIP 3.3 and PyQt 3.3 versions with Qt 3.0.8. > >> > >> Now I am planning to migrate to QT 3.3.6-8. > > > > This might work, but nobody will care, if it doesn't. > > > >> Can you please tell me if SIP 3.3 and PyQt 3.3 version are compatible > >> with QT 3.3.6-8 ? > > > > Well, being backwards isn't a crime per se, but for your own safety, I > > would strongly advise to use the the latest sip and PyQt3 releases: > > > > sip: 4.12.3 > > PyQt3: 3.18.1 > > > > That way, your PyQt3 code has good chances of still working properly, > > and you have the foundation for using PyQt4 in parallel, too. > > > > Pete > > ___ > > PyQt mailing list PyQt@riverbankcomputing.com > > http://www.riverbankcomputing.com/mailman/listinfo/pyqt > > ___ > PyQt mailing listPyQt@riverbankcomputing.com > http://www.riverbankcomputing.com/mailman/listinfo/pyqt ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Where can I find older versions of PyQt4 ?
It seems, that there is some bugs with newer versions of PyQt 4.8.x regarding screenshots code in GNS3. This feature worked well with PyQt 4.7.x. Where can I find binary PyQt 4.7.x. for Windows ? -- -Alexey Eromenko "Technologov" ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Comppiling QScintilla with python 3.2
After long trepidation, I started moving my python scripts from python 2.x to python 3.2. Pleasant surprise - sip-4.12.3 and PyQt-x11-gpl-4.8.4 compiled without problems! Python 3.2 IDLE does not work well with this version of PyQt. Anyway, eric 5.x would be better, so it is necessary to install python 3 version of QScintilla. Downloaded QScintilla-gpl-2.5.1.tar.gz, expanded the tar ball and attempted to compile: Changed the current dir to QScintilla-gpl-2.5.1/Python/ and tried the first step: $ python3.2 configure.py It immediately responded with the message: "Qsci/qsciglobal.h could not be found in /usr/include/qt4. If QScintilla is installed then use the -n argument to explicitly specify the correct directory." I am using a freshly installed kubuntu 11.04 "natty" OS and had a python 2.x version of QScintilla installed from ubuntu binaries. I thought that the message may simply be because of the installed binaries, so "completely removed" the installed QScintilla with the aid of "synaptic" program and tried to repeat the first step of compilation. It failed again with an identical message. I suspect I am doing someting wrong, but what? So where do I go from here? Your help will be greatly appreciated. OldAl. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[PyQt] Running a PyQt app compiled on OS X 10.6 on 10.5
I have a PyQt app which I compile into a binary with py2app (latest stable
versions of sip and PyQt [commercial]). I recently upgraded my build
machine from OSX 10.5 to 10.6. The binaries built on my new 10.6 system
won't even start up on 10.5:
6/13/11 10:36:35 AM com.apple.launchd[73] (0x10bab0.Locum[647]) Exited:
Terminated
6/13/11 10:37:19 AM [0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656]
<_FuncPtr object at 0x4b47b0>
6/13/11 10:37:19 AM [0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656]
Traceback (most recent call last):
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] File
"/Applications/RoastLogger.app/Contents/Resources/__boot__.py", line 187, in
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656]
_run('RoastLogger.py')
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] File
"/Applications/RoastLogger.app/Contents/Resources/__boot__.py", line 184, in
_run
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] execfile(path,
globals(), globals())
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] File
"/Applications/RoastLogger.app/Contents/Resources/RoastLogger.py", line 6,
in
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] from
roastloggerlib import main
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] File
"roastloggerlib/main.pyo", line 8, in
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] File
"PyQt4/QtGui.pyo", line 18, in
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656] File
"PyQt4/QtGui.pyo", line 11, in __load
6/13/11 10:37:19 AM [0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656]
ImportError:
dlopen(/Applications/RoastLogger.app/Contents/Resources/lib/python2.6/lib-dynload/PyQt4/QtGui.so,
2): no suitable image found. Did find:
6/13/11 10:37:19 AM
[0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656]
/Applications/RoastLogger.app/Contents/Resources/lib/python2.6/lib-dynload/PyQt4/QtGui.so:
unknown required load command 0x8022
6/13/11 10:37:19 AM RoastLogger[656] RoastLogger Error
6/13/11 10:37:21 AM com.apple.launchd[73]
([0x0-0x66066].org.pythonmac.unspecified.RoastLogger[656]) Exited with exit
code: 255
Googling around for "unknown required load command 0x8022" I did find
that this can be an issue with compiled apps, PyQt or otherwise:
http://www.riverbankcomputing.com/pipermail/pyqt/2009-November/025098.html
I have not yet tried altering the flags as that thread suggests. What's the
right/easiest way around this issue?
BZ
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Comppiling QScintilla with python 3.2
On Wednesday 15 June 2011, 03:04:32 Algis Kabaila wrote: > After long trepidation, I started moving my python scripts from python > 2.x to python 3.2. > > Pleasant surprise - sip-4.12.3 and PyQt-x11-gpl-4.8.4 compiled without > problems! > > Python 3.2 IDLE does not work well with this version of PyQt. Anyway, > eric 5.x would be better, so it is necessary to install python 3 version > of QScintilla. Downloaded QScintilla-gpl-2.5.1.tar.gz, expanded the tar > ball and attempted to compile: > > Changed the current dir to QScintilla-gpl-2.5.1/Python/ and tried the > first step: > > $ python3.2 configure.py > > It immediately responded with the message: > > "Qsci/qsciglobal.h could not be found in /usr/include/qt4. If QScintilla > is installed then use the -n argument to explicitly specify the correct > directory." You need to compile and install the qscintilla C++ lib before generating the python wrappers: pushd Qt4 qmake qscintilla.pro sudo make install popd > I am using a freshly installed kubuntu 11.04 "natty" OS and had a python > 2.x version of QScintilla installed from ubuntu binaries. I thought that > the message may simply be because of the installed binaries, so > "completely removed" the installed QScintilla with the aid of "synaptic" > program and tried to repeat the first step of compilation. It failed > again with an identical message. I suspect I am doing someting wrong, > but what? > > So where do I go from here? Al, manually compiling stuff like this should be done as the last resort only. One of the most compelling reasons to use Linux is the distributions package manager. OTOH, mixing that with manual builds is the source for many strange failures. My advice is: go through the hassle of building packages for your distribution. Even better, as far as I know, Ubuntu has something similar to openSUSE build service, or you might want to use that, since it is able to create ubuntu builds, too. Just needing the packages on a second system will pay off for the initial hassle. Guaranteed. Pete ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
Re: [PyQt] Comppiling QScintilla with python 3.2
On Wednesday 15 June 2011 15:45:08 Hans-Peter Jansen wrote: > On Wednesday 15 June 2011, 03:04:32 Algis Kabaila wrote: > > After long trepidation, I started moving my python scripts from python > > 2.x to python 3.2. > > > > Pleasant surprise - sip-4.12.3 and PyQt-x11-gpl-4.8.4 compiled without > > problems! > > > > Python 3.2 IDLE does not work well with this version of PyQt. Anyway, > > eric 5.x would be better, so it is necessary to install python 3 version > > of QScintilla. Downloaded QScintilla-gpl-2.5.1.tar.gz, expanded the tar > > ball and attempted to compile: > > > > Changed the current dir to QScintilla-gpl-2.5.1/Python/ and tried the > > first step: > > > > $ python3.2 configure.py > > > > It immediately responded with the message: > > > > "Qsci/qsciglobal.h could not be found in /usr/include/qt4. If QScintilla > > is installed then use the -n argument to explicitly specify the correct > > directory." > > You need to compile and install the qscintilla C++ lib before generating > the python wrappers: > > pushd Qt4 > qmake qscintilla.pro > sudo make install > popd > > > I am using a freshly installed kubuntu 11.04 "natty" OS and had a python > > 2.x version of QScintilla installed from ubuntu binaries. I thought that > > the message may simply be because of the installed binaries, so > > "completely removed" the installed QScintilla with the aid of "synaptic" > > program and tried to repeat the first step of compilation. It failed > > again with an identical message. I suspect I am doing someting wrong, > > but what? > > > > So where do I go from here? > > Al, manually compiling stuff like this should be done as the last resort > only. > > One of the most compelling reasons to use Linux is the distributions > package manager. OTOH, mixing that with manual builds is the source for > many strange failures. > > My advice is: go through the hassle of building packages for your > distribution. Even better, as far as I know, Ubuntu has something similar > to openSUSE build service, or you might want to use that, since it is able > to create ubuntu builds, too. > > Just needing the packages on a second system will pay off for the initial > hassle. Guaranteed. > > Pete Pete, thank you for the useful information. I have followed the instructions in http://www.riverbankcomputing.co.uk/static/Docs/QScintilla2/index.html and the process worked without error messages. Sorry for the noise! Thank you for the advice - greatly appreciated. I will certainly give it careful thought in my future endeavours. OTOH, it is tempting on occasions to take the lazy alternative - when your age is approaching 90 (3 years and 8 months to go :). Great to see you active and still serving SUSE community. Tempting to return to it, but ubuntu is nice and easy... Many thanks again, Al. ___ PyQt mailing listPyQt@riverbankcomputing.com http://www.riverbankcomputing.com/mailman/listinfo/pyqt
