Mateusz Sokół d04d964ace Implement NumPy 2.0 migration rule (#7702) ... ## Summary <!-- What's the purpose of the change? What does it do, and why? --> Hi! Currently NumPy Python API is undergoing a cleanup process that will be delivered in NumPy 2.0 (release is planned for the end of the year). Most changes are rather simple (renaming, removing or moving a member of the main namespace to a new place), and they could be flagged/fixed by an additional ruff rule for numpy (e.g. changing occurrences of `np.float_` to `np.float64`). Would you accept such rule? I named it `NPY201` in the existing group, so people will receive a heads-up for changes arriving in 2.0 before actually migrating to it. ~~This is still a draft PR.~~ I'm not an expert in rust so if any part of code can be done better please share! NumPy 2.0 migration guide: https://numpy.org/devdocs/numpy_2_0_migration_guide.html NEP 52: https://numpy.org/neps/nep-0052-python-api-cleanup.html NumPy cleanup tracking issue: https://github.com/numpy/numpy/issues/23999 ## Test Plan A unit test is provided that checks all rule's fix cases.		2023-11-03 03:47:01 +00:00
..
NPY001.py	Rename ruff crate to ruff_linter (#7529)	2023-09-20 08:38:27 +02:00
NPY002.py	Rename ruff crate to ruff_linter (#7529)	2023-09-20 08:38:27 +02:00
NPY003.py	Rename ruff crate to ruff_linter (#7529)	2023-09-20 08:38:27 +02:00
NPY201.py	Implement NumPy 2.0 migration rule (#7702)	2023-11-03 03:47:01 +00:00