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
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:
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:The text was updated successfully, but these errors were encountered: