1. PyPA
  2. Python Packaging Authority Projects
  3. pypi
  4. Issues


Issue #167 wontfix

Request for new trove classifiers: Django versions

created an issue

I found this list: https://pypi.python.org/pypi?%3Aaction=list_classifiers

I assumed it was a list of suggestions to avoid people creating duplicates etc, setting out a format. But it seems a hard coded list that setup.py classifiers are validated against when uploading to PyPI.

In that case it's weird that Django only gets a single entry "Framework :: Django", while something called 'Plone' gets a bunch of specific versions.

If trove classifiers are useful for anything (?) then I guess it would be useful for authors of Django apps to be able to specify which versions of Django their package works against, since there can be breaking changes between point versions.

I'd suggest:

  • 1.0 (earliest tag on github)
  • 1.1
  • 1.2
  • 1.3
  • 1.4
  • 1.5
  • 1.6
  • 1.7

Comments (9)

  1. anentropic reporter

    To the user the classifiers present as a tagging system, in which case it's weird having a fairly arbitrary hard-coded list.

    Maybe they're intended more for PyPI admins to get some stats about the repository...

    Still, as long as they're arranged hierarchically I don't see how it can be a misfeature to add child classifiers. The stats can still be rolled up into the parent but users can drill down if needed, i.e. it can only be more useful.

    Maybe it should work more like DNS where top level domains are fixed but, below that, items can be freely added.

  2. anentropic reporter

    I can appreciate that it's not worth adding new ones, in the context that the trove classifiers are not really useful or used by anybody (expect as a little ritual when writing their setup.py) ... I'm just curious if you see some potential harm in having more specific classifiers available?

    obviously if the classifiers don't exist no one will find a use for them

  3. Richard Jones

    The harm is that they're just noise if they're not used.

    Also, I tend to not add classifiers unless there is a community need for them. Apart from the original set, that is (hence oddities like BeOS).

  4. Log in to comment