py2many
mypy
Our great sponsors
py2many | mypy | |
---|---|---|
29 | 112 | |
583 | 17,380 | |
2.1% | 1.8% | |
8.3 | 9.8 | |
about 1 month ago | 7 days ago | |
Python | Python | |
MIT License | 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.
py2many
-
py2many VS kithon - a user suggested alternative
2 projects | 17 Jun 2023
-
Why I'm still using Python
https://github.com/py2many/py2many/blob/main/doc/langspec.md
Reimplement a large enough, commonly used subset of python stdlib using this dialect and we may be in the business of writing cross platform apps (perhaps start with android and Ubuntu/Gnome)
-
Codon: A high-performance Python compiler
For py2many, there is an informal specification here:
https://github.com/py2many/py2many/blob/main/doc/langspec.md
Would be great if all the authors of "python-like" languages get together and come up with a couple of specs.
I say a couple, because there are ones that support the python runtime (such as cython) and the ones which don't (like py2many).
-
A Python-compatible statically typed language erg-lang/erg
It'd not fully solve your issue, but have you ever seen https://github.com/py2many/py2many ?
-
Omyyyy/pycom: A Python compiler, down to native code, using C++
Cython doesn't consume python3 type hints and needs special type hints of its own. But it's certainly more mature than other players in the field.
What we need is a rpython suitable for app programming and a stdlib written in that dialect.
https://github.com/py2many/py2many/blob/main/doc/langspec.md
- I made a Python compiler, that can compile Python source down to fast, standalone executables.
- PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
-
Show HN: prometeo – a Python-to-C transpiler for high-performance computing
No intermediate AST. To understand the various stages of transpilation and separation of language specific and independent rewriters, this file is a good starting point:
https://github.com/adsharma/py2many/blob/main/py2many/cli.py...
This is awesome! The direction of using a subset of python, while leveraging the user base and static typing to accomplish some other everyday task in a different language is very legit IMO.
I took a cursory look at:
https://github.com/zanellia/prometeo/blob/master/prometeo/cg...
It seems quite similar in spirit to
https://github.com/adsharma/py2many/blob/main/pyrs/transpile...
I'm not spending much time on py2many last few months (started a new job). Let me know if any of it sounds useful - especially the ability to transpile to 7-8 languages including Julia, C++ and Rust.
-
Implicit Overflow Considered Harmful (and how to fix it)
Link to the test that's relevant for this discussion:
https://github.com/adsharma/py2many/blob/main/tests/cases/in...
This is an explicit deviation from python's bigint, which doesn't map very well to systemsey languages. The next logical step is to build on this to have dependent and refinement types.
Work in progress here:
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
-
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.
- Introducing Flask-Muck: How To Build a Comprehensive Flask REST API in 5 Minutes
-
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!
-
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.
-
Sharing Saturday #472
The in-progress tutorial is here in the official documentation. It sucks that I can never seem to make quick progress on this. Trying to do something clever with Protocols ended up with me making a pull request on the Mypy project for something that likely wasn't critical after all.
-
Writing Python like it's Rust
I'm also 100% convinced most people who use mypy don't realize the myriad ways it just silently stopps typing things or just silently crashes with a 0 exit code. Even if you configure it to warn untyped functions etc. It will still just not work properly in some of circumstances and you will literally never know until you debug a bug that just happened to trigger it. There are over 1.4k open but tickets it's such a broken piece of software: https://github.com/python/mypy/issues?q=is%3Aissue+is%3Aopen...
The involvement of Guido in mypy is such a tragedy.
What are some alternatives?
pyright - Static Type Checker for Python
ruff - An extremely fast Python linter and code formatter, written in Rust.
pyre-check - Performant type-checking for python.
black - The uncompromising Python code formatter
pytype - A static type analyzer for Python code
pydantic - Data validation using Python type hints
Flake8 - flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
typing - Python static typing home. Hosts the documentation and a user help forum.
PythonBuddy - 1st Online Python Editor With Live Syntax Checking and Execution
bandit - Bandit is a tool designed to find common security issues in Python code.
beartype - Unbearably fast near-real-time hybrid runtime-static type-checking in pure Python.
pylama - Code audit tool for python.