[Python-Dev] Proposed schedule for Python 3.4

[Christian Heimes]

Am 03.10.2012 13:54, schrieb Larry Hastings:
> As for the rest of it, my understanding was that there is no longer any
> great plan written in the stars for Python releases.  Python releases
> are comprised of whatever features people propose, implement, and are
> willing to support, that they can get done in time for the beta cutoff. 
> From that perspective, the schedule drives the features more than the
> other-way around.

I have some crypto and security related features planed for Python 3.4.
I'm planing a PEP on password hashing algorithms (password based key
derivation functions) like pbkdf2, bcrypt and scrypt. The topic was
discussed on python-ideas about half a year ago. We agree that it's
worth to have accelerated C implementations in the core.

Two days ago NIST announced the SHA-3 contest winner. My wrapper of
keccak https://bitbucket.org/tiran/pykeccak/ is almost ready and just
needs some cleanup and more tests. Once it's done I'll remove the Python
3.2 and 2.x compatibility code and integrate it into 3.4.

Christian