Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Greg Ewing <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > all PEPs for Py3k are due by April. > > Can we nominate one of our 2.x PEPs for promotion > to a 3000 PEP? > > If so, I'd like to nominate PEP 335 - Overloadable > Boolean Operators. Sure. That looks like something I r

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Greg Ewing <[EMAIL PROTECTED]> wrote: Phillip J. Eby wrote: > The __subclasses__ method is useful -- even more so in 3.x than in 2.x, > because in 3.x there are no classic classes. For security purposes, I think it would be better to adopt a principle that it shouldn't be possible

Re: [Python-3000] Reminder: Py3k PEPs due by April

Guido van Rossum wrote: > all PEPs for Py3k are due by April. Can we nominate one of our 2.x PEPs for promotion to a 3000 PEP? If so, I'd like to nominate PEP 335 - Overloadable Boolean Operators. -- Greg ___ Python-3000 mailing list Python-3000@python

Re: [Python-3000] Reminder: Py3k PEPs due by April

Phillip J. Eby wrote: > The __subclasses__ method is useful -- even more so in 3.x than in 2.x, > because in 3.x there are no classic classes. For security purposes, I think it would be better to adopt a principle that it shouldn't be possible to do anything dangerous merely by instantiating a c

Re: [Python-3000] Reminder: Py3k PEPs due by April

Raymond Hettinger wrote: > Here's that I think might not need a PEP: > > * Eliminate implicit string concatenation: "abc" "def" > in favor of an explicit + operation. -0.707. I've used languages where the only way of splitting a string over lines is to use concatenation, and it's tedious. > W

Re: [Python-3000] Fwd: Re: Reminder: Py3k PEPs due by April

Raymond Hettinger <[EMAIL PROTECTED]> wrote: > > there are subtle issues like > > > > ('hello %s' > >'world' % 42) > > Thank goodness the % formatting operator is going away. Having the > same precendence as the modulo-operation has not been a good thing. Did I miss a PEP somewhere? - J

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Steven Bethard <[EMAIL PROTECTED]> wrote: On 4/10/07, Brett Cannon <[EMAIL PROTECTED]> wrote: > And I still expect a named tuple implementation in the collections module. Fortunately, Raymond borrowed the time machine already:: Python 2.6a0 (trunk:54711M, Apr 6 2007, 23:48:33) [MS

Re: [Python-3000] Reminder: Py3k PEPs due by April

At 12:25 PM 4/10/2007 -0700, Brett Cannon wrote: >On 4/10/07, Phillip J. Eby ><[EMAIL PROTECTED]> wrote: >>At 12:03 PM 4/10/2007 -0700, Brett Cannon wrote: >> >2. Remove file.__init__, code.__init__, and object.__subclasses__ for >> >security reasons. >> >>The __subclasse

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Brett Cannon <[EMAIL PROTECTED]> wrote: > And I still expect a named tuple implementation in the collections module. Fortunately, Raymond borrowed the time machine already:: Python 2.6a0 (trunk:54711M, Apr 6 2007, 23:48:33) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote: At 12:03 PM 4/10/2007 -0700, Brett Cannon wrote: >2. Remove file.__init__, code.__init__, and object.__subclasses__ for >security reasons. The __subclasses__ method is useful -- even more so in 3.x than in 2.x, because in 3.x there are no cl

Re: [Python-3000] Reminder: Py3k PEPs due by April

At 12:03 PM 4/10/2007 -0700, Brett Cannon wrote: >2. Remove file.__init__, code.__init__, and object.__subclasses__ for >security reasons. The __subclasses__ method is useful -- even more so in 3.x than in 2.x, because in 3.x there are no classic classes. I was planning to make use of this in m

[Python-3000] Fwd: Re: Reminder: Py3k PEPs due by April

> there are subtle issues like > > ('hello %s' >'world' % 42) Thank goodness the % formatting operator is going away. Having the same precendence as the modulo-operation has not been a good thing. Raymond --- Begin Message --- On 4/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: Th

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: Thanks for the reminder. I expect to write two: * PEP to eliminate __del__ in favor of weakref idioms Woohoo! And I still expect a named tuple implementation in the collections module. =) -Brett

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: As I stated in my PyCon keynote and repeated (though somewhat hidden) in PEP 3000, all PEPs for Py3k are due by April. The end of April is only a few weeks away, so now is the time to start drafting that PEP if you care about Python 3000! T

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Raymond Hettinger <[EMAIL PROTECTED]> wrote: > Thanks for the reminder. I expect to write two: > > * PEP to eliminate __del__ in favor of weakref idioms > > * PEP on simpler alternative to abstract-base-classes > suggesting an occasional method special attribute > (so for instance a __

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Steven Bethard <[EMAIL PROTECTED]> wrote: > On 4/10/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > As I stated in my PyCon keynote and repeated (though somewhat hidden) > > in PEP 3000, all PEPs for Py3k are due by April. The end of April is > > only a few weeks away, so now is the

Re: [Python-3000] Reminder: Py3k PEPs due by April

Thanks for the reminder. I expect to write two: * PEP to eliminate __del__ in favor of weakref idioms * PEP on simpler alternative to abstract-base-classes suggesting an occasional method special attribute (so for instance a __getitem__ method can tell you whether it thinks it is a sequence or m

Re: [Python-3000] Reminder: Py3k PEPs due by April

On 4/10/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > As I stated in my PyCon keynote and repeated (though somewhat hidden) > in PEP 3000, all PEPs for Py3k are due by April. The end of April is > only a few weeks away, so now is the time to start drafting that PEP > if you care about Python 30

[Python-3000] Reminder: Py3k PEPs due by April

As I stated in my PyCon keynote and repeated (though somewhat hidden) in PEP 3000, all PEPs for Py3k are due by April. The end of April is only a few weeks away, so now is the time to start drafting that PEP if you care about Python 3000! This is so that we will be able to concentrate on *implement