This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zach.ware
Recipients ezio.melotti, mike lojkovic, vstinner, zach.ware
Date 2019-07-09.22:01:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562709720.17.0.359301159801.issue37533@roundup.psfhosted.org>
In-reply-to
Content
That issue shows a traceback from Python 2.7, which handles Unicode significantly differently than (read "not as well as") Python 3.  If the issue can be boiled down to a few lines of Python code that show a real problem in Python 3's Unicode handling (rather than in Tribler or PyQT) please reopen, but for now I see no indication that this is a problem in Python 3.  The chances of changing Python 2's Unicode handling in any meaningful way at this point in its lifecycle are nearly nil.
History
Date User Action Args
2019-07-09 22:02:00zach.waresetrecipients: + zach.ware, vstinner, ezio.melotti, mike lojkovic
2019-07-09 22:02:00zach.waresetmessageid: <1562709720.17.0.359301159801.issue37533@roundup.psfhosted.org>
2019-07-09 22:02:00zach.warelinkissue37533 messages
2019-07-09 22:01:59zach.warecreate