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 classifier: Framework :: aiohttp #54

Closed
asvetlov opened this issue Nov 5, 2020 · 7 comments · Fixed by #71
Closed

Request trove classifier: Framework :: aiohttp #54

asvetlov opened this issue Nov 5, 2020 · 7 comments · Fixed by #71

Comments

@asvetlov
Copy link
Contributor

asvetlov commented Nov 5, 2020

Request to add a new Trove classifier.

The name of the classifier you would like to add

Framework :: aiohttp

Why do you want to add this classifier?

https://github.com/aio-libs/aiohttp is very widely used in the Python community.
It has 13M downloads per month at the moment of writing: https://pypistats.org/packages/aiohttp
More than 50 libraries officially claim that they are built on top of aiohttp: https://docs.aiohttp.org/en/stable/third_party.html
Many more libraries exist but out of the list.
libraries.io claims that 1141 PyPI packages depend on aiohttp: https://libraries.io/pypi/aiohttp/dependents

Adding a trove classifier would benefit the project as it will make related projects more discoverable.
aiohttp already has a big and stable ecosystem, adding a dedicated classifier simplifies the searching.

@webknjaz
Copy link
Member

Hey @di, is there a formal procedure to get a blessing for the new classifier or should someone just go ahead and make a PR? I don't seem to find any instructions on this...

@di
Copy link
Sponsor Member

di commented Nov 14, 2020

Nope, just make a PR here.

@asvetlov
Copy link
Contributor Author

Done

@pradyunsg
Copy link
Member

FWIW, there are two requirements we've been using:

  • New Framework 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)

aiohttp satisfies both of them, as far as I'm concerned. :)

@Maillol
Copy link

Maillol commented Jul 8, 2021

Hello

I would add the tag to the packages: https://pypi.org/project/aiohttp-pydantic/

@ri-gilfanov
Copy link

Yes, that's a good idea.

I would add the tag to the package: https://pypi.org/project/aiohttp-sqlalchemy/

@michael-sulyak
Copy link

I would add the tag to the package: https://pypi.org/project/aiohttp-rpc/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
7 participants