mypy
beartype
Our great sponsors
mypy | beartype | |
---|---|---|
112 | 18 | |
17,541 | 2,420 | |
1.6% | 4.8% | |
9.7 | 9.4 | |
2 days ago | 2 days ago | |
Python | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mypy
- The GIL can now be disabled in Python's main branch
-
Polars – A bird's eye view of Polars
It's got type annotations and mypy has a discussion about it here as well: https://github.com/python/mypy/issues/1282
- Static Typing for Python
-
Python 3.13 Gets a JIT
There is already an AOT compiler for Python: Nuitka[0]. But I don't think it's much faster.
And then there is mypyc[1] which uses mypy's static type annotations but is only slightly faster.
And various other compilers like Numba and Cython that work with specialized dialects of Python to achieve better results, but then it's not quite Python anymore.
[0] https://nuitka.net/
[1] https://github.com/python/mypy/tree/master/mypyc
- Introducing Flask-Muck: How To Build a Comprehensive Flask REST API in 5 Minutes
-
WeveAllBeenThere
In Python there is MyPy that can help with this. https://www.mypy-lang.org/
-
It's Time for a Change: Datetime.utcnow() Is Now Deprecated
It's funny you should say this.
Reading this article prompted me to future-proof a program I maintain for fun that deals with time; it had one use of utcnow, which I fixed.
And then I tripped over a runtime type problem in an unrelated area of the code, despite the code being green under "mypy --strict". (and "100% coverage" from tests, except this particular exception only occured in a "# pragma: no-cover" codepath so it wasn't actually covered)
It turns out that because of some core decisions about how datetime objects work, `datetime.date.today() < datetime.datetime.now()` type-checks but gives a TypeError at runtime. Oops. (cause discussed at length in https://github.com/python/mypy/issues/9015 but without action for 3 years)
One solution is apparently to use `datetype` for type annotations (while continuing to use `datetime` objects at runtime): https://github.com/glyph/DateType
-
What's New in Python 3.12
PEP 695 is great. I've been using mypy every day at work in last couple years or so with very strict parameters (no any type etc) and I have experience writing real life programs with Rust, Agda, and some Haskell before, so I'm familiar with strict type systems. I'm sure many will disagree with me but these are my very honest opinions as a professional who uses Python types every day:
* Some types are better than no types. I love Python types, and I consider them required. Even if they're not type-checked they're better than no types. If they're type-checked it's even better. If things are typed properly (no any etc) and type-checked that's even better. And so on...
* Having said this, Python's type system as checked by mypy feels like a toy type system. It's very easy to fool it, and you need to be careful so that type-checking actually fails badly formed programs.
* The biggest issue I face are exceptions. Community discussed this many times [1] [2] and the overall consensus is to not check exceptions. I personally disagree as if you have a Python program that's meticulously typed and type-checked exceptions still cause bad states and since Python code uses exceptions liberally, it's pretty easy to accidentally go to a bad state. E.g. in the linked github issue JukkaL (developer) claims checking things like "KeyError" will create too many false positives, I strongly disagree. If a function can realistically raise a "KeyError" the program should be properly written to accept this at some level otherwise something that returns type T but 0.01% of the time raises "KeyError" should actually be typed "Raises[T, KeyError]".
* PEP 695 will help because typing things particularly is very helpful. Often you want to pass bunch of Ts around but since this is impractical some devs resort to passing "dict[str, Any]"s around and thus things type-check but you still get "KeyError" left and right. It's better to have "SomeStructure[T]" types with "T" as your custom data type (whether dataclass, or pydantic, or traditional class) so that type system has more opportunities to reject bad programs.
* Overall, I'm personally very optimistic about the future of types in Python!
[1] https://github.com/python/mypy/issues/1773
-
Mypy 1.6 Released
# is fixed: https://github.com/python/mypy/issues/12987.
-
Ask HN: Why are all of the best back end web frameworks dynamically typed?
You probably already know but you can add type hints and then check for consistency with https://github.com/python/mypy in python.
Modern Python with things like https://learnpython.com/blog/python-match-case-statement/ + mypy + Ruff for linting https://github.com/astral-sh/ruff can get pretty good results.
I found typed dataclasses (https://docs.python.org/3/library/dataclasses.html) in python using mypy to give me really high confidence when building data representations.
beartype
-
Writing Python Like Rust
https://github.com/beartype/beartype
I wish more people started using Beartype, it makes Python bearable
-
ChatGPT Git Hook Writes Your Commit Messages
I saw this on /r/Python the other day...
- When the client's management is happy but their dev team is a pain
-
Returning to snake's nest after a long journey, any major advances in python for science ?
As other folks have commented, type hints are now a big deal. For static typing the best checker is pyright. For runtime checking there is typeguard and beartype. These can be integrated with array libraries through jaxtyping. (Which also works for PyTorch/numpy/etc., despite the name.)
-
What are some features you wish Python had?
Maybe you're looking for https://github.com/beartype/beartype for runtime type enforcement; it's only at function calls, though, but probably a decent solution for codebases that are not completely typed for MyPy or pyright.
-
svg.py: Type-safe and powerful Python library to generate SVG files
It is though, if you add a type checker to your pipeline and use it without any escape hatches such as `Any` or `type: ignore`, you are essentially making the promise that your code is statically typed. But I say it is a matter of perspective because in my opinion runtime type checking should be avoided if we can get away with statically typed code, but there are type checkers that perform runtime type checking via annotations such as [Beartype](https://github.com/beartype/beartype) (with some trickery like assuming homogenous data structures as to not have to check every element of every structure). Anyway the definition of "type safe" is not 100% even in compiled languages.
- Python’s “Type Hints” are a bit of a disappointment to me
-
What's the best practice to validate parameter types at runtime in Python, with and without a third-party module?
There is the beartype project.
-
Statically typed Python
Personally I find working around mypy's quirks to be more effort than it's worth, so to offer another option: typeguard or beartype can be used to perform run-time type checking.
- Beartype: Unbearably fast runtime type checking in Python
What are some alternatives?
pyright - Static Type Checker for Python
typeguard - Run-time type checker for Python
ruff - An extremely fast Python linter and code formatter, written in Rust.
pydantic - Data validation using Python type hints
pyre-check - Performant type-checking for python.
mypyc - Compile type annotated Python to fast C extensions
black - The uncompromising Python code formatter
toit - Program your microcontrollers in a fast and robust high-level language.
pytype - A static type analyzer for Python code
benchmarks - Some benchmarks of different languages
Kategory - Λrrow - Functional companion to Kotlin's Standard Library