Skip to content
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

Unpin scipy #198

Merged
merged 2 commits into from
Aug 12, 2024
Merged

Unpin scipy #198

merged 2 commits into from
Aug 12, 2024

Conversation

jobrachem
Copy link
Contributor

Cannot reproduce the issue reported in #185, so this PR simply removes the pin to scipy<=1.12.
Closes #185

Opened as a draft to see if our CI passes.

@jobrachem jobrachem self-assigned this Jul 24, 2024
@jobrachem
Copy link
Contributor Author

The issue in the CI does not originate from scipy, but instead from incompatibility of tensorflow probability to numpy 2.0. At first, I could not reproduce the issue locally, because locally, I installed using the pmc specs, and pymc currently pins to numpy<2.

The current solution is to pin numpy in liesel to <2.0, too, until the downstream issue is addressed. There's already an issue in the tensorflow probability repo:

Once this is addressed, we can unpin numpy, since pymc correctly handles its dependency on numpy itself.

@jobrachem jobrachem mentioned this pull request Jul 24, 2024
@jobrachem jobrachem marked this pull request as ready for review July 24, 2024 19:35
@GianmarcoCallegher GianmarcoCallegher merged commit 147ffc9 into main Aug 12, 2024
4 checks passed
@GianmarcoCallegher GianmarcoCallegher deleted the compatibility-to-scipy-1_13 branch August 12, 2024 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compatibility to scipy 1.13
2 participants