Skip to content

Run tests with Python 3.11.0#7671

Merged
Pierre-Sassoulas merged 1 commit intopylint-dev:mainfrom
cdce8p:python-311
Oct 25, 2022
Merged

Run tests with Python 3.11.0#7671
Pierre-Sassoulas merged 1 commit intopylint-dev:mainfrom
cdce8p:python-311

Conversation

@cdce8p
Copy link
Copy Markdown
Member

@cdce8p cdce8p commented Oct 25, 2022

Description

Python 3.11 was released yesterday 🎉

@cdce8p cdce8p added Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry labels Oct 25, 2022
@cdce8p cdce8p added this to the 2.16.0 milestone Oct 25, 2022
@coveralls
Copy link
Copy Markdown

coveralls commented Oct 25, 2022

Pull Request Test Coverage Report for Build 3323787430

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 95.359%

Totals Coverage Status
Change from base Build 3323697382: 0.0%
Covered Lines: 17178
Relevant Lines: 18014

💛 - Coveralls

@github-actions

This comment has been minimized.

@Pierre-Sassoulas
Copy link
Copy Markdown
Member

Thank you @cdce8p 👍 It seems like the windows 3.11 fail is genuine, I don't see any significant change to the io module in the release note though.

@cdce8p
Copy link
Copy Markdown
Member Author

cdce8p commented Oct 25, 2022

Thank you @cdce8p 👍 It seems like the windows 3.11 fail is genuine, I don't see any significant change to the io module in the release note though.

Seems like an issue with the new pytest release (7.2.0) and pytest-benchmark. ionelmc/pytest-benchmark#226
We could pin pytest==7.1.3 until a new version for pytest-benchmark is released.

@Pierre-Sassoulas
Copy link
Copy Markdown
Member

Seems like an issue with the new pytest release (7.2.0) and pytest-benchmark.

Hmm, right, it's not related to this MR, 3.11-dev also fail on main right now. Do you think we should open another MR or fix in this one ?

@cdce8p
Copy link
Copy Markdown
Member Author

cdce8p commented Oct 25, 2022

Seems like an issue with the new pytest release (7.2.0) and pytest-benchmark.

Hmm, right, it's not related to this MR, 3.11-dev also fail on main right now. Do you think we should open another MR or fix in this one ?

Let's do it in a separate one in case we won't to backport it to the 2.15.x branch.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Effect of this PR on checked open source code: 🤖

Effect on pytest:
The following messages are now emitted:

Details
  1. inconsistent-return-statements:
    Either all return statements in a function should return an expression, or none of them should.
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/pytester.py#L301
  2. no-name-in-module:
    No name 'NOSE_SUPPORT_METHOD' in module '_pytest.deprecated'
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/python.py#L62
  3. no-name-in-module:
    No name 'PytestReturnNotNoneWarning' in module '_pytest.warning_types'
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/python.py#L81
  4. inconsistent-return-statements:
    Either all return statements in a function should return an expression, or none of them should.
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/python.py#L1085
  5. inconsistent-return-statements:
    Either all return statements in a function should return an expression, or none of them should.
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/fixtures.py#L130
  6. inconsistent-return-statements:
    Either all return statements in a function should return an expression, or none of them should.
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/python_api.py#L798
  7. no-name-in-module:
    No name 'NOSE_SUPPORT' in module '_pytest.deprecated'
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/nose.py#L5
  8. no-name-in-module:
    No name 'warn_explicit_for' in module '_pytest.warning_types'
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/config/__init__.py#L62
  9. no-member:
    Module '_pytest.deprecated' has no 'HOOK_LEGACY_MARKING' member
    https://github.com/pytest-dev/pytest/blob/bbe7cbae4aa24f4cb65230704b870c5dcf40781e/src/_pytest/config/__init__.py#L369

This comment was generated for commit c62301e

@cdce8p cdce8p deleted the python-311 branch October 26, 2022 07:09
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.

3 participants