bcrypt: New release results in bcrypt break
Hello,
Our system sadly relies on tip of bcrypt and in this case the new release breaks when you do
import bcrypt
Can anyone fix this? I don’t know what this package does except that it is used in some dependable packages.
About this issue
- Original URL
- State: open
- Created 7 months ago
- Comments: 22 (5 by maintainers)
I use
bcryptwithpasslibI updatedbcryptto4.1.0today and it has broken my serviceI run my service in a docker container from docker image
python:3.11-slimWith these dependencies:The following code works:
but with such dependencies
it crashes and traceback is:
Same error using the test script below.
passlib’s self-test logic appears to choke on thesaltparameter having changed expected types inbetween 4.0.1 and 4.1.0.Resulting stack trace:
Thanks for scrubbing this release from PyPI.
We have yanked the 4.1.0 release so people experiencing issues should
pip install -U bcryptand it will re-install 4.0.1. If you have a local wheel cache and just typepip install bcryptit may still install 4.1.0, so make sure you use-Uto have it hit PyPI.We’re looking at the Windows bug, but the passlib issue is actually an issue with passlib’s heuristic detection failing because we added
__version__to the shared object. We’ll work around this in 4.1.1 since while it isn’t our bug it certainly is our problem 😄I’ve gone ahead and done so.
(It was a bit fraught, because the only way to do so was to un-yank for a second. Hopefully this didn’t disturb anyone!)