Justus Magin

> I may look into what docutils does for cases like this. `docutils` appears to do something similar: warn / error (not sure how to interpret the output) if there's...

> I have a feeling that this is again a reason for [implementing separate `pint.QuantityArray` and `pint.QuantityScalar` types](https://github.com/hgrecco/pint/issues/1128#issuecomment-979432968) If we can make sure the `numpy` facet always returns that suggested...

As I said, I'm not sure what to do about this. However, I really would like to avoid doing this on first use of the `.pint` accessor, because that will...

the relevant issues are hgrecco/pint#950 and hgrecco/pint#1342. You won't see this in `pint-xarray`'s test suite because technically this is a property of `xarray` (`pint-xarray` is just a glue / convenience...

`pint` does not implement the array API, at all: all of the work that made it a "duck array" happened before that standard even existed, so `xarray` support is via...

very true, Array API support in `pint` would remove the need for `force_ndarray_like=True`. This is a huge undertaking, though, so not sure when we will get to that (my personal...

Not sure if this is helpful, but from the little I know of `beam` it sounds like it might be possible to use [branching](https://tour.beam.apache.org/tour/python/core-transforms/branching) for this. In other words, you...

if I understand correctly, we'd need a post-release workflow that queries zenodo to find the doi of the most recent release and creates a PR from that (using `doi2cff`). Does...

I don't think we can automate adding new contributors to the authors: Where would you get the information to put into `CITATION.cff` from? AFAICT, the only thing we would be...

If we can use the "cite-all-versions" doi that makes it much simpler. I wonder if creating a `pre-commit` hook that checks the changelog for version sections with dates and synchronizes...