Message72220
| Author | hagen |
|---|---|
| Recipients | hagen |
| Date | 2008-09-01.09:27:03 |
| SpamBayes Score | 8.2017914e-07 |
| Marked as misclassified | No |
| Message-id | <1220261226.32.0.128110321757.issue3745@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Whereas openssl-based _hashlib refuses to accept unencoded strings:
>>> _hashlib.openssl_sha256("\xff")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: object supporting the buffer API required
the _sha256 version encodes to UTF-8 by default:
>>> _sha256.sha256("\xff").digest() ==
_sha256.sha256("\xff".encode("utf-8")).digest()
True
I think refusing is better, but at least the behaviour should be
consistent. Same for the other algorithms in hashlib. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-09-01 09:27:06 | hagen | set | recipients: + hagen |
| 2008-09-01 09:27:06 | hagen | set | messageid: <1220261226.32.0.128110321757.issue3745@psf.upfronthosting.co.za> |
| 2008-09-01 09:27:05 | hagen | link | issue3745 messages |
| 2008-09-01 09:27:03 | hagen | create | |