Prev: bps coordinate identification
Next: Error Occurs: Replace a character in a String
From: Mensanator on 10 Apr 2010 19:47
On Apr 10, 5:45 pm, Michael Ströder <mich...(a)stroeder.com> wrote:
> average wrote:
> >> On behalf of the Python development team, I'm merry to announce the first beta
> >> release of Python 2.7.
>
> >> Python 2.7 is scheduled (by Guido and Python-dev) to be the last major version
> >> in the 2.x series.  Though more major releases have not been absolutely ruled
> >> out, it's likely that the 2.7 release will an extended period of maintenance for
> >> the 2.x series.
>
> > May I propose that the developers consider keeping this release *beta*
> > until after the present Python moratorium?  That is, don't let it be
> > marked as *official* until after, say, Python 3.3.
>
> > There are so many features taken from 3.0 that I fear that it will
> > postpone its adoption interminably
>
> Whether 3.x is adopted by developers is IMO not influenced by the 2.7 release
> schedule. At least the effect is highly speculative. So please simply release
> 2.7 when it's ready.

3.x won't be adopted by developers until it's fixed. As of now, it's
seriously broken and unsuitable for production.

>
> Ciao, Michael.

From: Chris Rebert on 10 Apr 2010 20:15
On Sat, Apr 10, 2010 at 4:47 PM, Mensanator <mensanator(a)aol.com> wrote:
> On Apr 10, 5:45 pm, Michael Ströder <mich...(a)stroeder.com> wrote:
>> average wrote:
>> >> On behalf of the Python development team, I'm merry to announce the first beta
>> >> release of Python 2.7.
>>
>> >> Python 2.7 is scheduled (by Guido and Python-dev) to be the last major version
>> >> in the 2.x series.  Though more major releases have not been absolutely ruled
>> >> out, it's likely that the 2.7 release will an extended period of maintenance for
>> >> the 2.x series.
>>
>> > May I propose that the developers consider keeping this release *beta*
>> > until after the present Python moratorium?  That is, don't let it be
>> > marked as *official* until after, say, Python 3.3.
>>
>> > There are so many features taken from 3.0 that I fear that it will
>> > postpone its adoption interminably
>>
>> Whether 3.x is adopted by developers is IMO not influenced by the 2.7 release
>> schedule. At least the effect is highly speculative. So please simply release
>> 2.7 when it's ready.
>
> 3.x won't be adopted by developers until it's fixed. As of now, it's
> seriously broken and unsuitable for production.

In what ways do you consider it broken?

Cheers,
Chris
From: Mensanator on 11 Apr 2010 00:08
On Apr 10, 7:15�pm, Chris Rebert <c...(a)rebertia.com> wrote:
> On Sat, Apr 10, 2010 at 4:47 PM, Mensanator <mensana...(a)aol.com> wrote:
> > On Apr 10, 5:45�pm, Michael Str�der <mich...(a)stroeder.com> wrote:
> >> average wrote:
> >> >> On behalf of the Python development team, I'm merry to announce the first beta
> >> >> release of Python 2.7.
>
> >> >> Python 2.7 is scheduled (by Guido and Python-dev) to be the last major version
> >> >> in the 2.x series. �Though more major releases have not been absolutely ruled
> >> >> out, it's likely that the 2.7 release will an extended period of maintenance for
> >> >> the 2.x series.
>
> >> > May I propose that the developers consider keeping this release *beta*
> >> > until after the present Python moratorium? �That is, don't let it be
> >> > marked as *official* until after, say, Python 3.3.
>
> >> > There are so many features taken from 3.0 that I fear that it will
> >> > postpone its adoption interminably
>
> >> Whether 3.x is adopted by developers is IMO not influenced by the 2.7 release
> >> schedule. At least the effect is highly speculative. So please simply release
> >> 2.7 when it's ready.
>
> > 3.x won't be adopted by developers until it's fixed. As of now, it's
> > seriously broken and unsuitable for production.
>
> In what ways do you consider it broken?

Issue 8093. Remarkably, this apparently hasn't been noticed before.
I expect 2.7 will be around for a long time.

>
> Cheers,
> Chris- Hide quoted text -
>
> - Show quoted text -

From: alex23 on 11 Apr 2010 00:51
Mensanator <mensana...(a)aol.com> wrote:
> 3.x won't be adopted by WINDOWS developers WHO USE IDLE until it's fixed.

I think you left your hyperbole level too high so I turned it down for
you. I don't know of _anyone_ who uses IDLE to run production code,
nor do I follow how one errant IDE shows that Python 3.x as a language
is broken.
From: Mensanator on 11 Apr 2010 11:03
On Apr 10, 11:51�pm, alex23 <wuwe...(a)gmail.com> wrote:
> Mensanator <mensana...(a)aol.com> wrote:
> > 3.x won't be adopted by WINDOWS developers WHO USE IDLE until it's fixed.
>
> I think you left your hyperbole level too high so I turned it down for
> you. I don't know of _anyone_ who uses IDLE to run production code,
> nor do I follow how one errant IDE shows that Python 3.x as a language
> is broken.

Planning to buy a Toyota?
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: bps coordinate identification
Next: Error Occurs: Replace a character in a String