Someone else brought up warnings in Python 2.7 and my response was that you
already get the warning in Python 3 so why get it twice across different
versions?
On Fri, Sep 11, 2015, 22:48 Serhiy Storchaka wrote:
> On 08.09.15 19:59, Brett Cannon wrote:
> > The approaches to module deprecation I h
On 08.09.15 19:59, Brett Cannon wrote:
The approaches to module deprecation I have seen are:
1. Nothing changes to the deprecation process; you deprecate a module
and remove it in one to two releases
2. Deprecate the module but with no plans for removal until Python 2.7
reaches its EOL (I have be
> On Sep 11, 2015, at 1:57 PM, Brett Cannon wrote:
>
> In order to facilitate writing code that works in both Python 2 & 3
> simultaneously, any module that exists in both Python 3.5 and
> Python 2.7 will not be removed from the standard library until
> Python 2.7 is no longer supported as speci
Tweaked wording that clearly state the mere existence in both Python 2.7
and 3.5 means the module won't be removed until Python 2.7 is EOL'ed:
In order to facilitate writing code that works in both Python 2 & 3
simultaneously, any module that exists in both Python 3.5 and
Python 2.7 will not be r
+1.
The language seems a bit ambiguous: "deprecated from 3.5 onward" -- what if
a module was deprecated in 3.3 or 3.4 but still present in 3.5? I assume
those are also included, but the language makes it possible to interpret
this as applying only to modules that were first marked as deprecated in
Since everyone seems happy with the proposal to keep deprecated modules in
Python 3 until Python 2.7 reaches EOL, here are my proposed changes to PEP
4. If no one objects I will commit the change and then update formatter and
imp to say they will be removed once Python 2.7 is no longer supported.
On Tue, Sep 8, 2015 at 7:59 PM, Brett Cannon wrote:
> There are two discussions going on in the issue tracker about deprecating
> some modules and it has led to the inevitable discussion of Python 2/3
> compatibility (I'm not even going to bother mentioning the issue #s as this
> thread is not abo
On 9 September 2015 at 04:56, Brett Cannon wrote:
> On Tue, 8 Sep 2015 at 11:36 Terry Reedy wrote:
>> > The approaches to module deprecation I have seen are:
>> > 1. Nothing changes to the deprecation process; you deprecate a module
>> > and remove it in one to two releases
>> > 2. Deprecate the
On Sep 08, 2015, at 10:02 AM, Guido van Rossum wrote:
>#2 sounds fine to me.
Agreed.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/pytho
On Tue, 8 Sep 2015 at 11:36 Terry Reedy wrote:
> On 9/8/2015 12:59 PM, Brett Cannon wrote:
> > There are two discussions going on in the issue tracker about
> > deprecating some modules and it has led to the inevitable discussion of
> > Python 2/3 compatibility (I'm not even going to bother menti
On 9/8/2015 12:59 PM, Brett Cannon wrote:
There are two discussions going on in the issue tracker about
deprecating some modules and it has led to the inevitable discussion of
Python 2/3 compatibility (I'm not even going to bother mentioning the
issue #s as this thread is not about the modules sp
On September 8, 2015 at 1:29:58 PM, Brett Cannon (bcan...@gmail.com) wrote:
>
> That is one possibility, but I notice that django.contrib.comments is still
> getting updated. For deprecated modules they probably won't even get
> bugfixes anymore so I wouldn't want to give the wrong impression the
On Tue, 8 Sep 2015 at 10:08 Donald Stufft wrote:
> On September 8, 2015 at 1:01:14 PM, Brett Cannon (bcan...@gmail.com)
> wrote:
> >
> > The approaches to module deprecation I have seen are:
> > 1. Nothing changes to the deprecation process; you deprecate a module and
> > remove it in one to two
On September 8, 2015 at 1:01:14 PM, Brett Cannon (bcan...@gmail.com) wrote:
>
> The approaches to module deprecation I have seen are:
> 1. Nothing changes to the deprecation process; you deprecate a module and
> remove it in one to two releases
> 2. Deprecate the module but with no plans for remov
#2 sounds fine to me.
On Tue, Sep 8, 2015 at 9:59 AM, Brett Cannon wrote:
> There are two discussions going on in the issue tracker about deprecating
> some modules and it has led to the inevitable discussion of Python 2/3
> compatibility (I'm not even going to bother mentioning the issue #s as
There are two discussions going on in the issue tracker about deprecating
some modules and it has led to the inevitable discussion of Python 2/3
compatibility (I'm not even going to bother mentioning the issue #s as this
thread is not about the modules specifically but module deprecation in
general
16 matches
Mail list logo
