Remove the _Unit factory, and make it a class method. #131
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.
There is a somewhat bizarre
_Unit
factory function that is there to allow construction of a unit if we already have the Udunits handle, and don't need to go through full__init__
.Unfortunately, this factory is hiding the fact that it is an optimisation, and should IMO be much more explicit about the fact. The problem of how well concealed the
_Unit
vsUnit
is highlighted by the existing implementation, which is being addressed in #125. In this PR, I fix this by not short-circuiting__init__
when we don't need to.This then is an alternative to #125.