<br><div class="gmail_quote">On Mon, Jun 2, 2008 at 4:09 PM, Guido van Rossum <<a href="mailto:guido@python.org">guido@python.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I will freely admit that I haven't followed this thread in any detail,<br>
but if it were up to me, I'd have the 2.6 internal code use PyString</blockquote><div>...<br></div><div><br>Should we read this as a BDFL pronouncement and make it so?<br><br>All that would mean change wise is that trunk r63675 as well as possibly r63672 and r63677 would need to be rolled back and this whole discussion over if such a big change should have happened would turn into a moot point.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I would also add macros that map the PyBytes_* APIs to PyString_*, but<br>
I would not start using these internally except in code newly written<br>
for 2.6 and intended to be "in the spirit of 3.0". IOW use PyString<br>
for 8-bit strings containing text, and PyBytes for 8-bit strings<br>
containing binary data. For 8-bit strings that could contain either<br>
text or data, I'd use PyString, in the spirit of 2.x.<br>
<br>
--Guido<br>
<div><div></div><br></div></blockquote></div>