Yves Delley

Had this issue too, in my case the culprit was a dynamically compiled function (so no source code available). I don't quite see why there are no line numbers for...

+1 for units support. I agree, parametrised dtypes would be the preferred solution, but I don't want to wait that long (I would be willing to contribute to that end,...

#988 would certainly allow to me to implement unit functionality on xarray, probably by leveraging an existing units package. What I don't like with that approach is the fact that...

Or another way to put it: While typical metadata/attributes are only relevant if you eventually read them (which is where you will notice if they were lost on the way),...

So for now, I'm hunting for `np.asarray`.

Without following the discussion in detail, what is the status here? In particular, I would like to do pointwise selection on multiple 1D coordinates using multidimensional indexer arrays. I can...

Really? I get a `ValueError: Indexers must be 1 dimensional` (`xarray/core/dataset.py:1031 in isel_points(self, dim, **indexers)` when I try. That is xarray 0.8.2, in fact from my fork recently cloned (~2-3...

Actually, what I meant by 3) was the `quantity_kind_cast(quantity_kind(100*N*M))` (given suitable Kinds for `torque` and `energy`), which it already does now. By 4), I referred to `quantity_cast(1_s)`. Might I have...

I agree, they all "may truncate". What I care about is what they may *not* do. Given that my point 4 is moot, my whole essay here loses some of...

Ok, the "severity" may not be that different, but to me these are fundamentally different things on a semantic level. My understanding of modern C++ is that code should be...