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 orsenthil
Recipients BreamoreBoy, adamnelson, ajaksu2, collinwinter, eric.araujo, ezio.melotti, mastrodomenico, mgiuca, nagle, orsenthil, pitrou, vak, varmaa, vstinner
Date 2010-07-19.12:13:25
SpamBayes Score 0.00180144
Marked as misclassified No
Message-id <20100719121317.GA12695@remy>
In-reply-to <1279538730.58.0.545269064043.issue1712522@psf.upfronthosting.co.za>
Content
On Mon, Jul 19, 2010 at 11:25:30AM +0000, Antoine Pitrou wrote:
> If we were following you, we would add "encoding" and "errors"
> arguments to any str-accepting 2.x function, so that it can also
> accept unicode strings. That's certainly not a reasonable solution.

I don't think Matt is indicating that. Just the quote function can be
used with unicode string as perfectly valid string input.
In the original py3k bug too, there was a big discussion on this very
same topic.
History
Date User Action Args
2010-07-19 12:13:27orsenthilsetrecipients: + orsenthil, collinwinter, varmaa, nagle, pitrou, vstinner, ajaksu2, ezio.melotti, eric.araujo, mgiuca, mastrodomenico, vak, adamnelson, BreamoreBoy
2010-07-19 12:13:25orsenthillinkissue1712522 messages
2010-07-19 12:13:25orsenthilcreate