expose some of the internal test functions in pint.testing

[keewis]

just as a side note, it might be good to change the autodoc-based documentation to something else, like autosummary

• Closes Where is pint.testing API reference? #1285, closes np.testing.assert_equal does not work with quantity lists #1272
• Executed pre-commit run --all-files with no errors
• The change is fully covered by automated unit tests
• Documented in docs/ as appropriate
• Added an entry to the CHANGES file

[keewis]

okay, I cheated my way around a bug in is_compatible_with when it is used with contexts (it ignores already active contexts), but I don't know enough about contexts to fix that in a general way. Do you have any ideas, @hgrecco, @jules-ch?

[jules-ch]

Hi @keewis do you have a minimal example for your issue with is_compatible_with ?

[keewis]

it would be something like this (taken from test_contexts.py::TestDefinedContexts::test_spectroscopy)

In [6]: ureg = pint.UnitRegistry()
   ...: 
   ...: a = 532.0 * ureg.nm
   ...: b = 563.5 * ureg.terahertz
   ...: 
   ...: with ureg.context("sp"):
   ...:     print(a.to(ureg.terahertz))
   ...:     assert a.is_compatible_with(b), "not compatible"
   ...: 
563.5196578947367 terahertz
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
<ipython-input-6-8eaa63cfa960> in <module>
      6 with ureg.context("sp"):
      7     print(a.to(ureg.terahertz))
----> 8     assert a.is_compatible_with(b), "not compatible"
      9 

AssertionError: not compatible

ureg.is_compatible_with behaves the same way (so at least it's consistent)

[jules-ch]

Can you file an issue regarding this, I'll quickly fix that.

[keewis]

sure

[jules-ch]

Gonna merge this after CI completes