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.

Sign up for GitHub

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

Jump to bottom

⬆️ 🤖 Dependencies: Update pytest requirement from ^7.0 to >=7,<9 #322

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

⬆️ 🤖 Dependencies: Update pytest requirement from ^7.0 to >=7,<9 #322

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 9, 2024 •
edited by sourcery-ai bot
Loading

Updates the requirements on pytest to permit the latest version.

Release notes

Sourced from pytest's releases.

8.3.4

pytest 8.3.4 (2024-12-01)

Bug fixes

  • #12592: Fixed KeyError{.interpreted-text role="class"} crash when using --import-mode=importlib in a directory layout where a directory contains a child directory with the same name.

  • #12818: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the AST, like executing.

  • #12849: ANSI escape codes for colored output now handled correctly in pytest.fail{.interpreted-text role="func"} with [pytrace=False]{.title-ref}.

  • #9353: pytest.approx{.interpreted-text role="func"} now uses strict equality when given booleans.

Improved documentation

  • #10558: Fix ambiguous docstring of pytest.Config.getoption{.interpreted-text role="func"}.

  • #10829: Improve documentation on the current handling of the --basetemp option and its lack of retention functionality (temporary directory location and retention{.interpreted-text role="ref"}).

  • #12866: Improved cross-references concerning the recwarn{.interpreted-text role="fixture"} fixture.

  • #12966: Clarify filterwarnings{.interpreted-text role="ref"} docs on filter precedence/order when using multiple @pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>{.interpreted-text role="ref"} marks.

Contributor-facing changes

  • #12497: Fixed two failing pdb-related tests on Python 3.13.
Commits
  • 53f8b4e Update pypa/gh-action-pypi-publish to v1.12.2
  • 98dff36 Prepare release version 8.3.4
  • 1b474e2 approx: use exact comparison for bool (#13013)
  • b541721 docs: Fix wrong statement about sys.modules with importlib import mode (#1298...
  • 16cb87b pytest.fail: fix ANSI escape codes for colored output (#12959) (#12990)
  • be6bc81 Issue #12966 Clarify filterwarnings docs on precedence when using multiple ma...
  • 7aeb72b Improve docs on basetemp and retention (#12912) (#12928)
  • c875841 Merge pull request #12917 from pytest-dev/patchback/backports/8.3.x/ded1f44e5...
  • 6502816 Merge pull request #12913 from jakkdl/dontfailonbadpath
  • 52135b0 Merge pull request #12885 from The-Compiler/pdb-py311 (#12887)
  • Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Build:

  • Update pytest dependency version range in pyproject.toml to allow versions from 7 up to but not including 9.

@dependabot
⬆️ 🤖 Dependencies: Update pytest requirement from ^7.0 to >=7,<9
2881f9d 
Updates the requirements on [pytest](https://github.com/pytest-dev/pytest) to permit the latest version.
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@7.0.0...8.3.4)

---
updated-dependencies:
- dependency-name: pytest
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@sourcery-ai Sourcery AI
Copy link

sourcery-ai bot commented Dec 9, 2024 •
edited
Loading

Reviewer's Guide by Sourcery

This PR updates the pytest dependency version constraint from ^7.0 to >=7,<9 in the project's dependencies. This change allows the project to use newer versions of pytest while maintaining compatibility with version 7 and preventing updates to version 9 or higher.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated pytest version constraint in poetry dependencies
  • Changed version constraint from caret notation (^7.0) to range notation (>=7,<9)
  • Maintains backward compatibility with version 7
  • Allows updates up to but not including version 9
 pyproject.toml
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

sourcery-ai[bot]
sourcery-ai bot reviewed Dec 9, 2024
View reviewed changes
Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

llamapreview[bot]
llamapreview bot reviewed Dec 9, 2024
View reviewed changes
Copy link

@llamapreview llamapreview bot left a comment

Choose a reason for hiding this comment

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

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR contains only dependency version updates, requiring no automated code review

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@llamapreview llamapreview[bot] llamapreview[bot] left review comments

@sourcery-ai sourcery-ai[bot] sourcery-ai[bot] left review comments

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants