Unit Awareness: Possible Future Breaking Change

[coddingtonbear]

Python-myfitnesspal currently, for at least most of the core functionality, has a concept of "unit-awareness" in which, while this feature is enabled, measurements are returned bundled with their unit using python-measurement objects. There are some problems though:

1. Python-measurement is only barely maintained at this point. It's a side-project of mine and I have to tell you I haven't thought about it in years, and there are much better alternatives available now.
2. Having a unit awareness feature that can be turned-on/off at the client level makes types a little difficult (right now: the types assume that you're not using unit awareness).
3. Most contributions aren't unit-aware, and instead just use bare floats or integers.

So, what I'm thinking about is a future breaking change in the next major release of Python-myfitnesspal in which either:

• (A) We switch to Pint for measurement objects and require that interactions with the library use those (i.e. that this would not be a feature that can be turned-off). or
• (B) We drop support for measurement awareness altogether. This is the easiest path, probably, and since unit awareness it 'off' by default, this is definitely the direction I'm leaning unless somebody convinces me out of it.

Of course that's going to be a little way down the road, though; I wonder, though, if any of you all have any thoughts or opinions on this?