Nick Coghlan added the comment:

I just wanted to note something I realised in chatting to Armin Ronacher 
recently: in both Python 2.x and 3.x, the encode/decode method APIs are 
constrained by the text model, it's just that in 2.x that model was effectively 
basestring<->basestring, and thus still covered every codec in the standard 
library. This greatly limited the use cases for the codecs.encode/decode 
convenience functions, which is why the fact they were undocumented went 
unnoticed.

In 3.x, the changed text model meant the method API become limited to the 
Unicode codecs, making the function based API more important.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue7475>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to