Ability to mark a version of a package as deprecated or unsupported

Then warehouse can serve that info back when pip looks up a package, and pip can display a warning.

This allows maintainers to inform users that theyr’e using an out of date version, without needing them to modify the source of the old package.

[pradyunsg]

NPM allows the package owners/authors to declare the package as deprecated, adding a very visible message on the package’s page about it.

See https://www.npmjs.com/package/iltorb for example.

---

Here’s a proposal: Add a “deprecate package and yank all releases” button in the Manage Project page.

It’ll let the owner provide a message that’s presented prominently on the package page and would, as the name suggests, also yank all the existing releases. New releases cannot be made for a deprecated package. It’ll be possible for an owner to un-deprecate a package, but this operation would not un-yank the past releases.

[warsaw]

This came up during a Pycon dinner conversation. IWBNI the admins could similarly mark a package. We were discussion the still active use of oauth despite the fact that it’s been unmaintained (with no new uploads) upstream since 2009, isn’t py3 compatible, there are better replacements (albeit with different APIs) on PyPI, and yet oauth still comes up as the top search hit. We don’t want people using the package any more, but we also don’t want to break existing usages. I’d like to see the package deprecated with a pip warning on install, and also down-rank the package in PyPI searches.