Dave

Oh, I was working on my own solution and just finished as well. I didn't know about the group api and the way I did it is definitely not the...

I was experimenting with some stuff and found some possibly unwanted behavior in `pint.systems.Group`: ```py >>> ureg.c, ureg.speed_of_light (, ) >>> ureg.constants.c, ureg.constants.speed_of_light (, ) # why is c returning...

Is this also desired behavior? ```py >>> ureg.define('testing = 0.8 * meter') >>> 'testing' in ureg.constants.members False >>> ureg.constants.testing # should not be accessible # how? ``` Seems anything defined...

Ah, full compatibility with Fraction and Decimals can be achieved by initializing the unit registry with `non_int_type=decimal.Decimal` etc... **Change line 4 in the text you sent to `ureg = UnitRegistry(non_int_type=Decimal)`...

Bit tricky to track it down, but it turns out it was `tokenize.tokenize` not recognizing the character as a number type. It's already pretty hacky but fixing mixed numbers would...

Any progress on this? I'd really like to be able to use this along with the new `percent` addition. > I haven't tested it, but I suspect the performance impact...

> current behavior has no benefits over it Just something to consider: I’ve experienced issues with high-framerate videos reporting an incorrect framerate and dropping a massive amount of frames on...

Awesome, thanks! 👍

lvsfunc has been re-structured over the past few days and is no longer just a file in the repo, it's a "proper" looking Python package now, so not sure how/if...

FWIW this affects the new "%" percent sign pre-processor too and was brought up in that PR. The .to() string should have the same pre-processors applied IMO.