On 7/20/07, Blake Winton <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > >> While the pickle/cPickle, StringIO/cStringIO, etc., naming can be > >> a bit annoying, it does give me the choice whether I want it to be > >> fast or flexible. > > I definitely *don't* want to continue the old habit of having a slow > > and a fast module with different names; the experience with especially > > cPickle and cStringIO is that everyone believes their code is > > performance critical and hence uses the C version if it exists, > > thereby repeating the same idiom over and over. > > Until they need to turn Unicode strings into file-like objects, at which > point they go back to StringIO. (Why yes, I was recently bitten by that > particular "restriction". :)
Py3k will have separate BytesIO and StringIO classes (both in the io module). The accelerations, if any, will be transparent. Subclasses or usage depending on implementation details however are not supported. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
