Re: Bug#1115706: Not installable with python3-cryptography >= 44
Hi Simon (2025.09.19_13:10:16_+0000)
Does anyone have thoughts on why some python packages use << versioning
on build dependencies even when there are no such versions released?
You sometimes see this. It's over-protective IMHO.
We don't always do this. Packages need to declare PEP386 (in practice
PEP440) compliance for dh_python3 to do this. Or you have to pass
--accept-upstream-versions.
That's probably worth re-visiting, because everything is PEP440
compliant, these days.
If this a python cultural upstream thing, is this something that should
be mirrored in Debian's Depends: versioning?
It's problematic for us to not mirror it, because then you can have
packages installed that don't have their dependencies met. pip doesn't
like that. pkg_resources (IIRC) used to also get quite up set about it.
So, typically patching the upstream dependencies is appropriate in these
situations.
Stefano
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
Reply to: