On 1/12/07, Raymond Hettinger <python at rcn.com> wrote: > [A.M. Kuchling] > > 2.6 wouldn't go changing existing APIs to begin requiring or returning > > the bytes type[*], of course, but extensions and new modules might use > > it. > > The premise is dubious. > > If I am currently maintaining a module, why would I switch to a bytes type > and forgo compatibility with Py2.5 and prior? I might as well just convert > it to run on Py3.0 and leave my Py2.5 code as-is for people who want to > run 2.x. A mutables bytes type is a useful addition to 2.X aside of the 3.0-compatibility motivation. Isn't that sufficient justification? -Mike
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