-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support PyPy #544
Support PyPy #544
Conversation
fb1e656
to
88ab11d
Compare
I'll mark this as ready for review. However, it requires nightly builds of PyPy (for pypy/pypy#5081), thus - no wheels yet. Unfortunately, I don't know how to enable cache on PyPy. I don't see anything wrong in the current approach (well, except that we should free cache somewhere in the m_free module method), working for CPython. So, maybe it's a PyPy issue. Two bugs were discovered. Maybe I should make a separate pr with last three commits? |
Does PyPy optimize the creation of new gmpy2 objects? Maybe the penalty for disabling cache is not severe....
A single PR is fine with me. |
I doubt.
Maybe. But I don't know, as working with cache is not tested here. |
747adfb
to
72cb08b
Compare
Closes aleaxit#523
Docs (for PyBytes_AsString) says: The data must not be modified in any way, unless the object was just created using PyBytes_FromStringAndSize(NULL, size). That's not the case for GMPy_MPFR_To_Binary(). So, PyPy seems to be right in rejecting modifications.
72cb08b
to
b6bd13b
Compare
Thanks, |
Closes #523