You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added support for the per-release JSON API (e.g. /pypi/requests/1.0.0/json) in the hopes that tools like Poetry could use it to quickly fetch dependencies during dependency resolution without needing to download the entire wheel, but they never supported this for internal registries anyway (python-poetry/poetry#5337).
I later added the --no-per-release-json argument to allow disabling this since it introduces a huge number of new files per release which slows down registry generation a lot.
I think we should probably just remove that feature entirely (or at the very least disable it by default), especially with PEP658 now adopted which I'm going to add support for soon. It's a better way to achieve the same goal and will actually be supported by tools going forward.
The text was updated successfully, but these errors were encountered:
I added support for the per-release JSON API (e.g.
/pypi/requests/1.0.0/json
) in the hopes that tools like Poetry could use it to quickly fetch dependencies during dependency resolution without needing to download the entire wheel, but they never supported this for internal registries anyway (python-poetry/poetry#5337).I later added the
--no-per-release-json
argument to allow disabling this since it introduces a huge number of new files per release which slows down registry generation a lot.I think we should probably just remove that feature entirely (or at the very least disable it by default), especially with PEP658 now adopted which I'm going to add support for soon. It's a better way to achieve the same goal and will actually be supported by tools going forward.
The text was updated successfully, but these errors were encountered: