Bug 718 – PySide/PyQt4 QByteArray incompatibilities: setNum method

PySide Bugzilla Closed for New Bugs

PySide is now a Qt Add-on and uses the Qt Project's JIRA Bug Tracker instead of this Bugzilla instance. This Bugzilla is left for reference purposes.

Bug 718 - PySide/PyQt4 QByteArray incompatibilities: setNum method

Summary:

PySide/PyQt4 QByteArray incompatibilities: setNum method

Status:	CLOSED FIXED

Product:	PySide
Classification:	Unclassified
Component:	QtCore
Version:	1.0.0
Platform:	All All

Importance:	P3 normal
Assigned To:	Hugo Parente Lima

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-03-10 21:46 EET by Hugo Parente Lima
Modified:	2011-04-01 23:16 EEST (History)
CC List:	8 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Hugo Parente Lima 2011-03-10 21:46:59 EET

On PySide setNum method was renamed to setFloat, setInt, etc... and there's no
setNum method, all this was inheritance from QtJambi, but PyQt has the setNum
method causing a unnedded incompatibility.

Test code:

import PySide.QtCore
import PyQt4.QtCore

q = PyQt4.QtCore.QByteArray()
assert(q.setNum)
s = PySide.QtCore.QByteArray()
assert(s.setNum)

Comment 1 Hugo Parente Lima 2011-03-11 22:38:02 EET

I'm fixing it as part of the typesystem "remove" cleanup story, since it's
trivial to fix.

Comment 2 Hugo Parente Lima 2011-03-16 16:24:05 EET

Fixed in commit:

pyside/008798b0e3e99235d3912d885b8322710c41338b

Comment 3 Hugo Parente Lima 2011-04-01 23:16:03 EEST

Closing bug after release of PySide 1.0.1.