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
PyPy: Update interpreter, unbreak many packages #55182
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MostAwesomeDude
force-pushed
the
pypy-mock
branch
from
February 10, 2019 17:20
42e8ae0
to
1a20a32
Compare
@GrahamcOfBorg build pypyPackages.mock |
1 similar comment
@GrahamcOfBorg build pypyPackages.mock |
GrahamcOfBorg
added
10.rebuild-darwin: 1-10
10.rebuild-linux: 1-10
and removed
10.rebuild-darwin: 0
10.rebuild-linux: 0
labels
Feb 10, 2019
|
MostAwesomeDude
force-pushed
the
pypy-mock
branch
from
February 12, 2019 04:06
b2b153c
to
398f4fc
Compare
MostAwesomeDude
changed the title
Unbreak many PyPy packages
PyPy: Update interpreter, unbreak many packages
Feb 12, 2019
nix-repl> map (s: s.isPyPy) [ python python3 pypy pypy3 ] [ false false true true ]
Note that this bumps both the 2.7 and 3.5 flavors of PyPy.
Not sure whether this is right TBH.
I looked at some of the failing tests and now I'm feeling rather queasy.
Unbreaks many PyPy packages.
Calling Trial directly enables PyPy support, since our PyPy packages only have a `pypy` binary rather than `python`.
Included a comment for the upstream commit where this was fixed recently: pallets/werkzeug@1cfdcf9
It Just Works now that everybody's versions have been bumped.
MostAwesomeDude
force-pushed
the
pypy-mock
branch
from
March 4, 2019 12:37
da4f1e8
to
f2cdd61
Compare
pushed to staging |
Hydra has been failing to build pypy-7.0.0 and pypy3-7.0.0, and so has my system. Was this ever tested using sandboxing? |
andersk
referenced
this pull request
Jul 31, 2019
swiften is broken since 2018-10-18: x86_64-linux: https://hydra.nixos.org/build/97180305 aarch64-linux: https://hydra.nixos.org/build/97193043 pypy is broken since 2019-05-29: x86_64-linux (pypy): https://hydra.nixos.org/build/97214777 x86_64-linux (pypy3): https://hydra.nixos.org/build/97221287 The builds for swiften and reposurgeon (depends on pypy) regularly fail during rebuilds for SCons updates (e.g. [0]). [0]: #65392
And…now pypy is marked as broken (8760c69). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
I like PyPy.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)This PR updates the PyPy interpreter versions and unbreaks many packages, including the ubiquitous Numpy.