-
Notifications
You must be signed in to change notification settings - Fork 250
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
32-bit Linux running on 64-bit ARM arch should have platform "linux_armv7l" #234
Conversation
I have no idea why the coverage dropped... |
…rmv7l". Currently on a 32-bit OS that runs on a 64-bit ARM CPU (ARM-v8, aarch64), _linux_platforms returns the incorrect string. This commit fixes this issue by following the solution similar to that of the x86_64/x86 pair.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are unfortunately failing.
Co-Authored-By: Brett Cannon <[email protected]>
Co-Authored-By: Brett Cannon <[email protected]>
No idea what the lint error means.. |
@xuhdev you need to run black over your code to fix your formatting. |
18c0f14
to
2667118
Compare
Directly calling "pytest" sometimes breaks tests on "pypy", such as pypa#234. As explained from pypy website <https://docs.pytest.org/en/latest/usage.html>: > ["python -m pytest"] is almost equivalent to invoking the command line > script pytest [...] directly, except that calling via python will also > add the current directory to sys.path. Note that the pytest script is not directly invoked in tests for other Python interpreters.
Directly calling "pytest" sometimes breaks tests on "pypy", such as pypa#234. As explained from pypy website <https://docs.pytest.org/en/latest/usage.html>: > ["python -m pytest"] is almost equivalent to invoking the command line > script pytest [...] directly, except that calling via python will also > add the current directory to sys.path. Note that, unlike tests for pypy, the pytest script is not directly invoked in tests for other Python interpreters.
Directly calling "pytest" sometimes breaks tests on "pypy", such as pypa#234, because the actual current code is untested. As explained from pypy website <https://docs.pytest.org/en/latest/usage.html>: > ["python -m pytest"] is almost equivalent to invoking the command line > script pytest [...] directly, except that calling via python will also > add the current directory to sys.path. Note that, unlike tests for pypy, the pytest script is not directly invoked in tests for other Python interpreters.
@brettcannon All tests have passed now. Could you review again? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a clean-up of the test code to cut down on repetitiveness.
Co-Authored-By: Brett Cannon <[email protected]>
Co-Authored-By: Brett Cannon <[email protected]>
Ping @brettcannon |
OK to have this merged w/o my review. |
As pypa/packaging#234 has been merged.
The bug in pypa/packaging#234 is now in the current stable pip.
The bug in pypa/packaging#234 is now in the current stable pip.
Currently on a 32-bit OS that runs on a 64-bit ARM CPU (ARM-v8,
aarch64),
_linux_platforms
returns the incorrect string. This commitfixes this issue by following the solution similar to that of the
x86_64/x86 pair.
Ported from pypa/pip#7352
cc @chrahunt @bdwyer2