Jules Chéron

Problems occurs with clashing keys & string parsing. We cannot have both clashing of keys & string parsing of constants. Even with different namespaces, that's the weakness of dealing with...

Hitting this aswell

A bunch of imports for commands need to be moved to `handle` to delay imports. It's done like that for some commands & imports but not all.

#3618 might help. I think we can wait & see if that improves performance.

@cgevans can you provide an example ?

Thanks for the info @keewis. If we can use a common interface for unit conversion with arrays, that would ease some pint parts. the user can then choose his library...

`q.max()` should be `q == q.max()` no ? I think there is something wrong wtih raising the correct error, since `condition` here is a quantity `np.where` got triggered again hence...

```python import pint import numpy as np ureg = pint.UnitRegistry() q = ureg.Quantity([1, 2], "kelvin") np.where(q == q.max()) (array([1]),)

I'll check to strip unit for condition aswell in the function implementing `np.where`. This should be enough to raise the appropriate error or using `True` as condition.

looks like we're missing an `__init__.py` file in pint._vendor