You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This new classifier will be useful for users of https://github.com/PyCQA/pylint to discover plugins published by the community. Pylint has support for custom plugins and there are quite a few already created by the community such as pylint-django or pytest-pylint. Also doing a basic naive search in PyPi yield quite a few results of packages that might be good candidates of this new trove classifier: https://pypi.org/search/?q=pylint&o=
Flake8 also has its own classifier which is another popular tool for static analysis.
Hi! Thanks for the well written 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 may 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 next guideline help. (I'm already convinced pylint is notable.)
As to the other guideline ('immediate use to existing projects'), the best way to demonstrate it is to have 10 (or more) other project maintainers submit comments on the requesting issue about their desire to use the classifier on their published project.
We appreciate any help gathering this information.
Activity
jamadden commentedon Apr 24, 2020
Hi! Thanks for the well written 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:
We understand that "notability" is subjective and we'd appreciate help judging that; responses to the next guideline help. (I'm already convinced pylint is notable.)
As to the other guideline ('immediate use to existing projects'), the best way to demonstrate it is to have 10 (or more) other project maintainers submit comments on the requesting issue about their desire to use the classifier on their published project.
We appreciate any help gathering this information.
xavfernandez commentedon Apr 24, 2020
👋 As I was the one suggesting to add this classifier I would have used it in my (modest) pylint plugin https://pypi.org/project/pylint-strict-informational/ (and will use it).
Shizoqua commentedon Aug 5, 2026
Hi, working on this — will open a PR adding the Pylint framework classifier.
merwok commentedon Aug 5, 2026
Please don’t just run a bot on open requests while ignoring the previous discussion.
This needs an assessment of need and support from project maintainers.