Re: [Python-3000] to be merged

2008-07-06 Thread Josiah Carlson
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 the

Re: [Python-3000] to be merged

2008-07-03 Thread Nick Coghlan
Benjamin Peterson wrote: On Wed, Jul 2, 2008 at 6:58 PM, Bill Janssen <[EMAIL PROTECTED]> wrote: P.S. Can people please remember to block commits that shouldn't be merged into 3.0? Can you remind me how to do that? Thanks. Certainly! Just run "svnmerge block -r [a revision]" [1] in your py3k

Re: [Python-3000] to be merged

2008-07-02 Thread Benjamin Peterson
On Wed, Jul 2, 2008 at 6:58 PM, Bill Janssen <[EMAIL PROTECTED]> wrote: >> P.S. Can people please remember to block commits that shouldn't be >> merged into 3.0? > > Can you remind me how to do that? Thanks. Certainly! Just run "svnmerge block -r [a revision]" [1] in your py3k working copy and th

Re: [Python-3000] to be merged

2008-07-02 Thread Bill Janssen
> P.S. Can people please remember to block commits that shouldn't be > merged into 3.0? Can you remind me how to do that? Thanks. Bill ___ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe:

Re: [Python-3000] to be merged

2008-07-02 Thread Benjamin Peterson
P.S. Can people please remember to block commits that shouldn't be merged into 3.0? (Or even better, merge the ones you make that should.) I feel rather nervous deciding whether something should be merged or not when it's an edge case. -- Cheers, Benjamin Peterson "There's no place like 127.0.0.

Re: [Python-3000] to be merged

2008-07-02 Thread Benjamin Peterson
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 s

Re: [Python-3000] to be merged

2008-07-02 Thread Josiah Carlson
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 stil

Re: [Python-3000] to be merged

2008-07-02 Thread Josiah Carlson
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. Jo

Re: [Python-3000] to be merged

2008-07-02 Thread Bill Janssen
> - SSL changes I've been maintaining the Lib/ssl.py, Lib/test/test_ssl.py and Modules/_ssl.c files separately for the two trees. I think the underlying changes in socket.py, and the IO subsystem, still make this a good idea, but I'm willing to be convinced differently. There's yet a third varia

Re: [Python-3000] to be merged

2008-07-02 Thread Guido van Rossum
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. Jo