Yes, Python 3.0 still has MD5, but it's now all tied up with the bytes type and encodings. I think I might investigate some kind of alternative scheme for doing this.
Cheers, Dave On Fri 26/09/08 9:28 AM , "Simon Cross" [EMAIL PROTECTED] sent: > > > On Fri, Sep 26, 2008 at 3:16 PM, David Beazley [EMAIL PROTECTED] > om> wrote: > > Yes, this would be a good feature to add to PLY-2.6. > I'll have to think of some new scheme for knowing > > when to run the update. Right now PLY relies on MD5 > signatures, but this > > being deprecated in Python 3.0 so I'll have to come up > with an alternative (maybe I'll do some kind of > > thing with hash keys). > > > > md5 signatures aren't being deprecated -- just the md5 module. It is > > being replaced by hashlib.md5. In current Python 2.6 importing the md5 > > module prints a deprecation warning. In current 3.0, the md5 module is > > gone. > > > > >>> import hashlib > > >>> hashlib.md5(b"foo").digest() > > '\xac\xbd\x18\xdbL\xc2\xf8\\\xed\xefeO\xcc\xc4\xa4\xd8' > > > > works without warnings in both current 2.6 and 3.0. > > > > Schiavo > > Simon > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ply-hack" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ply-hack?hl=en -~----------~----~----~----~------~----~------~--~---
