Sebastian Berg
Sebastian Berg
Hmmm, this removes the ability to use the env variable, so not sure about back-porting.
Not that I suspect anyone to jump at it. But for what it's worth, I think I tend to agree that the choice `order` seems unfortunate (but I expect it...
The biggest annoyance about moving the tests is maybe even that it makes backporting hard so yeah, would be nice to avoid. OTOH, it is also a bit odd to...
Not sure how much you need it, I am tempted to say: just use the private version. We will keep pretending that we can just delete it at some point...
@lpsinger if that works, that seems like a good idea to me. UFuncs currently do *not* have a `__dict__` so unless we want to change that, we need to add...
> So simply adding a setter to go with it would not make a lot of sense Maybe a setter can work, though? You could give it a logic of:...
Ah, you are right. I thought we would ask you to include the signature in your doc string, but that isn't great. There may be a simple solution, but I...
Just to come back: if assignment to `__doc__` is weird, I would say a `_set_doc` or so method should OK, with the understanding that we might replace it with a...
> If it's an in-place operation there's no new descriptor to finalize, we have to re-use the existing one. Why could you not use a temporary one? > I think...
> function is called inside the string to string cast So I suppose it is probably incorrect. But without structured dtypes, one would have to jump through very big hoop...