2014-10-10 2:52 GMT+02:00 Jesus Cea <jcea at jcea.es>: > "Yes, Python 2 is broken, the real deal is Python 3"? :). For Unicode, my favorite answer is "it's time to upgrade! Python 3 has a much better Unicode support." and not fix the issue on Python 2.7. I don't want to open the can of worm "unicode" in Python 2. I don't want to redo all the work I already did on Python 3. For the specific case of the new codec, I don't know. It will be easier to decide when the bug will be fully fixed in Python 3.5, to see the size of the changeset. Victor
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4