<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><a href="http://pyvideo.org/pycascades-2018/bdfl-python-3-retrospective.html">http://pyvideo.org/pycascades-2018/bdfl-python-3-retrospective.html</a> link to Guido’s talk, for your convenience<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> Python-Dev <python-dev-bounces+tritium-list=sdamon.com@python.org> <b>On Behalf Of </b>Guido van Rossum<br><b>Sent:</b> Thursday, April 26, 2018 6:12 PM<br><b>To:</b> Brett Cannon <brett@python.org><br><b>Cc:</b> Barry Warsaw <barry@python.org>; Python-Dev <python-dev@python.org><br><b>Subject:</b> Re: [Python-Dev] (Looking for) A Retrospective on the Move to Python 3<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Also see my talk at PyCascades and Victor's upcoming talk at PyCon.<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, Apr 26, 2018, 12:02 Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, 26 Apr 2018 at 10:19 Barry Warsaw <<a href="mailto:barry@python.org" target="_blank">barry@python.org</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>On Apr 26, 2018, at 09:28, Eric Snow <<a href="mailto:ericsnowcurrently@gmail.com" target="_blank">ericsnowcurrently@gmail.com</a>> wrote:<br>> <br>> On Thu, Apr 26, 2018 at 10:25 AM, Eric Snow <<a href="mailto:ericsnowcurrently@gmail.com" target="_blank">ericsnowcurrently@gmail.com</a>> wrote:<br>>> In pondering our approach to future Python major releases, I found<br>>> myself considering the experience we've had with Python 3. The whole<br>>> Py3k effort predates my involvement in the community so I missed a<br>>> bunch of context about the motivations, decisions, and challenges.<br>>> While I've pieced some of that together over the years now since I've<br>>> been around, I've certainly seen much of the aftermath. For me, at<br>>> least, it would be helpful to have a bit more insight into the<br>>> history. :)<br><br>It would certainly be an interesting document, but I suspect you’ll get a bit of the old “ask 3 lawyers and get 5 opinions” kind of response. ;)<br><br>As I remember it, there was definitely a feeling like, this would be our only chance to clean up some annoying cruft, and rectify some (in hindsight) incorrect design decisions made over the years, couple with a healthy dose of “we have no idea how to do the bytes/str split in a backward compatible way". There was probably a sense that the Python community was just small enough to be able to handle such a disruptive change, but wouldn’t ever be so again. The latter is definitely true today, even if the former was overly optimistic.<o:p></o:p></p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I agree with everything Barry said. There are some lessons in hindsight of how we could have handled bytes/str, but it was more of a decision of "really long transition versus a short one" -- jokes on us for what "short" became ;) -- which we simply won't make ever again.<o:p></o:p></p></div></div></div><p class=MsoNormal>_______________________________________________<br>Python-Dev mailing list<br><a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br><a href="https://mail.python.org/mailman/listinfo/python-dev" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/guido%40python.org" target="_blank">https://mail.python.org/mailman/options/python-dev/guido%40python.org</a><o:p></o:p></p></blockquote></div></div></div></body></html>