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

Update dependency pylint to v3.0.3 #69

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

devex-sa
Copy link
Contributor

@devex-sa devex-sa commented Jan 18, 2024

This PR contains the following updates:

Package Type Update Change
pylint (changelog) dependencies patch 3.0.2 -> 3.0.3

Release Notes

pylint-dev/pylint

v3.0.3

Compare Source

What's new in Pylint 3.0.3?

Release date: 2023-12-11

False Positives Fixed

  • Fixed false positive for unnecessary-lambda when the call has keyword arguments but not the lambda.

    Closes #​9148

  • Fixed incorrect suggestion for shallow copy in unnecessary-comprehension

    Example of the suggestion:
    #pylint: disable=missing-module-docstring
    a = [1, 2, 3]
    b = [x for x in a]
    b[0] = 0
    print(a) # [1, 2, 3]

    After changing b = [x for x in a] to b = a based on the suggestion, the script now prints [0, 2, 3]. The correct suggestion should be use list(a) to preserve the original behavior.

    Closes #​9172

  • Fix false positives for undefined-variable and unused-argument for
    classes and functions using Python 3.12 generic type syntax.

    Closes #​9193

  • Fixed pointless-string-statement false positive for docstrings
    on Python 3.12 type aliases.

    Closes #​9268

  • Fix false positive for invalid-exception-operation when concatenating tuples
    of exception types.

    Closes #​9288

Other Bug Fixes

  • Fix a bug where pylint was unable to walk recursively through a directory if the
    directory has an __init__.py file.

    Closes #​9210


Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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


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

This PR has been generated by Renovate Bot.

@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch 2 times, most recently from 8fac638 to 613b192 Compare January 19, 2024 08:38
@devex-sa devex-sa changed the title Update dependency pylint to v3.0.3 chore(deps): update dependency pylint to v3.0.3 Jan 19, 2024
@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch 6 times, most recently from 779697c to 4f03cbe Compare January 23, 2024 14:39
@devex-sa devex-sa changed the title chore(deps): update dependency pylint to v3.0.3 Update dependency pylint to v3.0.3 Jan 23, 2024
@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch 2 times, most recently from 2302326 to b1678ce Compare January 24, 2024 14:39
@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch 5 times, most recently from aae8440 to cd41f61 Compare February 8, 2024 08:35
@devex-sa devex-sa requested a review from a team as a code owner February 8, 2024 08:35
@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch from cd41f61 to c511a1d Compare February 21, 2024 10:35
@devex-sa devex-sa requested a review from a team as a code owner February 21, 2024 10:35
@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch from c511a1d to 157bf01 Compare February 22, 2024 10:35
@devex-sa devex-sa force-pushed the feature/renovate/pylint-3.x-lockfile branch from 157bf01 to cb89c74 Compare February 22, 2024 15:02
@samidbb samidbb added the norelease We don't want to release this label Feb 22, 2024
@samidbb samidbb merged commit b615e88 into main Feb 22, 2024
7 of 8 checks passed
@samidbb samidbb deleted the feature/renovate/pylint-3.x-lockfile branch February 22, 2024 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
norelease We don't want to release this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants