> > On Sep 19, 2014, at 8:02 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote: > > Donald Stufft wrote: > >> My biggest problem with ``python3``, is what happens after 3.9. > > Python2 technically includes 1.x versions as well, so it > wouldn't be unprecedented for python3 to imply versions > beyond 3.x. It would be a bit confusing, though. My problem isn’t that it *includes* it, it’s that either people have to go through the mess to update all of their things to ``python4`` at some point in the future, or Python 3.x will need to eventually mean ``python``. Well that or Python 4.x has a ``python3`` binary. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140919/fe09f2f9/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4