-
Notifications
You must be signed in to change notification settings - Fork 986
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
Add "replaced by" field for deprecated classifiers #4626
Labels
good first issue
This issue is ideal for first-time contributors!
Comments
@di I would like to work on issue. |
@di, I'd like to work on this issue from the Bloomberg London PyPA Sprint |
xni
added a commit
to xni/warehouse
that referenced
this issue
Oct 27, 2018
This is the first part, where I'm adding deprecation alternative to the admin page: #4950 I will try to complete the second part (message for the API) tomorrow. |
xni
added a commit
to xni/warehouse
that referenced
this issue
Oct 27, 2018
xni
added a commit
to xni/warehouse
that referenced
this issue
Oct 27, 2018
xni
added a commit
to xni/warehouse
that referenced
this issue
Oct 28, 2018
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One problem with our current ability to deprecate trove classifiers is that we don't have a great way to indicate to the user which classifier(s) they should be using instead.
For example, when I deprecated the classifier
Natural Language :: Ukranian
due to a typo and addedNatural Language :: Ukrainian
, any user that might have had the old classifier would have received an error like:It would be great if we could optionally identify one or more classifiers which replace a deprecated classifier when deprecating it, so we could make this error message something like:
Good First Issue: This issue is good for first time contributors. If you've already contributed to Warehouse, work on another issue without this label instead. If there is not a corresponding pull request for this issue, it is up for grabs. For directions for getting set up, see our Getting Started Guide. If you are working on this issue and have questions, feel free to ask them here,
#pypa-dev
on Freenode, or the pypa-dev mailing list.The text was updated successfully, but these errors were encountered: