Re: [Python-3000] PEPs 3xxx status

2007-02-17 Thread Eduardo \"EdCrypt\" O. Padoan
On 2/17/07, Talin <[EMAIL PROTECTED]> wrote: > I don't know about the others, however I want to speak to the issue of > 3101 and 3102, since I wrote them - the main reason that those PEPs > haven't been accepted is that there's no sample implementation to > evaluate. (At least, I'm not aware of any

Re: [Python-3000] PEPs 3xxx status

2007-02-17 Thread Guido van Rossum
And it's in the p3yk branch, too. The main reason these are all still drafts is that I expect that implementing them may cause a certain amount of redesign, and in some cases the spec isn't entirely clear. The "real" acceptance status (in my head) is all over the map -- 3102 is obviously accepted,

Re: [Python-3000] PEPs 3xxx status

2007-02-17 Thread Georg Brandl
Guido van Rossum schrieb: > And it's in the p3yk branch, too. > > The main reason these are all still drafts is that I expect that > implementing them may cause a certain amount of redesign, and in some > cases the spec isn't entirely clear. The "real" acceptance status (in > my head) is all over

[Python-3000] immutable classes [was: pre-PEP: Default Argument Expressions]

2007-02-17 Thread Jim Jewett
I have added python-ideas to the Cc list, and suggest removing python-3000 from additional replies. BJörn Lindqvist gave an example explaining why he might want to re-evaluate mutable default arguments. It still looks like like buggy code, but it isn't the error I was expecting -- and I think it