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
Linux x86_64: 4 wheels (Python 3.8 - Python 3.11) at ~81 MiB each
Linux aarch64: 4 wheels (Python 3.8 - Python 3.11) at ~81 MiB each
macOS x86_64: 4 wheels (Python 3.8 - Python 3.11) at ~19 MiB each
sdist: ~4 MiB
We have deleted all release candidates from PyPI to make additional space. We plan to get conda distributions of all existing wheels onto conda-forge (c.f. conda-forge/fastjet-feedstock#9) to ensure that any old releases that need to be deleted for space have a public built version available somewhere.
How frequently do you make a release?
Roughly once every 2-3 months, but there are some bursts in the schedule given conference driven development.
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
Project URL
https://pypi.org/project/fastjet/
Does this project already exist?
New limit
30 GB
Update issue title
Which indexes
PyPI
About the project
Pybind11 bindings for the FastJet clustering algorithms used in high energy particle physics (https://github.com/scikit-hep/fastjet).
The first release of the project to PyPI was in 2021.
The project currently supports Python 3.8 - 3.11 but would like to start supporting Python 3.12 wheels as well.
How large is each release?
Using the v3.4.1.3 release as a reference example (https://pypi.org/project/fastjet/3.4.1.3/#files)
Project total per release: ~730 MiB
We have deleted all release candidates from PyPI to make additional space. We plan to get conda distributions of all existing wheels onto conda-forge (c.f. conda-forge/fastjet-feedstock#9) to ensure that any old releases that need to be deleted for space have a public built version available somewhere.
How frequently do you make a release?
Roughly once every 2-3 months, but there are some bursts in the schedule given conference driven development.
Code of Conduct
The text was updated successfully, but these errors were encountered: