Is astropy.units essential in more fields than just astronomy?

Greetings. Thanks for a great set of packages!

It’s difficult to think of a broader use case than the one for which astropy.units was designed—for computation using physical quantities!

I am very new to this project and I don’t want to step on any toes. Still, I can’t help but wonder if astropy.units should be “advertised” as bigger than only astronomy. A subset of possible mechanisms for this includes moving the module outside the astropy namespace, and/or listing a variety of other domains for which it’s a great fit in the documentation, and/or writing an official blog post (though I don’t believe Astropy has a blog?).

Generally, What do you all think?

[namurphy]

Come to think of it, I also use astropy.units.imperial really frequently while cooking, instead of having to remember the nonsensical unit conversions we have to deal with in the U.S.

I’ll probably also use astropy.units if I ever write a vegan cookbook using horrible but surprisingly convenient units like barn-megaparsecs:

>>> from astropy import units
>>> (1*units.barn*units.Mpc).to(units.imperial.tsp)
<Quantity 0.6260350298930571 tsp>

[bsipocz]

One idea I had at some point would be to create a package that contains no code but just imports from astropy.units - this would just help with the branding issue, but still use astropy behind the scenes 😉

or just raise awareness that astropy is overall a useful package 😉