Skip to content
This repository has been archived by the owner on May 30, 2020. It is now read-only.

Ordering of releases in json #171

Closed
ewdurbin opened this issue Jul 29, 2014 · 1 comment
Closed

Ordering of releases in json #171

ewdurbin opened this issue Jul 29, 2014 · 1 comment

Comments

@ewdurbin
Copy link
Member

Originally reported by: Aaron Meurer (Bitbucket: asmeurer, GitHub: asmeurer)


One thing that the json API lacks compared to the xmlrpc API is the ordering of releases. In the json API, the releases are keys in a dictionary, and hence unordered.

The tarballs have upload times, but a release can have multiple tarballs, and also if I'm not mistaken you can upload a tarball to an old release.

The xmlrpc API has package_releases(package_name, show_hidden=False). The json API could have a package_releases key with a list of releases. I don't know how to handle hidden releases.


@di
Copy link
Member

di commented Apr 12, 2018

Moved to pypi/warehouse#3650.

@di di closed this as completed Apr 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants