Skip to content

Support for legacy register API #1627

@di

Description

@di

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:

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions