Bump the build-python group in /build/pip with 2 updates

[dependabot]

Bumps the build-python group in /build/pip with 2 updates: charset-normalizer and keyring.

Updates charset-normalizer from 3.4.0 to 3.4.1

Release notes

Sourced from charset-normalizer's releases.

Version 3.4.1

🚀 We're still raising awareness around HTTP/2, and HTTP/3!

Did you know that Internet Explorer 11 shipped with an optional HTTP/2 support back in 2013? also libcurl did ship it in 2014[...] Using Requests today is the rough equivalent of using EOL Windows 8! We promptly invite Python developers to look at the first drop-in replacement for Requests, namely Niquests. Ship with native WebSocket, SSE, Happy Eyeballs, DNS over HTTPS, and so on[...] All of this while remaining compatible with all Requests prior plug-ins / add-ons.

It leverages charset-normalizer in a better way! Check it out, you will gain up to being 3X faster and get a real/respectable support with it.

3.4.1 (2024-12-24)

Changed

• Project metadata are now stored using pyproject.toml instead of setup.cfg using setuptools as the build backend.
• Enforce annotation delayed loading for a simpler and consistent types in the project.
• Optional mypyc compilation upgraded to version 1.14 for Python >= 3.8

Added

• pre-commit configuration.
• noxfile.

Removed

• build-requirements.txt as per using pyproject.toml native build configuration.
• bin/integration.py and bin/serve.py in favor of downstream integration test (see noxfile).
• setup.cfg in favor of pyproject.toml metadata configuration.
• Unused utils.range_scan function.

Fixed

• Converting content to Unicode bytes may insert utf_8 instead of preferred utf-8. (#572)
• Deprecation warning "'count' is passed as positional argument" when converting to Unicode bytes on Python 3.13+

Changelog

Sourced from charset-normalizer's changelog.

3.4.1 (2024-12-24)

Changed

• Project metadata are now stored using pyproject.toml instead of setup.cfg using setuptools as the build backend.
• Enforce annotation delayed loading for a simpler and consistent types in the project.
• Optional mypyc compilation upgraded to version 1.14 for Python >= 3.8

Added

• pre-commit configuration.
• noxfile.

Removed

• build-requirements.txt as per using pyproject.toml native build configuration.
• bin/integration.py and bin/serve.py in favor of downstream integration test (see noxfile).
• setup.cfg in favor of pyproject.toml metadata configuration.
• Unused utils.range_scan function.

Fixed

• Converting content to Unicode bytes may insert utf_8 instead of preferred utf-8. (#572)
• Deprecation warning "'count' is passed as positional argument" when converting to Unicode bytes on Python 3.13+

Commits

• ffdf7f5 🔧 fix long description content-type inferred as rst instead of md
• c7197b7 📝 fix changelog entries (#582)
• c390e1f Merge pull request #581 from jawah/refresh-part-2
• f9d6b8c 🔒 add CODEOWNERS
• 7ce1ef1 🔧 use ubuntu-22.04 for cibuildwheel in continuous deployment workflow
• deed205 🔧 update LICENSE copyright
• f11f571 🔧 include noxfile in sdist
• 1ec7c06 🔧 update changelog
• 14b4649 🐛 output(...) replace declarative mark using non iana compliant encoding ...
• 1b06bc0 Merge branch 'refresh-part-2' of github.com:jawah/charset_normalizer into ref...
• Additional commits viewable in compare view

Updates keyring from 25.5.0 to 25.6.0

Changelog

Sourced from keyring's changelog.

v25.6.0

Features

• Avoid logging a warning when config does not specify a backend. (#682)

Commits

• a9a7624 Finalize
• 21680c6 Merge pull request #702 from jfly/issue-682
• bf80b69 Add news fragment.
• 1526c17 Don't log a warning when the backend config section is missing
• edaa964 Merge https://github.com/jaraco/skeleton
• 5c34e69 Use extend for proper workaround.
• 1119d7b Merge https://github.com/jaraco/skeleton
• 750a189 Require Python 3.9 or later now that Python 3.8 is EOL.
• e61a9df Include pyproject.toml in ruff.toml.
• db4dfc4jaraco/skeleton#151
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[gaugebot]

@dependabot[bot] Thank you for contributing to gauge. Your pull request has been labeled as a release candidate 🎉🎉.

Merging this PR will trigger a release.

Please bump up the version as part of this PR.

Instructions to bump the version can found at CONTRIBUTING.md

If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done.