Will a proposed change to PyPI's JSON API break poetry?

[warsaw]

This long standing PyPI issue describes a problem where a project on PyPI with no packages uploads, returns a 404 on the JSON API. Now that PyPI supports organizations, this is problematic because neither roles nor org ownership can be determined for these "empty reserved" projects.

In discussions with some PyPI developers and maintainers, we think it would both be correct and doable to instead, return a truncated JSON body for these types of reserved-but-empty projects.

One question is whether this would break Poetry or not. If I'm reading the code correctly, I think it will not. Instead of getting a PackageNotFoundError in this case, you'll get a 200 response, a JSON body, and an empty list of releases.

Could you please confirm whether nor not this is a breaking change from Poetry's point of view? If it would break Poetry, can you give me some estimate of what kind of lead time you'd need to adjust to this change?

TIA!

[radoering]

Does this only influence the version-less endpoint of the API (/pypi/<project>/json)? Then, it should not influence Poetry because since #6081 Poetry only uses the version-specific endpoint /pypi/<project>/<version>/json (and the Index API).

[sbrunner]

Then the version of Poetry < 1.3 (4 years old) will break?

[warsaw]

Thanks @radoering. Confirmed, it would only influence the versionless endpoint. The versioned endpoint would not change, nor would the Index API.