TST: Restrict numpy version for dynesty compatibility #981
Conversation
This file contains hidden or 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
Collaborator
Author
|
I made this branch on this fork as it allows me to manually trigger a rebuild of the containers before this is merged. |
mj-will
approved these changes
Aug 26, 2025
Collaborator
Author
|
I merged this without passing as there are related PRs that need to be merged also. |
mj-will
pushed a commit
to mj-will/bilby
that referenced
this pull request
Oct 16, 2025
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.
After we fix the numpy incompatibilities in #979 and #980 the remaining numpy issue will be in dynesty, since that will need #950 we should be able to remove this pin when a new release of dynesty is available.