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 333 - QChar enums missing
: QChar enums missing
Status: CLOSED INVALID
Product: PySide
Classification: Unclassified
Component: QtCore
: HEAD
: All All
: P5 normal
Assigned To: renato filho
:
:
:
  Show dependency treegraph
 
Reported: 2010-09-01 07:35 EEST by Matti Airas
Modified: 2010-09-10 19:26 EEST (History)
8 users (show)

See Also:


Attachments
A silly testcase (92 bytes, text/x-python)
2010-09-01 07:35 EEST, Matti Airas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matti Airas 2010-09-01 07:35:00 EEST
QChar has been removed when PSEP 101 was implemented. This had one awkward
consequence: also the enums are gone. For example, the example textobject.py
refers to QtCore.QChar.ObjectReplacementCharacter, which does not exist any
more.

What to do? :-) Should the enums be still retained even though QChar itself is
gone?
Comment 1 Matti Airas 2010-09-01 07:35:52 EEST
Created attachment 75 [details]
A silly testcase
Comment 2 Matti Airas 2010-09-01 07:49:31 EEST
Comparing to PyQt, they don't implement the enums either:

        try:
            # Python v2.
            orc = unichr(0xfffc)
        except NameError:
            # Python v3.
            orc = chr(0xfffc)
Comment 3 Hugo Parente Lima 2010-09-01 10:59:02 EEST
Most functions of QChar can be found in unicodedata object in python, although
I didn't find a constant in Python for this character, maybe I didn't search
enough or maybe this constant just doesn't exists in python libs.

IMO exporting the QChar enums without a QChar class will just confuse the
people, besides the only missing part is this constant.
Comment 4 Matti Airas 2010-09-01 12:15:53 EEST
Fair enough, just wanted to hear your opinion. I'm resolving this as WONTFIX.
Or should it rather be invalid?
Comment 5 Hugo Parente Lima 2010-09-01 14:28:12 EEST
Invalid, it's not a bug or exceptional behaviour.