Use numpy testing utilities instead of custom close_to*

[ricardoV94]

pymc/tests/checks.py

Lines 18 to 27 in e1d36ca

	def close_to(x, v, bound, name="value"):
	assert np.all(np.logical_or(np.abs(x - v) < bound, x == v)), (
	name + " out of bounds: " + repr(x) + ", " + repr(v) + ", " + repr(bound)
	)
	def close_to_logical(x, v, bound, name="value"):
	assert np.all(np.logical_or(np.abs(np.bitwise_xor(x, v)) < bound, x == v)), (
	name + " out of bounds: " + repr(x) + ", " + repr(v) + ", " + repr(bound)
	)

Numpy testing routines already take care of asserting / printing failures nicely. We should just use them: https://numpy.org/doc/stable/reference/routines.testing.html

[error9098x]

Hi, I have changed the testing utility to numpy, now how do I test my changes locally ?

[ricardoV94]

This may help? https://www.pymc.io/projects/docs/en/stable/contributing/running_the_test_suite.html