On Wed, Jul 2, 2008 at 5:50 PM, Josiah Carlson <[EMAIL PROTECTED]> wrote: > > I'm in the process of doing the conversion. asyncore.py was no > problem, but asynchat.py relies heavily on the 2.x buffer() object > (specifically the slicing aspects thereof), which went away, to be > replaced by the seemingly incomplete memoryview object. Are > memoryviews going to be gaining slicing ability (in the case of > 1-dimensional memory views, which also have step forced to 1)? Are we > just waiting for an implementation? Or because of the ability to > offer a memoryview into just about any object now, "slicing" only some > objects (1-dimensional in particular) breaks consistency for all other > objects?
It's in the PEP [1]. However, we've had the unfortunate experience of finding that much of the PEP hasn't been implemented. [1] http://www.python.org/dev/peps/pep-3118/ > > - Josiah > -- Cheers, Benjamin Peterson "There's no place like 127.0.0.1." _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
