Just a heads up (primarily for Georg and Larry): I've started marking some issues as release blockers for 3.4 (currently just the bytes-bytes/str-str transform() API and the set_encoding() method discussed recently on python-ideas). These are important gaps identified in the new Unicode handling model, and we should make sure to review and discuss them well in advance of 3.4 being released. Those are the only two I've identified so far where that course of action has seemed appropriate - most of the time for this kind of thing, I'd just assign the issue to myself to take a look at after the feature freeze is over or else bump the priority up to high. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
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