-
Couldn't load subscription status.
- Fork 1.1k
External classifiers #7582
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
External classifiers #7582
Conversation
9370491 to
5f7730d
Compare
|
Need to merge/release pypa/trove-classifiers#6 and update this here first, and waiting on a review from @ewdurbin at least (although we've chatted about it and I don't think there's much else to do here). |
|
Just out of an abundance of caution, I'm gonna snag a backup of the classifiers table before this merges. :-D Otherwise, 💯 |
|
Backup taken! |
This PR moves the canonical source for classifiers out of PyPI's database and into the
trove-classifiersproject.This is a necessary step to resolve pypa/packaging#147 and move PyPI's metadata validation out of PyPI and into
packaging.PyPI's behavior here for the end user remains unchanged. For administrators, new & deprecated classifiers are no longer created through the UI, but as pull requests for
trove-classifiersand dependency upgrades here.PyPI still retains a
Classifiermodel to help with efficiently searching for projects based on classifiers, but it is now essentially just a mapping from the classifier name to id. New rows in the classifiers table are created for new classifiers the first time a project is uploaded using that classifier.Fixes #4626, fixes #3786, closes #4950, closes #1244.