Jules Chéron

Yes for now `get_compatible_units` use with system only filter with units added (through group inclusion) to the system not with (base units , derived units and composed units) as stated...

True we should have commutative operations on any operations IMO it would make the use of the library more consistent. I don't think it will change the way we use...

> What is the expected result: (a) 24 inch, (b) 2 foot, (c) 0.6096meter? For the typical user (c) is least expected, probably (b) is the nices. On the other...

I can give it a shot.

@hgrecco About operation with same unit, I think i'm gonna change my mind. Taking the most precise unit is simpler & maybe the best option. Numpy does that with `timedelta`...

Same here, if you want this I'd suggest wrapping this in a function. I know it sounds appealing at first, but I'd rather put those kind of examples in the...

@wenx-z can you describe the error you encounter ? it should work even if the numpy version have removed it.

Sure, do you want to try to file a PR ? I think we're gonna keep repr, to ignore any form of localization but str should be localized if specified.

When using Quantity with `m_as` you will get the magnitude with the same unit as this Quantity. It is the expected behaviour, I've just realized this function is not present...

A bit of context here, a lot of methods in pint accepts `UnitLike` types (str, Unit, UnitContainer, Quantity) to use it as a unit in public methods. This is the...