Ben Greiner

> * (I don't see any deprecation notice here though) It's the "Note" box right at the top. > This NEP is superseded by the scientific python ecosystem coordination guideline...

I am not sure if updating an accepted APE is the correct way. I originally wanted to update to whatsnew of Astropy 6.1 directly (https://github.com/astropy/astropy/pull/16376) and still think this would...

`environment.yml` is not relevant here. The only relevant lines are in pyproject.toml: https://github.com/pandas-dev/pandas/blob/v2.2.2/pyproject.toml#L11 https://github.com/pandas-dev/pandas/blob/d9cdd2ee5a58015ef6f4d15c7226110c9aab8140/pyproject.toml#L30-L32 and from the changelog: https://pandas.pydata.org/docs/whatsnew/v2.2.2.html#pandas-2-2-2-is-now-compatible-with-numpy-2-0 > Pandas 2.2.2 is the first version of pandas that is...

Besides, this is not a failure related to pandas, but rather to a change in numpy type promotion: https://numpy.org/devdocs/numpy_2_0_migration_guide.html#changes-to-numpy-data-type-promotion https://github.com/dask/fastparquet/blob/ec267332d6585dfdec513404c06c603c1726122a/fastparquet/converted_types.py#L159-L162

If I kill the `node` processes in between the pytest calls, the test suite passes all times: ```shell for i in 1 2 3 4 5 6; do testenv/bin/python -m...

This is only relevant for deprecated setup.py builds. Proper PEP517 usage does not exhibit the failure.

Fixed in https://github.com/pycroscopy/pyUSID/pull/87

np.int has been removed from numpy 1.24. This should be plain 'int' now. ``` [ 25s] ============================= test session starts ============================== [ 25s] platform linux -- Python 3.8.16, pytest-7.2.0, pluggy-1.0.0...

duplicate of #32

I am not sure why the pandas bug is still not picked up yet. Numpy as been released for a few weeks already and the regular pandas CI should have...