I tried using meshio against a nightly build of numpy==2 and noticed that it does not work because of missing np.string_. I was able to do some things that I depend on by replacing each occurence of np.string_ by np.bytes_ within meshio codebase, as suggested by the migration guide. I did not run the full meshio test suite so there might be other things to consider.
Describe the bug Soon there will be a backwards-incompatible release of numpy. As a consequence,
np.string_will be removed, see the migration guide:https://numpy.org/devdocs/numpy_2_0_migration_guide.html
I tried using
meshioagainst a nightly build ofnumpy==2and noticed that it does not work because of missingnp.string_. I was able to do some things that I depend on by replacing each occurence ofnp.string_bynp.bytes_withinmeshiocodebase, as suggested by the migration guide. I did not run the fullmeshiotest suite so there might be other things to consider.To Reproduce
numpy==2from https://anaconda.org/scientific-python-nightly-wheels/numpyimport meshiothenmeshio.readand/ormeshio.writeandmeshio.Mesh