Author ncoghlan
Recipients docs@python, ncoghlan
Date 2013-09-07.13:09:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378559362.61.0.726437189184.issue18959@psf.upfronthosting.co.za>
In-reply-to
Content
As discussed at the language summit earlier this year [1], it isn't alway easy to tell when glancing through the standard library docs which modules are merely hanging around because removing them would break backwards compatibility.

However, after reviewing the current ToC, we currently appear to only have two genuinely superseded modules: optparse (superseded by argparse) and imp (superseded by importlib).

Other cases where different modules touch on the same area are high level/low level splits (e.g. select vs selectors), or ones where the alternate modules are offering compatibility with different styles of API (e.g. etree vs DOM for XML, getopt vs argparse).

In future, asyncore/asynchat will hopefully be superseded by the PEP 3156 code (as "concurrent.events" or similar) and would also be moved under the new heading.

Marking as "easy" since the mechanics of the patch should be pretty simple: create a new heading and move the references to optparse and imp from their current locations.

[1] http://python-notes.boredomandlaziness.org/en/latest/conferences/pyconus2013/20130313-language-summit.html#legacy-modules

(I thought I had already created a bug for this, but can't find it, so I've created this new one. If I did already create an issue, we can close it as a duplicate and keep this one.)
History
Date User Action Args
2013-09-07 13:09:22ncoghlansetrecipients: + ncoghlan, docs@python
2013-09-07 13:09:22ncoghlansetmessageid: <1378559362.61.0.726437189184.issue18959@psf.upfronthosting.co.za>
2013-09-07 13:09:22ncoghlanlinkissue18959 messages
2013-09-07 13:09:21ncoghlancreate