On May 06, 2010, at 09:33 PM, Benjamin Peterson wrote:
>I don't think there's any point in being hypothetical about. I believe
>we've already said that maintence for 2.7 will last for at least 5
>years, so let's proclaim it.
+1. If our goal is to move our community to Python 3, then I think we d
A.M. Kuchling wrote:
> On Fri, May 07, 2010 at 07:52:49PM +1000, Nick Coghlan wrote:
>> 3.x). I'll take a stab at a more accurate rationale:
>
> Thanks! I've applied the scalpel and reduced it to:
I saw this go by on the checkin list - looks good (although Philip is
right about mentioning PYTHON
A.M. Kuchling wrote:
> On Fri, May 07, 2010 at 09:30:00AM +0200, "Martin v. Löwis" wrote:
>> I agree with Terry: how did you arrive at the 4 years for 2.x releases?
>> Bug fixes releases stopped after the next feature release being made,
>> which gave (counting between initial release and last bug
On May 7, 2010, at 9:09 AM, A.M. Kuchling wrote:
> You can re-enable display of :exc:`DeprecationWarning` messages by
> running Python with the :option:`-Wdefault` (short form:
> :option:`-Wd`) switch, or you can add
> ``warnings.simplefilter('default')`` to your code.
The new PYTHONWARNINGS
On Fri, May 7, 2010 at 09:09, A.M. Kuchling wrote:
> On Fri, May 07, 2010 at 07:52:49PM +1000, Nick Coghlan wrote:
> > 3.x). I'll take a stab at a more accurate rationale:
>
> Thanks! I've applied the scalpel and reduced it to:
>
> * A policy decision was made to silence warnings only of interes
On Fri, May 07, 2010 at 07:52:49PM +1000, Nick Coghlan wrote:
> 3.x). I'll take a stab at a more accurate rationale:
Thanks! I've applied the scalpel and reduced it to:
* A policy decision was made to silence warnings only of interest to
developers by default. :exc:`DeprecationWarning` and it
On Fri, May 07, 2010 at 09:30:00AM +0200, "Martin v. Löwis" wrote:
> I agree with Terry: how did you arrive at the 4 years for 2.x releases?
> Bug fixes releases stopped after the next feature release being made,
> which gave (counting between initial release and last bug fix release):
I used the
Terry Reedy wrote:
> Then the warnings stuff
>>
>> * Because 2.7 will be running production applications, a policy
>
> Every major version (xcept 3.0) has run production application, and 3.1
> may be and 3.2 certainly will be. So this reasoning is not clear to me.
>
>>decision was made to sil
> * It's very likely the 2.7 release will have a longer period of
> maintenance compared to earlier 2.x versions. Python 2.7 will
> continue to be maintained while the transition to 3.x is in
> progress, and that transition will itself be lengthy. Most 2.x
> versions are maintained for ab
On 5/6/2010 9:50 PM, A.M. Kuchling wrote:
FYI: I've just added the text below to the "What's New" document for
2.7. I wanted to describe how 2.7 will probably be maintained, but
didn't want to write anything that sounded like an iron-clad guarantee
of a maintenance timespan. Does this text seem
2010/5/6 A.M. Kuchling :
> FYI: I've just added the text below to the "What's New" document for
> 2.7. I wanted to describe how 2.7 will probably be maintained, but
> didn't want to write anything that sounded like an iron-clad guarantee
> of a maintenance timespan. Does this text seem like a rea
"A.M. Kuchling" writes:
> FYI: I've just added the text below to the "What's New" document for
> 2.7. I wanted to describe how 2.7 will probably be maintained, but
> didn't want to write anything that sounded like an iron-clad guarantee
> of a maintenance timespan. Does this text seem like a reas
On Thu, May 6, 2010 at 6:50 PM, A.M. Kuchling wrote:
> FYI: I've just added the text below to the "What's New" document for
> 2.7. I wanted to describe how 2.7 will probably be maintained, but
> didn't want to write anything that sounded like an iron-clad guarantee
> of a maintenance timespan. D
FYI: I've just added the text below to the "What's New" document for
2.7. I wanted to describe how 2.7 will probably be maintained, but
didn't want to write anything that sounded like an iron-clad guarantee
of a maintenance timespan. Does this text seem like a reasonable set
of statements?
--amk
14 matches
Mail list logo
