➜

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 pitrou
Recipients eric.araujo, eric.smith, ncoghlan, pitrou, r.david.murray
Date 2010-09-29.22:09:30
SpamBayes Score 0.00035988304
Marked as misclassified No
Message-id <1285798167.3194.56.camel@localhost.localdomain>
In-reply-to <1285797358.89.0.615919758335.issue9873@psf.upfronthosting.co.za>
Content 
> The primary reason for supporting ASCII compatible bytes directly is
> specifically to avoid the encoding and decoding overhead associated
> with the translation to unicode text.

I think it's quite misguided. latin1 encoding and decoding is blindingly
fast (on the order of 1GB/s. here). Unless you have multi-megabyte URLs,
you won't notice any overhead.
History
Date User Action Args
2010-09-29 22:09:31pitrousetrecipients: + pitrou, ncoghlan, eric.smith, eric.araujo, r.david.murray
2010-09-29 22:09:30pitroulinkissue9873 messages
2010-09-29 22:09:30pitroucreate