On Sat, Oct 12, 2013 at 11:06 AM, Georg Brandl <g.bra...@gmx.net> wrote:
> Am 12.10.2013 19:37, schrieb Antoine Pitrou: > > On Sat, 12 Oct 2013 19:19:44 +0200 > > Christian Heimes <christ...@python.org> wrote: > ... > >> * add PBKDF2 to ``hashlib`` > >> * make ``hashlib`` a package and add PBKDF2 to a new ``hashlib.kdf`` > module > >> * make ``hashlib`` a package and add PBKDF2 to a new ``hashlib.pbkdf2`` > >> module > agreed with any of these three. > > Putting it in "hashlib" sounds fine. There's no reason to create a > > myriad of small separate modules. > > Maybe it's a good idea to expose HMAC through hashlib as well, and > deprecate > the standalone module at some point? > that also makes sense... I'd leave hmac.py around through at least 3.6 but going ahead and moving the implementation into hashlib in 3.4 makes sense. -gps
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
