-
-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
BUG: Pip 20.3 is causing Linux py38 np dev pipeline to fail #38221
Labels
CI
Continuous Integration
Dependencies
Required and optional dependencies
Upstream issue
Issue related to pandas dependency
Milestone
Comments
phofl
added
Bug
Needs Triage
Issue that has not been reviewed by a pandas team member
CI
Continuous Integration
and removed
Needs Triage
Issue that has not been reviewed by a pandas team member
labels
Dec 1, 2020
See pypa/pip#9186 |
So once this is fixed upstream, we should revert the pin. |
Noting that, from my PoV, the underlying issue here is that pip's getting wheels with versions that are not valid (see pypa/pip#9186 (comment)) and this is the first version of pip where it rejects such wheels by default. The fix probably needs to happen wherever the wheels are being generated. |
lithomas1
added
Dependencies
Required and optional dependencies
Upstream issue
Issue related to pandas dependency
and removed
Bug
labels
May 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CI
Continuous Integration
Dependencies
Required and optional dependencies
Upstream issue
Issue related to pandas dependency
The first pipeline to fail was 2a115d5 which also was the first pipeline using pip 20.3
This seems to be a problem with scipy version.
@jreback @jbrockmendel @jorisvandenbossche
Last pipeline to work:
https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=49130&view=logs&j=eab14f69-13b6-5db7-daeb-7b778629410b&t=71ac627c-7b38-59b1-014b-81753001ec5e
First fo fail:
https://dev.azure.com/pandas-dev/pandas/_build/results?buildId=49159&view=logs&j=eab14f69-13b6-5db7-daeb-7b778629410b&t=71ac627c-7b38-59b1-014b-81753001ec5e&l=333
The text was updated successfully, but these errors were encountered: