Message 97203 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	lemburg
Recipients	ebfe, gregory.p.smith, hagen, kmtracey, lemburg, pitrou, rpetrov, vstinner
Date	2010-01-04.11:49:27
SpamBayes Score	5.072953e-05
Marked as misclassified	No
Message-id	<4B41D5C5.2060206@egenix.com>
In-reply-to	<1262471934.81.0.102422134164.issue3745@psf.upfronthosting.co.za>

Content
Gregory P. Smith wrote: > > Gregory P. Smith <greg@krypto.org> added the comment: > > In order to get a -3 PyErr_WarnPy3k warning for unicode being passed to hashlib objects (a nice idea) I suggest creating an additonal 's' like thing ('s3' perhaps?) in Python/getargs.c for that purpose rather than modifying all of the hashlib modules to accept an O, type check it and warn, and then re-parse it as a s (that'd be a lot of tedious code duplication). Good idea. We're likely going to need this in more places, so I'm +1 on adding an "s3" parser marker.

Gregory P. Smith wrote:
> 
> Gregory P. Smith <greg@krypto.org> added the comment:
> 
> In order to get a -3 PyErr_WarnPy3k warning for unicode being passed to hashlib objects (a nice idea) I suggest creating an additonal 's*' like thing ('s3' perhaps?) in Python/getargs.c for that purpose rather than modifying all of the hashlib modules to accept an O, type check it and warn, and then re-parse it as a s* (that'd be a lot of tedious code duplication).

Good idea. We're likely going to need this in more places, so I'm +1 on
adding an "s3" parser marker.

History
Date	User	Action	Args
2010-01-04 11:49:28	lemburg	set	recipients: + lemburg, gregory.p.smith, pitrou, vstinner, kmtracey, hagen, rpetrov, ebfe
2010-01-04 11:49:27	lemburg	link	issue3745 messages
2010-01-04 11:49:27	lemburg	create