[tpoacher]

and mypy is "an optional static type checker for Python" [0]

Given that both pypy (through RPython) and mypy deal with static type checks in some sense, I kept confusing the two projects until recently.

Also, I just learnt (from another comment in this post) about mypyc [1], which seems to complete the circle somehow in my mind.

  [0] https://www.mypy-lang.org/
  [1] https://github.com/mypyc/mypyc

[LtWorf]

pypy existed long before type annotations were a thing

[masklinn]

And JITs often don't care for type specifications as they can generally get better info from the runtime values, need to support that anyway, and for languages like python the type specifications can be complete lies anyway. They also might support (and substitute) optimised versions of types internally (e.g. pypy has supported list specialisation for a long time).

Maybe it's changed since, but last I checked the JVM's JIT did not care at all for java's types.

Which is not to say JITs don't indirectly benefit mind, type annotations tend to encourage monomorphic code, which JITs do like a lot. But unlike most AOT compilers it's not like they mind that annotations are polymorphic as long as the runtime is monomorphic...

[rcxdude]

PyPy may not care in principle, but RPython does, being a kind of python dialect designed for static compilation that is intended for writing JIT engines like PyPy.

[canjobear]

Don't forget about RPy https://pypi.org/project/rpy2/2.2.7/

[gcarvalho]

Don't forget about dmypy, the daemon version of mypy.

https://mypy.readthedocs.io/en/stable/mypy_daemon.html