➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ebfe
Recipients ebfe
Date 2009-01-03.17:08:22
SpamBayes Score 0.00025567753
Marked as misclassified No
Message-id <1231002504.32.0.171592356443.issue4821@psf.upfronthosting.co.za>
In-reply-to
Content 
Here is the follow-up to issue #4818. The patches attached allow the
built-in SHA modules to release the GIL.

Also the build-in SHA modules will now no longer accept "s#" as input.
Input is parsed just as in the openssl-driven classes where
unicode-objects are explicitly rejected.


The built-in hash modules have been not quite beautiful before even more
code is now copy & pasted between them. Is there any interest in
refactoring all those modules? AFAIK _sha1 and such are only used by
hashlib.py ...
History
Date User Action Args
2009-01-03 17:08:24ebfesetrecipients: + ebfe
2009-01-03 17:08:24ebfesetmessageid: <1231002504.32.0.171592356443.issue4821@psf.upfronthosting.co.za>
2009-01-03 17:08:23ebfelinkissue4821 messages
2009-01-03 17:08:22ebfecreate