-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Currently, the legacy API provided by Warehouse does not include the ability provided by pypi-legacy to register a package name, giving a "410 Client Error: This API is no longer supported" message.
Instead, it prefers to register the package the first time a release is uploaded. Thus, it's not actually necessary to register a package name at all before attempting to make an initial release.
There are a few open issues elsewhere as a result of this:
- "410 Client Error: This API is no longer supported" during
twine register
pypa/twine#200 - Documentation contains an obsolete link pypa/twine#214
- Register using twine fails if following the guide pypa/packaging.python.org#263
- Remove "twine register" reference in distributing.rst pypa/packaging.python.org#271
- http://stackoverflow.com/questions/40022710/how-am-i-supposed-to-register-a-package-to-pypi
We currently have a stale PR which was attempting to add back the legacy register API: #1418
However, I see some advantages to continuing to not support this aspect of the API, namely because it's continued existence:
- Enables name squatting;
- Creates the edge case of how to display a registered package with no release (404 for registered package with no release #1388);
- Causes the occasional support request to release an unmaintained package with no releases.
And in addition, as the current Warehouse API shows, it's seemingly unnecessary.
Should we add support for legacy-style registration?
- If so, we should get WIP: Add support for legacy Register API #1418 fixed and merged;
- If not, we should update the user guide and/or twine, because it's causing confusion.