Conversation
Adds classifiers for the https://github.com/litestar-org/litestar project, which was rebranded to `Litestar` in version 2.0 onward, and previously was known as `Starlite`. This is an ASGI framework and we would like to classify it as such.
|
Hi! Thanks for the request. The PyPI moderators are in the process of developing a few guidelines for the creation of new Framework classifiers. Because removing classifiers is very difficult, and the longer the classifier list gets the harder it is to browse, I think we're expecting the bar to add new ones to be relatively high. Currently, we're looking at these guidelines:
We understand that "notability" is subjective and we'd appreciate help judging that. As to the other guideline ('immediate use to existing projects'), it's been suggested that
Thanks! |
litestar and starlite classifierslitestar classifier
|
Friendly ping :) I hope that this will be merged 🙏 |
Adds classifiers for the https://github.com/litestar-org/litestar project that has ~6,000 stars on GitHub and has projects used by companies like @scalar, @mozilla, @GoogleCloudPlatform, the EU's @eea to name a few.
Request to add a new Trove classifier.
The name of the classifier(s) you would like to add:
Framework :: LitestarFramework :: Litestar :: 2Framework :: Litestar :: 3Why do you want to add this classifier?
Brief:
Why not use current ones?
Frameworkclassifiers as they do not exist (yet).How much usage?
Some, not all, existing PyPI packages that would benefit from discoverability by filtering by framework: