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 hdima
Recipients hdima, pitrou, pje
Date 2008-12-22.16:36:13
SpamBayes Score 3.3532834e-09
Marked as misclassified No
Message-id <494FC1FA.6020200@hlabs.spb.ru>
In-reply-to <1229960264.6263.47.camel@localhost>
Content
Antoine Pitrou wrote:
>> If you want to change to using bytes, you're going to have to take it
>> to the Web-SIG and hash out a revision to PEP 333, which at the moment
>> requires the use of strings, period.
> 
> What was called str in 2.x has become the bytes object in py3k.
> What was called unicode in 2.x has become str in py3k.
> (roughly)

Agreed, moreover it's time for Python 3.0.1 and we need to decide -
apply a patch or just remove wsgiref completely for now. Keep wsgiref
just as nonworking piece of code is the worse solution which can made
questionable all WSGI effort.

Given that old str has been replaced by bytes in Python 3 I think the
patch is a correct implementation of the PEP from the Python 3's point
of view. To avoid confusion note about the meaning of the term *string*
can be added to the PEP later.
History
Date User Action Args
2008-12-22 16:36:14hdimasetrecipients: + hdima, pje, pitrou
2008-12-22 16:36:13hdimalinkissue4718 messages
2008-12-22 16:36:13hdimacreate