Arch Linux has recently switched its 'python' package to the Python v3
branch. SIP and PyQt still require the 'python2' package, probably because
the unpatched D-Bus Python bindings currently won't work with Python v3.
I'm guessing that some other Linux distributions will continue using Python
v2
I must also leap to the defence of Arch Linux, which I've happily used for
about four years. In calling itself a "bleeding-edge" distribution, it must
be willing to upgrade major packages promptly. I think the onus is now on
other distributions to ensure that the 'python2' and 'python3'
symbolic-
I think I've encountered a bug in PyQt v4.8.1 when loading Boolean types via
QSettings. I'm also using SIP v4.11.2 and Python v3.1.3.
Here's the code I'm using to save the setting:
if Main.uiSettings.cbPreferSUdo.checkState() == QtCore.Qt.Unchecked :
> User.System.bPreferSUdo = False
> else
This used to work fine when my PyQt code was in Python v2 syntax. I was
using 'QVariant' when saving Boolean values and 'toBool()' when loading
them.
Now that I've upgraded my code to Python v3 syntax, 'QVariant' is gone and I
possibly shouldn't need to use 'bool()' either. Given that Python wan
After further research, not even the following code works:
User.System.bPreferSUdo = bool( str.title( oItems ) )
>
I had to use the following code, which isn't exactly pretty:
User.System.bPreferSUdo = ( oItems == True ) or ( oItems == "true" )
>
The second method takes into account that the va
I was pretty sure that you guys would have that sort of mentality and I
don't blame you for not wanting to tamper with it. I just wanted to
illustrate the point that this seems like quite a devolution from the good
old days of 'QVariant'.
___
PyQt mailin
Hi Phil
The Arch Linux developer who's responsible for maintaining the SIP and PyQt
packages has informed me that PyQt v4.8.3 won't build on his machine with
SIP v4.12.1 and Python v3.1.3.
I'm trying to update python-qt to 4.8.3, but build fails with:
> __
> Genera
Yes, I'm sorry about that. So that we don't look like complete fools, I'll
provide you with a brief explanation.
Our "python2-sip" (Python v2) and "python-sip" (Python v3) packages have
conflicting files. We decided to use the ones from "python2-sip" and then
force "python-sip" to depend on it.
