pyiron / structuretoolkit

build, analyse and visualise atomistic structures for materials science
BSD 3-Clause "New" or "Revised" License
7 stars 0 forks source link

Bump numpy from 1.26.4 to 2.0.1 #226

Open dependabot[bot] opened 3 months ago

dependabot[bot] commented 3 months ago

Bumps numpy from 1.26.4 to 2.0.1.

Release notes

Sourced from numpy's releases.

v2.0.1

NumPy 2.0.1 Release Notes

NumPy 2.0.1 is a maintenance release that fixes bugs and regressions discovered after the 2.0.0 release. NumPy 2.0.1 is the last planned release in the 2.0.x series, 2.1.0rc1 should be out shortly.

The Python versions supported by this release are 3.9-3.12.

NOTE: Do not use the GitHub generated "Source code" files listed in the "Assets", they are garbage.

Improvements

np.quantile with method closest_observation chooses nearest even order statistic

This changes the definition of nearest for border cases from the nearest odd order statistic to nearest even order statistic. The numpy implementation now matches other reference implementations.

(gh-26656)

Contributors

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

  • @​vahidmech +
  • Alex Herbert +
  • Charles Harris
  • Giovanni Del Monte +
  • Leo Singer
  • Lysandros Nikolaou
  • Matti Picus
  • Nathan Goldbaum
  • Patrick J. Roddy +
  • Raghuveer Devulapalli
  • Ralf Gommers
  • Rostan Tabet +
  • Sebastian Berg
  • Tyler Reddy
  • Yannik Wicke +

Pull requests merged

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

  • #26711: MAINT: prepare 2.0.x for further development
  • #26792: TYP: fix incorrect import in ma/extras.pyi stub
  • #26793: DOC: Mention '1.25' legacy printing mode in set_printoptions
  • #26794: DOC: Remove mention of NaN and NAN aliases from constants

... (truncated)

Commits
  • 4c9f431 Merge pull request #27000 from charris/prepare-2.0.1
  • 0e70e00 REL: Prepare for the NumPy 2.0.1 release [wheel build]
  • 4d10ffc Merge pull request #26995 from charris/backport-26985
  • 764b667 BUG: Add object cast to avoid warning with limited API
  • 9be6ad6 Merge pull request #26971 from charris/backport-26935
  • 6d950e9 BUG: fix f2py tests to work with v2 API
  • 89630c0 Merge pull request #26962 from charris/backport-26919
  • 88fa840 TST: Apply test suggestion by Nathan for rlstrip fixes
  • a9da01e BUG,MAINT: Fix utf-8 character stripping memory access
  • 6afbbf8 Merge pull request #26963 from charris/backport-26930
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

coderabbitai[bot] commented 3 months ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
dependabot[bot] commented 3 months ago

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.

jan-janssen commented 3 months ago
======================================================================
ERROR: test_get_frame (test_visualize.TestAtoms.test_get_frame)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/structuretoolkit/structuretoolkit/tests/test_visualize.py", line 34, in test_get_frame
    self.assertEqual(dx.ptp(), 1, msg="Frames not drawn along the nearest edges")
                     ^^^^^^
AttributeError: `ptp` was removed from the ndarray class in NumPy 2.0. Use np.ptp(arr, ...) instead.

----------------------------------------------------------------------
jan-janssen commented 3 months ago
  The following packages are incompatible
  ├─ numpy 2.0.1**  is installable with the potential options
  │  ├─ numpy 2.0.1, which can be installed;
  │  ├─ numpy [1.26.4|2.0.1] would require
  │  │  └─ python_abi 3.10.* *_cp310, which can be installed;
  │  ├─ numpy [1.26.4|2.0.1] would require
  │  │  └─ python_abi 3.11.* *_cp311, which can be installed;
  │  └─ numpy [1.26.4|2.0.1] would require
  │     └─ python_abi 3.9.* *_cp39, which can be installed;
  ├─ pymatgen 2024.7.18**  is installable with the potential options
  │  ├─ pymatgen 2024.7.18 would require
  │  │  └─ numpy >=1.26.4,<2.0a0  with the potential options
  │  │     ├─ numpy 1.26.4 conflicts with any installable versions previously reported;
  │  │     ├─ numpy [1.26.4|2.0.1], which can be installed (as previously explained);
  │  │     ├─ numpy [1.26.4|2.0.1], which can be installed (as previously explained);
  │  │     ├─ numpy [1.26.4|2.0.1], which can be installed (as previously explained);
  │  │     └─ numpy 1.26.4 would require
  │  │        └─ python_abi 3.9 *_pypy39_pp73, which can be installed;
  │  ├─ pymatgen 2024.7.18 would require
  │  │  └─ python_abi 3.10.* *_cp310, which can be installed;
  │  ├─ pymatgen 2024.7.18 would require
  │  │  └─ python_abi 3.11.* *_cp311, which can be installed;
  │  └─ pymatgen 2024.7.18 would require
  │     └─ python_abi 3.9.* *_cp39, which can be installed;
  ├─ python 3.12**  is not installable because there are no viable options
  │  ├─ python [3.12.0|3.12.1|3.12.2|3.12.3|3.12.4] would require
  │  │  └─ python_abi 3.12.* *_cp312, which conflicts with any installable versions previously reported;
  │  ├─ python 3.12.0rc3 would require
  │  │  └─ _python_rc, which does not exist (perhaps a missing channel);
  │  └─ python [3.12.0|3.12.1|3.12.2|3.12.3|3.12.4] conflicts with any installable versions previously reported;
  └─ scipy 1.14.0**  is installable with the potential options
     ├─ scipy 1.14.0 would require
     │  └─ python_abi 3.10.* *_cp310, which can be installed;
     ├─ scipy 1.14.0 would require
     │  └─ python_abi 3.11.* *_cp311, which can be installed;
     └─ scipy 1.14.0 would require
        └─ python_abi 3.12.* *_cp312, which conflicts with any installable versions previously reported.
dependabot[bot] commented 2 months ago

A newer version of numpy exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

jan-janssen commented 1 month ago
  └─ pyxtal 1.0.3**  is installable and it requires
     ├─ numpy >=1.26,<2  with the potential options
     │  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4|2.1.1], which can be installed (as previously explained);
     │  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4|2.1.1], which can be installed (as previously explained);
     │  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] conflicts with any installable versions previously reported;
     │  ├─ numpy 1.26.0 would require
     │  │  └─ pypy3.9 >=7.3.12 , which can be installed;
     │  ├─ numpy [1.26.0|1.26.2|1.26.3|1.26.4] would require
     │  │  └─ python_abi 3.9.* *_cp39, which can be installed;
     │  ├─ numpy [1.26.2|1.26.3] would require
     │  │  └─ pypy3.9 >=7.3.13 , which can be installed;
     │  ├─ numpy 1.26.4 would require
     │  │  └─ pypy3.9 >=7.3.15 , which can be installed;
     │  └─ numpy [2.0.0rc1|2.0.0rc2] would require
     │     └─ _numpy_rc, which does not exist (perhaps a missing channel);