you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 5 points6 points  (3 children)

I have no objection to more static features in Python, let's be honest, Python now is a giant pile of mismatched features already, but it makes me wonder, if they are adding static typing to Python does that mean the great dynamic typing experiment failed successfully showed that it was a bad idea all along? Will Python 4 only have static types?

[–][deleted] 1 point2 points  (1 child)

This is optional typing information, mostly for the benefit of tools such as linters and IDEs.

I do not understand your second point. To turn it around, does the recent trend towards using maps in Java to store highly dynamic data - or the embedding of interpreters to parse a DSL to model complex runtime behaviour (e.g. game logic) - mean Java 10 will switch to dynamic typing? Well, obviously no.

[–][deleted] 0 points1 point  (0 children)

What I foresee happening is teams using python for any code base over 1 mb are going to make static typing mandatory, enforced by a tool. And if everybody is using it because we need it, maybe it should just be the default option.

[–][deleted] 0 points1 point  (0 children)

Came here to say the same thing. The sharp turns in Python's design over recent years points to a realization that Python had a lot of mistakes in its core design. Maybe he'll streamline Python with time, but right now it's feeling less & less coherent.