Re: [Python-3000] A plus for naked unbound methods

2008-10-06 Thread Mark Seaborn
Terry Reedy <[EMAIL PROTECTED]> wrote: > I have seen a couple of objections to leaving unbound methods naked (as > functions) when retrieved in 3.0. Here is a plus. > > A c.l.p poster reported that 2.6 broke his code because the addition of > default rich comparisons to object turned tests like

Re: [Python-3000] A plus for naked unbound methods

2008-10-06 Thread Terry Reedy
Mark Seaborn wrote: Terry Reedy <[EMAIL PROTECTED]> wrote: I have seen a couple of objections to leaving unbound methods naked (as functions) when retrieved in 3.0. Here is a plus. A c.l.p poster reported that 2.6 broke his code because the addition of default rich comparisons to object tur

Re: [Python-3000] A plus for naked unbound methods

2008-10-06 Thread Mark Seaborn
Terry Reedy <[EMAIL PROTECTED]> wrote: > Mark Seaborn wrote: > > Terry Reedy <[EMAIL PROTECTED]> wrote: > > > >> I have seen a couple of objections to leaving unbound methods naked (as > >> functions) when retrieved in 3.0. Here is a plus. > >> > >> A c.l.p poster reported that 2.6 broke his co

[Python-3000] Proposed Python 3.0 schedule

2008-10-06 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given what still needs to be done, is this a reasonable schedule? Do we n

Re: [Python-3000] Proposed Python 3.0 schedule

2008-10-06 Thread Benjamin Peterson
On Mon, Oct 6, 2008 at 7:47 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > So, we need to come up with a new release schedule for Python 3.0. My > suggestion: > > 15-Oct-2008 3.0 beta 4 > 05-Nov-2008 3.0 rc 2 > 19-Nov-2008 3.0 rc 3 > 03-Dec-2008 3

Re: [Python-3000] A plus for naked unbound methods

2008-10-06 Thread Terry Reedy
Mark Seaborn wrote: Terry Reedy <[EMAIL PROTECTED]> wrote: Mark Seaborn wrote: Terry Reedy <[EMAIL PROTECTED]> wrote: I have seen a couple of objections to leaving unbound methods naked (as functions) when retrieved in 3.0. Here is a plus. A c.l.p poster reported that 2.6 broke his code b

Re: [Python-3000] [Python-Dev] Proposed Python 3.0 schedule

2008-10-06 Thread Raymond Hettinger
[Barry Warsaw] So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given what still needs to be done, is this a reasonable schedule? Do we need two more betas? Yes to bot

Re: [Python-3000] [Python-Dev] Proposed Python 3.0 schedule

2008-10-06 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 6, 2008, at 9:48 PM, Raymond Hettinger wrote: [Barry Warsaw] So, we need to come up with a new release schedule for Python 3.0. My suggestion: 15-Oct-2008 3.0 beta 4 05-Nov-2008 3.0 rc 2 19-Nov-2008 3.0 rc 3 03-Dec-2008 3.0 final Given w

Re: [Python-3000] Proposed Python 3.0 schedule

2008-10-06 Thread James Y Knight
On Oct 6, 2008, at 8:52 PM, Benjamin Peterson wrote: I'm not sure we do. Correct me if I'm wrong, but the "big ticket", issue bytes/unicode filepaths, has been resolved. And looking at the tracker, I only see 18 release blockers. Well, if you mean that the resolution decided upon is to "simply

Re: [Python-3000] [Python-Dev] Filename as byte string in python 2.6 or 3.0?

2008-10-06 Thread Adam Olsen
On Mon, Oct 6, 2008 at 5:12 PM, Glenn Linderman <[EMAIL PROTECTED]> wrote: > On approximately 10/3/2008 11:57 PM, came the following characters from the > keyboard of Adam Olsen: >> On Fri, Oct 3, 2008 at 10:14 PM, Glenn Linderman <[EMAIL PROTECTED]> >> wrote: >>> Alternative 3: Portable programs u

Re: [Python-3000] [Python-Dev] Filename as byte string in python 2.6 or 3.0?

2008-10-06 Thread Adam Olsen
On Mon, Oct 6, 2008 at 11:23 PM, Glenn Linderman <[EMAIL PROTECTED]> wrote: > On approximately 10/6/2008 10:18 PM, came the following characters from the > keyboard of Adam Olsen: >> But "Unicode" on windows is invalid. It shares all the same problems >> UTF-8b does, but worse as a correct UTF-16