
<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><br class="">On Sep 19, 2014, at 8:02 PM, Greg Ewing <<a href="mailto:greg.ewing@canterbury.ac.nz" class="">greg.ewing@canterbury.ac.nz</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Donald Stufft wrote:<br class=""><br class=""><blockquote type="cite" class="">My biggest problem with ``python3``, is what happens after 3.9.<br class=""></blockquote><br class="">Python2 technically includes 1.x versions as well, so it<br class="">wouldn't be unprecedented for python3 to imply versions<br class="">beyond 3.x. It would be a bit confusing, though.<br class=""></div></blockquote><br class=""></div><div>My problem isn’t that it *includes* it, it’s that either people have to go</div><div>through the mess to update all of their things to ``python4`` at some point</div><div>in the future, or Python 3.x will need to eventually mean ``python``.</div><div><br class=""></div><div>Well that or Python 4.x has a ``python3`` binary.</div><br class=""><div class="">

<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">---</div><div class="">Donald Stufft</div><div class="">PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA</div></div></div>

</div>

<br class=""></body></html>