-
Notifications
You must be signed in to change notification settings - Fork 468
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
numeric formatting overriding default_format
in 0.19
#1501
Comments
the behavior you see in Arguably, this became a bit confusing because there was such a big delay between the releases while the revert was intended for a quick bugfix release, but the idea is that we do a proper deprecation cycle before enabling the entirely separate formats. @hgrecco, what do you think about adding a setting to the registry that controls this? That way people can explicitly select which behavior to use, and the deprecation might also become a bit easier. |
@keewis I am ready to release 0.19.1. Do you want to include your patch in this release or in 0.19.2? |
not sure. I was planning to investigate this evening, but I can't promise anything. If it's not a lot of work for you to do the release I'd say doing two separate bugfix releases might be worth considering? |
agreed! |
thank you for looking into this so quickly |
I noticed that the unit string formatting changed slightly with the new
0.19
releasespecifically, when setting a custom
default_format
on theUnitRegistry
the setting is now lost when printing with additional numeric formatting options (e.g..2f
) (see the code below)is this intended or is there a different way to keep the default unit formatting style?
0.18
0.19
The text was updated successfully, but these errors were encountered: