> Therefore, as you imply, I think the solution to this issue is to start > the process of deprecating the bytes version of the api in py3k with a > view to removing it completely - possibly with a less aggressive > timeline than normal. In Python 2.7, I think documenting the issue and > a recommendation to always use unicode is sufficient (ie, we can't > deprecate it and a new BytesWarning seems gratuitous.) That sounds all fine to me. Regards, Martin
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