On 2/18/06, Josiah Carlson <jcarlson at uci.edu> wrote: > Look at what we've currently got going for data transformations in the > standard library to see what these removals will do: base64 module, > binascii module, binhex module, uu module, ... Do we want or need to > add another top-level module for every future encoding/codec that comes > out (or does everyone think that we're done seeing codecs)? Do we want > to keep monkey-patching binascii with names like 'a2b_hqx'? While there > is currently one text->text transform (rot13), do we add another module > for text->text transforms? Would it start having names like t2e_rot13() > and e2t_rot13()? If top-level modules are the problem then why not make codecs into a package? from codecs import utf8, base64 utf8.encode(u) -> b utf8.decode(b) -> u base64.encode(b) -> b base64.decode(b) -> b -- Adam Olsen, aka Rhamphoryncus
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