Explicitly typed version of Python?

No You can not have cake and eat cake.

Python is great because its dynamically typed! Period. (That's why it have such nice standard library too)

There is only 2 advantages of statically typed languages 1) speed - when algorithms are right to begin with and 2) compilation errors

As for 1)

• Use PyPi,
• Profile,
• Use ctype libs for great performance.

Its typical to have only 10% or less code that is performance critical. All that other 90%? Enjoy advantages of dynamic typing.

As for 2)

• Use Classes (And contracts)
• Use Unit Testing
• Use refactoring
• Use good code editor

Its typical to have data NOT FITTING into standard data types, which are too strict or too loose in what they allow to be stored in them. Make sure that You validate Your data on Your own.

Unit Testing is must have for algorithm testing, which no compiler can do for You, and should catch any problems arising from wrong data types (and unlike compiler they are as fine grained as you need them to be)

Refactoring solves all those issues when You are not sure if given changes wont break Your code (and again, strongly typed data can not guarantee that either).

And good code editor can solve so many problems... Use Sublime Text for a while. And then You will know what I mean.

(To be sure, I do not give You answer You want to have. But rather I question Your needs, especially those that You did not included in Your question)

The short answer is no. What you are asking for is deeply built into Python, and can't be changed without changing the language so drastically that is wouldn't be Python.

I'm assuming you don't like variables that are re-typed when re-assigned to? You might consider other ways to check for this if this is a problem with your code.

From python 3, the ability to use type annotation was introduced into the python standard with PEP 3017.

Fast-forward to python 3.5 and PEP 0484 builds on this to introduce type hinting along with the typing module which enables one to specify the types for a variable or the return type of a function.

from typing import Iterator

def fib(n: int) -> Iterator[int]:
    a, b = 0, 1
    while a < n:
        yield a
        a, b = b, a + b

Above example taken from https://pawelmhm.github.io

According to the 484 notes:

While these annotations are available at runtime through the usual __annotations__ attribute, no type checking happens at runtime. Instead, the proposal assumes the existence of a separate off-line type checker which users can run over their source code voluntarily. Essentially, such a type checker acts as a very powerful linter. (While it would of course be possible for individual users to employ a similar checker at run time for Design By Contract enforcement or JIT optimization, those tools are not yet as mature.)

tl;dr

Although python provides this form of "static typing", it is not enforced at run time and the python interpreter simply ignores any type specifications you have provided and will still use duck typing to infer types. Therefore, it is up to you to find a linter which will detect any issues with the types.

Furthermore

The motivation for including typing in the python standard was mostly influenced by mypy, so it might be worth checking them out. They also provide examples which may prove useful.