PyPy compatibility
See original GitHub issueThis was raised on twitter, and may be important for some users. Currently msgspec
is written as a c extension using some private cpython apis, making it incompatible with pypy. It would be good to have a pypy compatible build, whether through changes to the c extension or through a separate pure python release. Either seems fine to me, provided the result doesn’t decrease cpython performance noticeably.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Python compatibility - PyPy
Python compatibility. The goal of this page is to point out some of the differences between running python with PyPy and with CPython ......
Read more >PyPy - packages
PyPy's Python packages compatibility. PyPy is a fast, compliant alternative implementation of the Python language. Nearly all Python packages install ...
Read more >Frequently Asked Questions - PyPy documentation
Which Python version (2.x?) does PyPy implement?¶. PyPy comes in two versions: one is fully compatible with Python 2.7;; the other is fully ......
Read more >PyPy3 v5.5.0 - PyPy documentation
Coming four months after PyPy3.3 v5.2, it improves compatibility with Python 3.3 (3.3.5). We strongly recommend updating from previous PyPy3 versions.
Read more >PyPy v7.3.6: release of python 2.7, 3.7, and 3.8
The interpreters are based on much the same codebase, thus the multiple release. This is a micro release, all APIs are compatible with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is not something I plan on supporting in a volunteer-only basis (if someone wanted to pay for this, I might be willing to expand support).
A few reasons:
msgspec
is heavily tied to the CPython c-api for performance. PyPy does support a subset of the CPython c-api, but it does so in a way that is not very performant, and isn’t 100% compatible. We could add shims everywhere that’s needed to makemsgspec
PyPy compatible, but that would muddy up the code, increasing our maintenance burden.Thanks for clarifying this. I think we are fine not having pypy support.