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
For Python 3.12, the numpy>=1.26.0b1 means that using pip's default upgrade strategy, this will also pick up release candidates, which might not be desirable (c.f. scikit-hep/cabinetry#477)
but there hasn't been a release since then. A new release would resolve this issue, without users needing to explicitly guard against release candidates.
matthewfeickert
changed the title
[BUG] forcing use of release candidate numpy on Python 3.12
[BUG] defaulting to use of release candidate numpy on Python 3.12
May 29, 2024
Describe the bug
This might not really be a "bug", but it is different from the expected user experience.
hist
v2.7.2
has different NumPy requirements between Python 3.12 and older Pythonshist/pyproject.toml
Lines 41 to 42 in 8ab9594
For Python 3.12, the
numpy>=1.26.0b1
means that usingpip
's default upgrade strategy, this will also pick up release candidates, which might not be desirable (c.f. scikit-hep/cabinetry#477)This was fixed in #543 with the move to
hist/pyproject.toml
Line 41 in 9c3a275
but there hasn't been a release since then. A new release would resolve this issue, without users needing to explicitly guard against release candidates.
Steps to reproduce
The text was updated successfully, but these errors were encountered: