use application reg in docs#1931
Open
andrewgsavage wants to merge 8 commits into
Open
Conversation
CodSpeed Performance ReportMerging #1931 will degrade performances by 20.71%Comparing Summary
Benchmarks breakdown
|
Collaborator
Author
|
Some small changes to the text in docs/getting/tutorial.rst |
Owner
|
As I mentiones before, I like this change. I was discussing this with some friends which are not pint users. A lot of them ask "why get_application_registry?, Why so long?, Do you really need the application part of the name?" Shall we bikeshed this public API? (we can still leave |
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
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.
pre-commit run --all-fileswith no errorsreplaces
ureg = pint.UnitRegistry()withureg = pint.get_application_registry()in the docs