Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency black to v25 #13107

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
black (changelog) ==24.10.0 -> ==25.1.0 age adoption passing confidence
black (changelog) ==24.8.0 -> ==25.1.0 age adoption passing confidence

Release Notes

psf/black (black)

v25.1.0

Compare Source

Highlights

This release introduces the new 2025 stable style (#​4558), stabilizing
the following changes:

  • Normalize casing of Unicode escape characters in strings to lowercase (#​2916)
  • Fix inconsistencies in whether certain strings are detected as docstrings (#​4095)
  • Consistently add trailing commas to typed function parameters (#​4164)
  • Remove redundant parentheses in if guards for case blocks (#​4214)
  • Add parentheses to if clauses in case blocks when the line is too long (#​4269)
  • Whitespace before # fmt: skip comments is no longer normalized (#​4146)
  • Fix line length computation for certain expressions that involve the power operator (#​4154)
  • Check if there is a newline before the terminating quotes of a docstring (#​4185)
  • Fix type annotation spacing between * and more complex type variable tuple (#​4440)

The following changes were not in any previous release:

  • Remove parentheses around sole list items (#​4312)
  • Generic function definitions are now formatted more elegantly: parameters are
    split over multiple lines first instead of type parameter definitions (#​4553)
Stable style
  • Fix formatting cells in IPython notebooks with magic methods and starting or trailing
    empty lines (#​4484)
  • Fix crash when formatting with statements containing tuple generators/unpacking
    (#​4538)
Preview style
  • Fix/remove string merging changing f-string quotes on f-strings with internal quotes
    (#​4498)
  • Collapse multiple empty lines after an import into one (#​4489)
  • Prevent string_processing and wrap_long_dict_values_in_parens from removing
    parentheses around long dictionary values (#​4377)
  • Move wrap_long_dict_values_in_parens from the unstable to preview style (#​4561)
Packaging
  • Store license identifier inside the License-Expression metadata field, see
    PEP 639. (#​4479)
Performance
  • Speed up the is_fstring_start function in Black's tokenizer (#​4541)
Integrations
  • If using stdin with --stdin-filename set to a force excluded path, stdin won't be
    formatted. (#​4539)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners January 29, 2025 06:59
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Jan 29, 2025
@product-auto-label product-auto-label bot added samples Issues that are directly related to samples. api: compute Issues related to the Compute Engine API. labels Jan 29, 2025
Copy link
Contributor

@code-review-assist code-review-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi team,

I'm currently reviewing this pull request and will provide my feedback shortly. In the meantime, here's a summary for you and other reviewers to quickly get up to speed:

This pull request, submitted by Renovate bot, updates the black dependency across the project. The intent is to upgrade the code formatter to version 25.1.0 from versions 24.8.0 and 24.10.0, depending on the python version.

Here's a breakdown of the changes:

  • Dependency Update: The black dependency in compute/client_library/requirements.txt is updated to version 25.1.0 for both Python versions 3.9 and above, and below 3.9.

The changes are limited to updating the version number in the requirements file. No code changes are directly introduced by this PR, only an indirect change via the updated formatter.

Release notes for black v25.1.0 highlight numerous bug fixes and improvements to the formatter's stability and performance, including a new stable style for 2025 and various fixes related to string processing, f-strings, and type annotations. You can find the full details in the PR description.

I'll provide a more detailed review shortly.

Meanwhile, a little poem to brighten your day:

Code flows like a river,
Updates bring a fresh new spring,
Bugs flee in the night.

Best,
Gemini

@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jan 29, 2025
Copy link
Contributor

@code-review-assist code-review-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pull request updates the black dependency to v25.1.0. It's good practice to keep dependencies up-to-date, especially for development tools like linters and formatters. Upgrading to the latest version of black ensures that you're using the most recent features and bug fixes, and helps maintain consistency in code style across the project. Since this is an automated PR from Renovate, I've checked that the changes are limited to updating the version numbers in the requirements.txt file, and that the new version numbers are correct.

I've also reviewed the changelog for black v25.1.0 and it looks like there are some significant changes introduced in the 2025 stable style, including changes to trailing commas, parentheses handling, and docstring formatting. It's important to be aware of these changes as they might affect the formatting of your codebase. After upgrading, it's recommended to run black on your codebase to apply the new formatting rules and ensure consistency. You might also want to consider adding a step to your CI/CD pipeline to automatically format code with black on each commit or pull request. This helps prevent style inconsistencies from creeping into the codebase over time. The AUTHORING_GUIDE.md file recommends using black and provides instructions for running it locally and in Docker, which is helpful.

@glasnt glasnt added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 6, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: compute Issues related to the Compute Engine API. owlbot:run Add this label to trigger the Owlbot post processor. samples Issues that are directly related to samples.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants