Bump Bijectors to 0.14.0 #2384
Draft
Bump Bijectors to 0.14.0 #2384
Conversation
This file contains 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
penelopeysm
force-pushed
the
py/bump-bijectors
branch
2 times, most recently
from
def68db
to
cf6b195
Compare
14 tasks
penelopeysm
force-pushed
the
py/bump-bijectors
branch
from
cf6b195
to
1d427f1
Compare
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.
Following on from TuringLang/Bijectors.jl#337.
I dropped support for 0.13 because 0.13 requires Tapir not Mooncake anyway.
Don't merge yet; the rest of TuringLang needs to be Bijectors-0.14-compatible, and it isn't.