Why Poetry uses JSON API for PyPI but HTML Index API for other sources?

[mfridman]

According to the documentation (https://python-poetry.org/docs/repositories#python-package-index-pypi):

Poetry interacts with PyPI via its JSON API. This is used to retrieve a requested package's versions, metadata, files, etc.

I've observed that when connecting to private repositories that also implement this JSON API, Poetry doesn't use it and defaults to the HTML index API instead.

Could someone explain why Poetry specifically uses the JSON API for PyPI but favors the HTML index API for other repositories, even when they implement the same JSON API?

[dimbleby]

other sources don't implement the same JSON API

[mfridman]

But suppose other sources do support it - is there a way to make Poetry prefer the JSON API instead?

From what I understand, both PEP 691 and PEP 658 have gained acceptance as the standard ecosystem-wide ways to serve metadata in a PEP 503 repository. So I'm curious how to get Poetry to play nice with non-PyPI sources that offer these newer APIs?

[mfridman]

For context, I believe one of the maintainers (@neersighted, sorry for the @ 😅 ) mentioned #4113 (comment) that Poetry will one day move towards this:

Once PyPI gains support, we will likely implement this in Poetry and unify all of our source handling code to no longer special-case PyPI.

Hence the discussion as I couldn't find anything specific around this (if this is being tracked in another issue, apologies and we can continue the discussion there).

[dimbleby]

#9170

[mfridman]

Thanks for the link, I'll close this discussion. Apologies as I missed that issue.