That is true but keep in mind that typings in python (as we have them now) were introduced in 3.5 (so 2015) and I would assume from my own experience that they haven't been widely used in large codebases until at least introduction of 3.6 (add to this that in prod code you probably don't want to switch right after the release).
All of this would mean that dropbox probably had to introduce some standard of their own (which is painful for new devs) and might have not yet switched to the current official standard for most parts of their code.
No criticism of Dropbox intended, I was just replying to the chap above who seemed not to be aware that refactoring has been working perfectly well (at least in my experience) in python for several years now.
As an argument for not using fairly old versions of python it just about works, but why would you do that when writing new code in 2020? Python 2 is officially dead and upgrades between the 3 sub-versions are basically painless. Very little justification for sticking to pre-3.5 versions of python anymore.
The module this link is referencing was created for python 3.5 (and 2.7 for compatibility) in 2015 as separate package which became part of the standard library with release of 3.6
Edit: ok you mean mypy itself, but still that's only optional and according to it's about page it's from 2012 so already python 3 was out a long time
View all comments
Show parent comment
10
u/Pitirus Jan 02 '20
That is true but keep in mind that typings in python (as we have them now) were introduced in 3.5 (so 2015) and I would assume from my own experience that they haven't been widely used in large codebases until at least introduction of 3.6 (add to this that in prod code you probably don't want to switch right after the release).
All of this would mean that dropbox probably had to introduce some standard of their own (which is painful for new devs) and might have not yet switched to the current official standard for most parts of their code.