Message201078
| Author | haakon |
|---|---|
| Recipients | Arfrever, asvetlov, bjornedstrom, christian.heimes, dstufft, englabenny, ezio.melotti, gregory.p.smith, haakon, habnabit, jcea, maker, markk, pitrou, python-dev, sbt |
| Date | 2013-10-23.22:48:50 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1382568530.35.0.0141933638662.issue16113@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Please make sure that the currently committed code is not released as part of Python 3.4. SHA-3 is not standardised yet, and NIST has said that they intend to make some changes to the Keccak SHA-3 submission before standardisation as a FIPS. The links englabenny posted have a good overview of the SHA-3 timeline and the proposed changes. It would be very confusing if hashlib in Python 3.4 came with a "sha3" that was incompatible with the final standard. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-10-23 22:48:50 | haakon | set | recipients: + haakon, gregory.p.smith, jcea, pitrou, christian.heimes, habnabit, ezio.melotti, Arfrever, asvetlov, englabenny, maker, python-dev, sbt, bjornedstrom, dstufft, markk |
| 2013-10-23 22:48:50 | haakon | set | messageid: <1382568530.35.0.0141933638662.issue16113@psf.upfronthosting.co.za> |
| 2013-10-23 22:48:50 | haakon | link | issue16113 messages |
| 2013-10-23 22:48:50 | haakon | create | |