Isn't this recent bit of discussion an argument in favor of a new stdlib module `version`? That would contain things like resolving a version tuple to an executable name (or a cross-platform piece of an executable name)? Obviously this doesn't actually answer the question of how naming should be done in the future, but it does mean that (new) code will have the actual choice abstracted away.
--Josh On Mon, Nov 6, 2017 at 4:20 AM Stephan Houben <stephan...@gmail.com> wrote: > 2017-11-06 12:53 GMT+01:00 Brice Parent <cont...@brice.xyz>: > >> >> I think the only problem we can reach here, not only in our lifetimes, >> but in the next years, is not Python3.10 vs Python31.0 (Python3.x will be >> long dead when we reach this point!), but the ordering of versions, like >> (python310 < python40). But it probably is a false problem, as after a >> two-digit minor version, we can fix the length of minor versions to two >> digits when needed (python310 < python400). >> > > No probs with either of my proposals: > > >>> "python39.dll" < "python3A.dll" < "python40.dll" > True > >>> "python39.dll" < "python3⑽.dll" < "python40.dll" > True > > Stephan > > >> >> _______________________________________________ >> Python-ideas mailing list >> Python-ideas@python.org >> https://mail.python.org/mailman/listinfo/python-ideas >> Code of Conduct: http://python.org/psf/codeofconduct/ >> >> _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > https://mail.python.org/mailman/listinfo/python-ideas > Code of Conduct: http://python.org/psf/codeofconduct/ >
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
