A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-August/127951.html below:

[Python-Dev] Deprecating the formatter module

[Python-Dev] Deprecating the formatter module [Python-Dev] Deprecating the formatter moduleTerry Reedy tjreedy at udel.edu
Wed Aug 14 20:37:07 CEST 2013
On 8/14/2013 12:09 PM, Nick Coghlan wrote:
> On 14 August 2013 11:55, Brett Cannon <brett at python.org> wrote:

>> I view a deprecation as the same thing. If we leave the module in until
>> Python 4 then I can live with that, but simply moving documentation around
>> is not enough to communicate to those who didn't read the release notes to
>> know modules they rely on are now essentially orphaned.
>
> No, a deprecation isn't enough, because it doesn't help authors and
> educators to know "this is legacy, you can skip it". We need both.

At least a couple of releases before deletion, we should put a 'legacy' 
package up on pypi. Then the deprecation message could say to use that 
as an alternative.

-- 
Terry Jan Reedy

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4