-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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
ENH: PyPy Support #42509
Comments
@lithomas1 removed milestone. we can assess whether any PRs could be backported (if/when opened) otherwise the milestone is normally only used to track regressions and PRs requiring backport. |
Whoops, my bad. |
It seems the third step, enable tests here, should be the first. As I read things, the CI is currently building pandas but not testing it, and uses a PyPy from conda-forge via miniconda. So I think I should
That should get test failures down to a point where it makes sense to
Locally, that gets ubuntu down to 84 test failures in about 1hr22m, which is not that much longer than the other workflows under xref @h-vetinari (since I think work here should precede work on the pandas-feedstock PR) |
Getting error with import pandas, I am trying to use pandas in pypy, please help me with this issue
Here is my installation
|
This is a bug in the current PyPy feedstock. See conda-forge/pypy3.6-feedstock#109 |
Its working now. Thank you @mattip |
Are there any plans to publish pypy wheels by default (for every release in the future)? |
It looks like conda-forge is dropping support for pypy - maybe we should also consider dropping it at this point? |
Tracker for getting PyPy support
-
We can probably add this for 1.3.1.- Actually, it will probably be easier to add after 1.3.1, since 1.3.1 includes a fix for the PyPy build.
The text was updated successfully, but these errors were encountered: