Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warehouse API to delete old .dev wheels (nightly builds) #12810

Open
ogrisel opened this issue Jan 11, 2023 · 2 comments
Open

Warehouse API to delete old .dev wheels (nightly builds) #12810

ogrisel opened this issue Jan 11, 2023 · 2 comments
Labels
APIs/feeds blocked Issues we can't or shouldn't get to yet feature request

Comments

@ogrisel
Copy link

ogrisel commented Jan 11, 2023

Since wharehouse does not provide a way to specify a retention policy for nightly builds (see #8792), publishing nightly builds on pypi.org could cause a waste of resources, especially for packages that generates many binary wheels for numerous platforms.

Making it possible to programmatically delete old .dev wheel files (or even full .dev releases and their files) could be a possible solution alternative to a server-side retention policy: schedule job on the project CI could handle the deletion of old nightly builds and therefore implement some kind of retention policy on the client side. This solution was discussed in:

@ogrisel ogrisel added feature request requires triaging maintainers need to do initial inspection of issue labels Jan 11, 2023
@dolfinus
Copy link

Why not use https://test.pypi.org for nightly builds?

@di
Copy link
Member

di commented Apr 11, 2023

Blocked on #13409.

@di di added the blocked Issues we can't or shouldn't get to yet label Apr 11, 2023
@di di removed the requires triaging maintainers need to do initial inspection of issue label Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APIs/feeds blocked Issues we can't or shouldn't get to yet feature request
Projects
None yet
Development

No branches or pull requests

4 participants