Update numpy requirement from ==1.26.* to ==2.1.*

[dependabot[bot]]

Updates the requirements on numpy to permit the latest version.

Release notes

Sourced from numpy's releases.

2.1.3 (Nov 2, 2024)

NumPy 2.1.3 Release Notes

NumPy 2.1.3 is a maintenance release that fixes bugs and regressions discovered after the 2.1.2 release. This release also adds support for free threaded Python 3.13 on Windows.

The Python versions supported by this release are 3.10-3.13.

Improvements

• Fixed a number of issues around promotion for string ufuncs with StringDType arguments. Mixing StringDType and the fixed-width DTypes using the string ufuncs should now generate much more uniform results.

  (gh-27636)

Changes

• numpy.fix now won't perform casting to a floating data-type for integer and boolean data-type input arrays.

  (gh-26766)

Contributors

A total of 15 people contributed to this release. People with a "+" by their names contributed a patch for the first time.

• Abhishek Kumar +
• Austin +
• Benjamin A. Beasley +
• Charles Harris
• Christian Lorentzen
• Marcel Telka +
• Matti Picus
• Michael Davidsaver +
• Nathan Goldbaum
• Peter Hawkins
• Raghuveer Devulapalli
• Ralf Gommers
• Sebastian Berg
• dependabot[bot]
• kp2pml30 +

Pull requests merged

A total of 21 pull requests were merged for this release.

... (truncated)

Changelog

Sourced from numpy's changelog.

This is a walkthrough of the NumPy 2.1.0 release on Linux, modified for building with GitHub Actions and cibuildwheels and uploading to the anaconda.org staging repository for NumPy <https://anaconda.org/multibuild-wheels-staging/numpy>_. The commands can be copied into the command line, but be sure to replace 2.1.0 by the correct version. This should be read together with the :ref:general release guide <prepare_release>.

Facility preparation

Before beginning to make a release, use the requirements/*_requirements.txt files to ensure that you have the needed software. Most software can be installed with pip, but some will require apt-get, dnf, or whatever your system uses for software. You will also need a GitHub personal access token (PAT) to push the documentation. There are a few ways to streamline things:

• Git can be set up to use a keyring to store your GitHub personal access token. Search online for the details.
• You can use the keyring app to store the PyPI password for twine. See the online twine documentation for details.

Prior to release

Add/drop Python versions

When adding or dropping Python versions, three files need to be edited:

• .github/workflows/wheels.yml # for github cibuildwheel
• .travis.yml # for cibuildwheel aarch64 builds
• setup.py # for classifier and minimum version check.

Make these changes in an ordinary PR against main and backport if necessary. Using the BLD: prefix (build label) for the commit summary will cause the wheel builds to be run so that the changes will be tested, We currently release wheels for new Python versions after the first Python rc once manylinux and cibuildwheel support it. For Python 3.11 we were able to release within a week of the rc1 announcement.

Backport pull requests

Changes that have been marked for this release must be backported to the maintenance/2.1.x branch.

Update 2.1.0 milestones

... (truncated)

Commits

• 98464cc Merge pull request #27690 from charris/prepare-2.1.3
• cbda85b REL: Prepare for the NumPy 2.1.3 release [wheel build]
• daa8699 Merge pull request #27672 from charris/backport-27666
• 614ca19 Merge pull request #27673 from charris/backport-27636
• e6b02d7 DOC: add release note
• 54fd729 BUG: substantially simplify and fix issue with justification promoter
• a90fe7c BUG: fix more issues with string ufunc promotion
• a121864 BUG: fixes for StringDType/unicode promoters
• f055fb9 BUG: Fix a reference count leak in npy_find_descr_for_scalar.
• 5895c02 Merge pull request #27669 from charris/backport-27663
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.