New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patches for thread-support in built-in SHA modules #49071
Comments
Here is the follow-up to issue bpo-4818. The patches attached allow the Also the build-in SHA modules will now no longer accept "s#" as input. The built-in hash modules have been not quite beautiful before even more |
This patch is a duplicate of bpo-3745. |
Oops, it's not a duplicate /o\ But it may solves bpo-3745 (reject unicode |
sha1module_small_locks.diff patch is very similar to the changes made
Instead of copy/paste code in hashlib, sha1, sha256 and sha512 (4
And about sha, why using 3 files for sha? Are the source code so #define FLOAT float
#define FLT FLT
#ifdef USE_WIDE_CHAR
#define STRTOF wcstof
#define STRTOF_L __wcstof_l
#else
# define STRTOF strtof
# define STRTOF_L __strtof_l
#endif
#include "strtod.c" Refactoring to share code between hash modules will ease the changes, |
fyi - I took care of the unicode data acceptance issue for all hashlib Yes, the hashlib modules have a -lot- of code in common. Refactoring |
I'll integrate your patch once I'm done with my SHA-3 patch bpo-16113. I'm using parts of your patch in my new sha3 code to release the GIL. I'll also check if I can share more code between the SHA family modules. |
@tiran this issue has been idle for a decade. Is it still useful? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: