-
Notifications
You must be signed in to change notification settings - Fork 240
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
Fix AppVeyor's PyPy failure on finding libffi #371
Fix AppVeyor's PyPy failure on finding libffi #371
Conversation
c7d51d9
to
d8e0b54
Compare
Progress. PyPy 2.7 now works with the fixes. Now waiting for a nightly build of 3.6 and maybe later a release with these fixes. |
This reverts commit f1c4ebb.
3877508
to
f909242
Compare
Assuming you don't want to merge this until these fixes are in an official Pypy release? |
Hmmm, I don't know. I guess we could ping PyPy again and ask what their short term plans on a patch release? I actually still need to fix a mistake I made in a PR on f-strings, there, that's probably blocking a release :-| I should get to that this weekend. |
Closing, since 7.3.2 is out and can almost be merged (see #430). |
Cfr. https://foss.heptapod.net/pypy/pypy/issues/3229 and https://foss.heptapod.net/pypy/pypy/merge_requests/726