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 to add Framework :: Inkscape #20

Open
doctormo opened this issue Mar 18, 2020 · 4 comments
Open

Request to add Framework :: Inkscape #20

doctormo opened this issue Mar 18, 2020 · 4 comments
Labels
new classifier request Request for a new classifier

Comments

@doctormo
Copy link

Request to add a new Trove classifier.

The name of the classifier you would like to add

  • Framework :: Inkscape
  • Framework :: Inkscape :: Extensions

Why do you want to add this classifier?

The Inkscape project would like to install it's python based extensions using pip/pypi and having a specific classifier would allow our inkscape extension manager graphical user interface to search for and show only Inkscape specific extensions in the results.

Background issue: pypa/packaging-problems#335

The Inkscape project uses the word "extensions", but I see plugins is the typical word used in python land. Either would be fine, extensions for preference.

@di di transferred this issue from pypi/support Apr 4, 2020
@pradyunsg pradyunsg changed the title Trove Classifier Request Request to add Framework :: Inkscape Apr 5, 2020
@pradyunsg
Copy link
Member

Hi! Thanks for the request. The PyPI moderators have 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, the bar to add new ones is relatively high. Currently, we have 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; responses to the second guideline help.

As to the second guideline ('immediate use to existing projects'), the best way to demonstrate notability is to have 10 or more other project maintainers submit comments on the requesting issue (i.e. here!) about their desire to use the classifier on their published project.

We appreciate any help gathering those responses.

@pradyunsg pradyunsg added the new classifier request Request for a new classifier label Apr 5, 2020
@doctormo
Copy link
Author

doctormo commented Apr 5, 2020

Thanks pradyunsg for the clear requirements. This helps me build a sense of what we need to do in Inkscape to get the classifier recognised. For now we will stick to using the generic ones until we have a notable number of classifierees.

It would be helpful if pypi allowed future classifiers so we could guide creators to use something which would then work right away if this came to pass. But I believe at the moment packages are rejected if they have classifiers that aren't in the single list right?

@pradyunsg
Copy link
Member

Yes, PyPI rejects uploads that use an invalid / non-existent classifier. You can find the current list of classifiers for PyPI on https://pypi.org/classifiers.

@doctormo
Copy link
Author

doctormo commented Apr 6, 2020

Sorry I mean to say: That behaviour is unhelpful for prospective classifiers, it's rather stringent as it could just ignore them.

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

2 participants