Pin bandersnatch to <6.6. #814
Conversation
ggainey
force-pushed
the
pin_bandersnatch
branch
from
6a58e1d to
4df325a
Compare
|
The install-failure here is due to our more-strict upperbounds check requiring bandersnatch 6.5, on an image built with python-3.9 - which is not supported by bandersnatch>=6.4.0. We will need to pin to ~=6.3.0 until we stop supporting py3.9, and/or figure out how to make the UB check take the python-version into account. |
ggainey
force-pushed
the
pin_bandersnatch
branch
from
4df325a to
d32d6da
Compare
pyproject.toml
Outdated
| "pulpcore>=3.49.0,<3.85", | ||
| "pkginfo>=1.10.0,<1.13.0", | ||
| "bandersnatch>=6.3,<7.0", # Anything >6.3 requires Python 3.10+ | ||
| "bandersnatch~=6.3.0", # Anything >6.3 requires Python 3.10+ |
There was a problem hiding this comment.
Should this be
| "bandersnatch~=6.3.0", # Anything >6.3 requires Python 3.10+ | |
| "bandersnatch>=6.3.0,<6.4", # Anything >6.3 requires Python 3.10+ |
then?
There was a problem hiding this comment.
Aren't these identical?
There was a problem hiding this comment.
Yes, and no.
They mean the same to python, but dependabot treats them differently.
See pypa/bandersnatch#1892 for the discussion. In addition, 6.3.0 is the last bandersnatch that supports py3.9. fixes pulp#809.
ggainey
force-pushed
the
pin_bandersnatch
branch
from
d32d6da to
2e064ca
Compare
Backport to 3.13: 💚 backport PR created✅ Backport PR branch: Backported as #831 🤖 @patchback |
Pin bandersnatch to <6.6. (cherry picked from commit 1f44c79)
…0e8b6b8aab3e1a8fedf915f54efd99/pr-814 [PR #814/1f44c79a backport][3.13] Pin bandersnatch to <6.6.
2 participants
See pypa/bandersnatch#1892 for the discussion.