⬆ Bump setuptools from 72.1.0 to 75.8.2

[dependabot]

Bumps setuptools from 72.1.0 to 75.8.2.

Changelog

Sourced from setuptools's changelog.

v75.8.2

Bugfixes

• Fixed pkg_resources.require(...) to also consider standardised dist-info directories. (#4856)

v75.8.1

Bugfixes

• Fix wheel file naming to follow binary distribution specification -- by :user:di (#4766)
• Fixed crash generating error message printed when building wheels for the free-threaded build using the limited API. -- by :user:ngoldbaum (#4809)
• Fix documentation for recent CFLAGS distutils change. -- by :user:thesamesam (#4836)

v75.8.0

Features

• Implemented Dynamic field for core metadata (as introduced in PEP 643). The existing implementation is currently experimental and the exact approach may change in future releases. (#4698)

v75.7.0

Features

• pypa/distutils#310#4478)
• Synced with pypa/distutils@ff11eed0c including bugfix for duplicate CFLAGS and adaption to support Python 3.13 is_abs in the C compiler (#4669). (#4790)

v75.6.0

Features

• Preserve original PKG-INFO into METADATA when creating wheel

... (truncated)

Commits

• 9aa3771 Bump version: 75.8.1 → 75.8.2
• c0f39c0 Update WorkingSet.find to consider standardised .dist-info directory names (#...
• edca181 Add news fragment
• 22355fc Also consider '-' separator in tests
• 8280e2c Attempt to solve path normalisation issue in windows tests
• a3718c8 Slightly change test, so that we are sure about the correct distribution bein...
• 23b73aa Fix mypy errors
• 2c24223 Update WorkingSet.find to consider standardised dist-info names
• 79d6e46 Add regression test for issue 4853
• 56c055b Bump version: 75.8.0 → 75.8.1
• 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 <dependency name> 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)

Summary by Sourcery

Chores:

• Update setuptools dependency to the latest version.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the setuptools dependency from version 72.1.0 to 75.8.2. The change was implemented by updating the version in Pipfile.lock.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
The pull request updates the setuptools dependency from version 72.1.0 to 75.8.2.	Bumped setuptools version in Pipfile.lock.	Pipfile.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 generate docstrings to generate docstrings for this 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[codiumai-pr-agent-free]

CI Feedback 🧐

(Feedback updated until commit 6d9d454)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: build

Failed stage: run-build-scripts [❌]

Failed test name: ""

Failure summary: This log appears to be a system package listing from an Ubuntu environment and doesn't actually show a failure. The log shows installed packages and their versions on an Ubuntu system, which is likely just part of the environment setup phase of the action. Without seeing an actual error message or failure, I cannot determine why the action failed. The shown log section only contains successful package installations.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 1484: #7 47.59 ii iso-codes 4.4-1 all ISO language, territory, currency, script codes and their translations 1485: #7 47.59 ii java-common 0.72 all Base package for Java runtimes 1486: #7 47.59 ii jq 1.6-1ubuntu0.20.04.1 amd64 lightweight and flexible command-line JSON processor 1487: #7 47.59 ii libacl1:amd64 2.2.53-6 amd64 access control list - shared library 1488: #7 47.59 ii libapparmor1:amd64 2.13.3-7ubuntu5.3 amd64 changehat AppArmor library 1489: #7 47.59 ii libappstream4:amd64 0.12.10-2 amd64 Library to access AppStream services 1490: #7 47.59 ii libapt-pkg6.0:amd64 2.0.10 amd64 package management runtime library 1491: #7 47.59 ii libargon2-1:amd64 0~20171227-0.2 amd64 memory-hard hashing function - runtime library 1492: #7 47.59 ii libasan5:amd64 9.4.0-1ubuntu1~20.04.2 amd64 AddressSanitizer -- a fast memory error detector ... 1516: #7 47.59 ii libc-bin 2.31-0ubuntu9.16 amd64 GNU C Library: Binaries 1517: #7 47.59 ii libc-dev-bin 2.31-0ubuntu9.16 amd64 GNU C Library: Development binaries 1518: #7 47.59 ii libc6:amd64 2.31-0ubuntu9.16 amd64 GNU C Library: Shared libraries 1519: #7 47.59 ii libc6-dev:amd64 2.31-0ubuntu9.16 amd64 GNU C Library: Development Libraries and Header Files 1520: #7 47.59 ii libcap-ng0:amd64 0.7.9-2.1build1 amd64 An alternate POSIX capabilities library 1521: #7 47.59 ii libcap2:amd64 1:2.32-1ubuntu0.1 amd64 POSIX 1003.1e capabilities (library) 1522: #7 47.59 ii libcap2-bin 1:2.32-1ubuntu0.1 amd64 POSIX 1003.1e capabilities (utilities) 1523: #7 47.59 ii libcc1-0:amd64 10.5.0-1ubuntu1~20.04 amd64 GCC cc1 plugin for GDB 1524: #7 47.59 ii libcom-err2:amd64 1.45.5-2ubuntu1.1 amd64 common error description library ... 1539: #7 47.59 ii libdrm-amdgpu1:amd64 2.4.107-8ubuntu1~20.04.2 amd64 Userspace interface to amdgpu-specific kernel DRM services -- runtime 1540: #7 47.59 ii libdrm-common 2.4.107-8ubuntu1~20.04.2 all Userspace interface to kernel DRM services -- common files 1541: #7 47.59 ii libdrm-intel1:amd64 2.4.107-8ubuntu1~20.04.2 amd64 Userspace interface to intel-specific kernel DRM services -- runtime 1542: #7 47.59 ii libdrm-nouveau2:amd64 2.4.107-8ubuntu1~20.04.2 amd64 Userspace interface to nouveau-specific kernel DRM services -- runtime 1543: #7 47.59 ii libdrm-radeon1:amd64 2.4.107-8ubuntu1~20.04.2 amd64 Userspace interface to radeon-specific kernel DRM services -- runtime 1544: #7 47.59 ii libdrm2:amd64 2.4.107-8ubuntu1~20.04.2 amd64 Userspace interface to kernel DRM services -- runtime 1545: #7 47.59 ii libedit2:amd64 3.1-20191231-1 amd64 BSD editline and history libraries 1546: #7 47.59 ii libelf1:amd64 0.176-1.1ubuntu0.1 amd64 library to read and write ELF files 1547: #7 47.59 ii liberror-perl 0.17029-1 all Perl module for error/exception handling in an OO-ish way ... 1568: #7 47.59 ii libglib2.0-bin 2.64.6-1~ubuntu20.04.7 amd64 Programs for the GLib library 1569: #7 47.59 ii libglib2.0-data 2.64.6-1~ubuntu20.04.7 all Common files for GLib library 1570: #7 47.59 ii libglvnd0:amd64 1.3.2-1~ubuntu0.20.04.2 amd64 Vendor neutral GL dispatch library 1571: #7 47.59 ii libglx-mesa0:amd64 21.2.6-0ubuntu0.1~20.04.2 amd64 free implementation of the OpenGL API -- GLX vendor library 1572: #7 47.59 ii libglx0:amd64 1.3.2-1~ubuntu0.20.04.2 amd64 Vendor neutral GL dispatch library -- GLX support 1573: #7 47.59 ii libgmp10:amd64 2:6.2.0+dfsg-4ubuntu0.1 amd64 Multiprecision arithmetic library 1574: #7 47.59 ii libgnutls30:amd64 3.6.13-2ubuntu1.11 amd64 GNU TLS library - main runtime library 1575: #7 47.59 ii libgomp1:amd64 10.5.0-1ubuntu1~20.04 amd64 GCC OpenMP (GOMP) support library 1576: #7 47.59 ii libgpg-error0:amd64 1.37-1 amd64 GnuPG development runtime library

[dependabot]

Superseded by #25.