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 pje
Recipients hdima, pitrou, pje
Date 2008-12-22.15:23:48
SpamBayes Score 8.681269e-07
Marked as misclassified No
Message-id <1229959430.03.0.614310706267.issue4718@psf.upfronthosting.co.za>
In-reply-to
Content
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.

This has nothing to do with the desirability of bytes vs. strings; I am
sure that if Python had bytes from day 1, bytes would've been the way to
go with it.  But simply changing the reference library is not the way to
change the spec.

In the meantime, as far as I'm aware, there are two other patches
pending to address these issues, but I'm not in a position to assess
their readiness/correctness since I have yet to even download Py3K.  In
principle, I approve their approaches, so if someone else can handle the
code review, those fixes could in principle be put in without changing
the PEP.  But to put *this* patch in, the PEP would have to be changed.
History
Date User Action Args
2008-12-22 15:23:50pjesetrecipients: + pje, hdima, pitrou
2008-12-22 15:23:50pjesetmessageid: <1229959430.03.0.614310706267.issue4718@psf.upfronthosting.co.za>
2008-12-22 15:23:49pjelinkissue4718 messages
2008-12-22 15:23:48pjecreate