On Wed, Jul 2, 2008 at 3:50 PM, Josiah Carlson <[EMAIL PROTECTED]> wrote: > On Wed, Jul 2, 2008 at 1:57 PM, Josiah Carlson <[EMAIL PROTECTED]> wrote: >> On Wed, Jul 2, 2008 at 1:17 PM, Benjamin Peterson >> <[EMAIL PROTECTED]> wrote: >>> I just merged a good chunk of the trunk -> py3k queue, but there are >>> still some things to be dealt with: >>> >>> - bsddb It seesm bsddb still has yet to be ported to Py3k. See #2887. >>> >>> - The asyncore/asynchat patches. Josiah, can you do this? >>> >>> - The Mac 4-way arch build. >>> >>> - The bin/hex/oct float things. (These can just be blocked, right?) >>> >>> - SSL changes >> >> I will try with asyncore/asynchat, but I have no experience with py3k >> or the 2to3 converter. > > 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?
See changelist 64764 that updates asyncore, asynchat, and smtpd (which also required changes), their tests, and documentation. - Josiah _______________________________________________ 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
