Deprecation warning for float8_e4m3b11 #77
Merged
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
Merged
hawkinsp
approved these changes
Jun 6, 2023
jakevdp
force-pushed
the
deprecate-e4m3b11
branch
from
75f26d5 to
db7782d
Compare
jakevdp
force-pushed
the
deprecate-e4m3b11
branch
from
db7782d to
8003d2d
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.
float8_e4m3b11has been renamed tofloat8_e4m3b11fnuzfor more consistency with other dtype names in the package. We'll remove this later (probably in ml_dtypes v0.3.0) but for the upcoming 0.2.0 release it should raise a deprecation warning.