You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Quantity API that standardises methods and attributes would make it easier to write code that supports multiple unit libraries. At present this is difficult and has lead to multiple integration packages being written to support units, eg pint-xarray and xarray-quantity.
Is unyt interested in collobrating on developing and adopting a Quantity API?
The text was updated successfully, but these errors were encountered:
Yes. As the common maintainer to unyt and astropy I am well aware of this initiative. My hope is that the "Quantity 2.0" library might completely remove the need for unyt for 99% of it's users (although it might lack support for custom unit systems, which is crucial in yt), so I think my time is better spent helping develop the quantity API and the Quantity library rather than supporting it in unyt: I'm not sure the effort needed to support the quantity API for the remaining 1% is worth it, but it might. At the moment unyt's development and maintenance is 100% volunteer time (in short supply) so no promise can be made, but I would happily review/merge pull requests if anyone is interested in contributing in this area.
There has been some interest in a Quantity or Units API, similar to the array API standard.
hgrecco/pint#2101
astropy/astropy#8210
astropy/astropy-APEs#91
https://pydims.github.io/pydims/developer/index.html
A Quantity API that standardises methods and attributes would make it easier to write code that supports multiple unit libraries. At present this is difficult and has lead to multiple integration packages being written to support units, eg pint-xarray and xarray-quantity.
Is unyt interested in collobrating on developing and adopting a Quantity API?
The text was updated successfully, but these errors were encountered: