[Python-Dev] Remove typing from the stdlib (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Tue Nov 7 17:33:09 EST 2017

On 8 November 2017 at 04:41, Lukasz Langa <lukasz at langa.pl> wrote:

4. How do we even version this library then? Probably like this: 3.7.0.0, 3.7.0.1, 3.7.1.0, and so on. But that depends on answers to the other questions above.

Something you may want to consider is switching to CalVer for typing itself, such that we end up saying something like "Python 3.7.0 includes typing 2017.12.1".

My experience has been that CalVer is just better for interoperability specifications, since it inherently conveys information about the age of the specification. Saying "We target typing 2017.12.1" in 2018 immediately lets people know they're going to need some pretty up to date software to run a project that has that caveat on it. By contrast, saying the same thing in 2021 means most things released in the past 3 years should be able to handle it.

Such an approach also avoids future confusion if the final version of Python 3.7 were to start bundling Python 3.8's version of typing.

Cheers, Nick.

-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia

More information about the Python-Dev mailing list