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

Merge maintenance 2.15.9 in main #7956

Conversation

Pierre-Sassoulas
Copy link
Member

No description provided.

github-actions bot and others added 10 commits December 12, 2022 14:32
…lint-dev#7922) (pylint-dev#7923)

(cherry picked from commit bc9f15f)

Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
… (pylint-dev#7930)

* Replace multiprocessing.pool with concurrent.futures.ProcessPoolExecutor to avoid deadlocks.

In a multiprocessing.pool, if a process terminates in a non-clean fashion
(for example, due to OOM or a segmentation fault), the pool will silently
replace said process, but the work that the process was supposed to do
will never be done, causing pylint to hang indefinitely.
The concurrent.futures.ProcessPoolExecutor will raise a
BrokenProcessPool exception in that case, avoiding the hang.

Co-authored-by: Daniël van Noord <13665637+DanielNoord@users.noreply.github.com>
(cherry picked from commit 5eca8ec)

Co-authored-by: Daniel <daniel.werner@scalableminds.com>
…ylint-dev#7918)

Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com>
…ylint-dev#7941)

Ensure that the import path is fixed up before calling
._astroid_module_checker() so that the pylint_django plugin can
successfully import the Django settings module when its checkers are
initialized.

Closes pylint-dev#7938

(cherry picked from commit 491eef5)

Co-authored-by: Daniel Harding <dharding@living180.net>
…rror code (pylint-dev#7931) (pylint-dev#7943)

Returning 2 here is confusing as it doesn't match the documentation: https://pylint.pycqa.org/en/latest/user_guide/usage/run.html#exit-codes

* pylint: use exit code 32 when invalid arguments are passed

* pylint: add failing test when ambiguous abbreviated parameters are set in a config file

This is confusing behaviour. The output is:

```
usage: pylint [options]
pylint: error: ambiguous option: --no could match --notes, --notes-rgx, --no-docstring-rgx
```

The exit code is 2 which doesn't match the documentation: https://pylint.pycqa.org/en/latest/user_guide/usage/run.html#exit-codes

* pylint: use exit code 32 when ambiguous abbreviated parameters are set in a config file

Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com>
(cherry picked from commit 62232b3)

Co-authored-by: David Lawson <dmrlawson@gmail.com>
…t-dev#7948)

In order to help when the target interpreter is not installed locally
and you can't update automatically yourself (pypy/old interpreters
like python 3.7).

Done for: Refs pylint-dev#7945
@Pierre-Sassoulas Pierre-Sassoulas added Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry labels Dec 17, 2022
@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.15.9 milestone Dec 17, 2022
@coveralls
Copy link

Pull Request Test Coverage Report for Build 3720380620

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.0%) to 95.445%

Totals Coverage Status
Change from base Build 3708337066: -0.0%
Covered Lines: 17663
Relevant Lines: 18506

💛 - Coveralls

@Pierre-Sassoulas Pierre-Sassoulas merged commit e7d7a1d into pylint-dev:main Dec 17, 2022
@Pierre-Sassoulas Pierre-Sassoulas deleted the merge-maintenance-2.15.x-in-main branch December 17, 2022 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants