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

feat: add litestar classifier #148

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

JacobCoffee
Copy link

@JacobCoffee JacobCoffee commented Jun 25, 2023

Adds classifiers for the https://github.com/litestar-org/litestar project

Request to add a new Trove classifier.

The name of the classifier(s) you would like to add:

  • Framework :: Litestar
  • Framework :: Litestar :: 2
  • Framework :: Litestar :: 3

Why do you want to add this classifier?

Brief:

  • This is an ASGI framework and we would like to classify it as such.

Why not use current ones?

  • There are no proper Framework classifiers as they do not exist (yet).

How much usage?

  • The core project along with other published organization repos, and whichever the community build with and publish.

Why multiple?

  • Major Versioning.

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.
@di
Copy link
Member

di commented Aug 30, 2023

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:

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

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

  • Requestors can demonstrate this by providing links to 10 or more existing PyPI projects that have expressed a desire to use the classifier; or
  • Another way to demonstrate this would be to have 10 or more other project maintainers submit comments on the requesting issue about their desire to use the classifier.

Thanks!

@JacobCoffee JacobCoffee closed this Sep 8, 2023
@JacobCoffee JacobCoffee changed the title feat: add litestar and starlite classifiers feat: add litestar classifier Sep 27, 2024
@JacobCoffee JacobCoffee reopened this Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants