Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request trove classifiers for ASGI #13

Open
michael-k opened this issue Dec 23, 2019 · 1 comment
Open

Request trove classifiers for ASGI #13

michael-k opened this issue Dec 23, 2019 · 1 comment
Labels
new classifier request Request for a new classifier

Comments

@michael-k
Copy link

michael-k commented Dec 23, 2019

Request to add a new Trove classifier.

The name of the classifiers you would like to add

  • Topic :: Internet :: WWW/HTTP :: ASGI
  • Topic :: Internet :: WWW/HTTP :: ASGI :: Application
  • Topic :: Internet :: WWW/HTTP :: ASGI :: Middleware
  • Topic :: Internet :: WWW/HTTP :: ASGI :: Server

Why do you want to add these classifiers?

  • The same classifiers exist for WSGI.
  • async/asyncio gains more and more popularity in the Python community. In a few days Python 2.7 will finally reach its EOL and then all supported versions of Python support asyncio.
  • Django 3.0 is the first release of Django with basic async support, continuing the work started with channels back in 2015. Django is very conservative when it comes to new features and even they decided to support async.
  • There's a spec: https://github.com/django/asgiref/
  • There are (at least) three servers: https://asgi.readthedocs.io/en/latest/implementations.html#servers
@jamadden jamadden transferred this issue from pypi/warehouse Jan 6, 2020
@jamadden
Copy link
Member

Hi! Thanks for the well written request. The PyPI moderators have a few guidelines for the creation of new classifiers. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, the bar to add new ones is relatively high. Currently, the guidelines state:

  • New classifiers should be created if they are "notable;" and
  • They will be of immediate use to existing projects (in other words, no creating classifiers simply in anticipation of future uses)

We understand that "notability" is subjective and we'd appreciate help judging that; the information you've already provided goes a long way towards satisfying that, but it still essentially seems limited to one particular application framework.

As to the other guideline ('immediate use to existing projects'), the best way we've found to demonstrate that would be to have 10 or more other project maintainers submit comments on the requesting issue about their desire to use the classifier.

The same classifiers exist for WSGI.

I only see one similar classifier for WSGI, Topic :: Internet :: WWW/HTTP :: WSGI. It doesn't seem to have any further sub-classifiers. Adding just one classifier is a somewhat easier bar to clear.

@di di transferred this issue from pypi/support Apr 4, 2020
@pradyunsg pradyunsg added the new classifier request Request for a new classifier label Apr 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new classifier request Request for a new classifier
Projects
None yet
Development

No branches or pull requests

3 participants