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
Currently 7 functions from the numpy.testing namespace are re-exported in yt.testing. The code currently looks like this:
# we import this in a weird way from numpy.testing to avoid triggering# flake8 errors from the unused imports. These test functions are imported# elsewhere in yt from here so we want them to be imported here.fromnumpy.testingimportassert_array_equal, assert_almost_equal# NOQA isort:skipfromnumpy.testingimportassert_equal, assert_array_less# NOQA isort:skipfromnumpy.testingimportassert_string_equal# NOQA isort:skipfromnumpy.testingimportassert_array_almost_equal_nulp# isort:skipfromnumpy.testingimportassert_allclose, assert_raises# NOQA isort:skipfromnumpy.testingimportassert_approx_equal# NOQA isort:skipfromnumpy.testingimportassert_array_almost_equal# NOQA isort:skip
Last time this was updated (~3yrs ago, when isort was first enabled), we didn't attempt to get rid of that, but there is no actual gain to doing that excepts for backward compatibility, but we can actually go through a deprecation cycle if we wrap these functions instead of directly re-exporting them.
This is probably a reasonable goal to set for the next feature release so I'll triage this into the 4.2 milestone for now
The text was updated successfully, but these errors were encountered:
Report
Currently 7 functions from the
numpy.testing
namespace are re-exported inyt.testing
. The code currently looks like this:Last time this was updated (~3yrs ago, when isort was first enabled), we didn't attempt to get rid of that, but there is no actual gain to doing that excepts for backward compatibility, but we can actually go through a deprecation cycle if we wrap these functions instead of directly re-exporting them.
This is probably a reasonable goal to set for the next feature release so I'll triage this into the 4.2 milestone for now
The text was updated successfully, but these errors were encountered: