[Python-Dev] Reorganize Python categories (Core, Library, ...)?

Barry Warsaw barry at python.org
Wed Oct 4 09:39:21 EDT 2017

On Oct 4, 2017, at 05:52, Victor Stinner <victor.stinner at gmail.com> wrote:

> My problem is that almost all changes go into "Library" category. When
> I read long changelogs, it's sometimes hard to identify quickly the
> context (ex: impacted modules) of a change.
> It's also hard to find open bugs of a specific module on
> bugs.python.org, since almost all bugs are in the very generic
> "Library" category. Using full text returns "false positives".
> It's hard to find categories generic enough to not only contain a
> single item, but not contain too many items neither. Other ideas:
> * XML: xml.doc, xml.etree, xml.parsers, xml.sax modules
> * Import machinery: imp and importlib modules
> * Typing: abc and typing modules

I often run into the same problem.  If we’re going to split up the Library section, then I think it makes sense to follow the top-level organization of the library manual:


That already provides a mapping from module to category, and for the most part it’s a taxonomy that makes sense and is time proven.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171004/bd86460e/attachment.sig>

More information about the Python-Dev mailing list