On 15/08/13 01:08, Brett Cannon wrote:
On Tue, Aug 13, 2013 at 10:22 PM, Steven D'Aprano <st...@pearwood.info>wrote:
On 13/08/13 23:36, Brett Cannon wrote:
On Tue, Aug 13, 2013 at 6:34 AM, Serhiy Storchaka <storch...@gmail.com
wrote:
12.08.13 22:22, Brett Cannon написав(ла):
I have created
http://bugs.python.org/****issue18716<http://bugs.python.org/**issue18716>
<http://bugs.python.**org/issue18716 <http://bugs.python.org/issue18716>>to
deprecate the
formatter module for removal in Python 3.6 unless someone convinces me
otherwise that deprecation and removal is the wrong move.
[...]
There is a balance to keeping the
load of work for core devs at a level that is tenable to the level of
quality we expect from ourselves which means making sure we don't let cruft
build up in the stdlib and overwhelm us.
These are all very good arguments, for both sides, and it is a balance between code churn
and bit rot, but on balance I'm going to come down firmly in favour of Nick's earlier
recommendation: PendingDeprecation (and/or a move to a "Legacy" section in the
docs). In a couple more releases there may be concrete plans for an eventual Python 4, at
which time we can discuss whether to delay deprecation until Python 4 or drop it sooner.
And in the meantime, perhaps somebody will decide to give the module some love
and attention. I'm not able to give a commitment to do so right now, but it is
a module that interests me so maybe it will be me, he says optimistically.
--
Steven
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
