Pin pytensor to < 2.31#493
Closed
zaxtax wants to merge 1 commit into
Closed
Conversation
This pins the version while the following gets resolved pymc-devs/pytensor#1425
Member
|
Did you link the right issue? Scan vectorize has never been supported, it's not a regression. My preference would be against pinning, because I really want some of the features in 2.31. Is this related to the marginalize with minibatch bug? |
Contributor
Author
|
No, this is just for the existing marginalize tests that used to pass and don't after the 2.31 release |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
pytensor introduced some regressions since 2.31
This pins the version below that while the following gets resolved
pymc-devs/pytensor#1425