3 ms·
That helps not to break an existing codebase. But not if there's a nice new library you really have a need for that uses new 3.8 features, and you can't use it
by coldtea 6y ago
That helps not to break an existing codebase.
But not if there's a nice new library you really have a need for that uses new 3.8 features, and you can't use it because you're stuck with 3.6 for example...
- rbanffy 6y agoWe can always offer a PR that allows the library to run on older versions. I am limited to 3.6 on many environments and would be extremely happy to know others on 3.6 have better library support. Having said that, It's not something I feel. I know some things can get faster and some syntax can be improved, but, so far, I'm pretty OK with those envs running on 3.6. As for me, locally I use 3.8. If I do any 3.8-ism, CI will catch it.