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/2015-September/141513.html below:

[Python-Dev] Choosing an official stance towards module deprecation in Python 3

[Python-Dev] Choosing an official stance towards module deprecation in Python 3 [Python-Dev] Choosing an official stance towards module deprecation in Python 3Donald Stufft donald at stufft.io
Tue Sep 8 19:35:44 CEST 2015
On September 8, 2015 at 1:29:58 PM, Brett Cannon (bcannon at 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
> modules are still being maintained. Plus we would have to figure out who is
> in charge of the actual project on PyPI since there isn't a concept of
> group ownership.
> 

I don't really much care which way it is done, I was just throwing it out there
as a possibility. Though I think the first problem is solvable by clear
documentation. Actually in Django's case I think it was "Ok we've removed it,
if somebody wants to step up and maintain it they can, otherwise it's going to
wither and die on it's own", but my memory might be faulty. The second problem
is easier, you can add multiple people to a project, and "Organization/Group"
accounts will be something that gets implemented in Warehouse.


-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA


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