Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

build(deps-dev): update pytest requirement from ~=7.0 to ~=8.2#903

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed

Conversation

@dependabot
Copy link
Contributor

@dependabotdependabotbot commented on behalf ofgithubApr 29, 2024
edited
Loading

Updates the requirements onpytest to permit the latest version.

Release notes

Sourced frompytest's releases.

8.2.0

pytest 8.2.0 (2024-04-27)

Deprecations

  • #12069: A deprecation warning is now raised when implementations of one of the following hooks request a deprecatedpy.path.local parameter instead of thepathlib.Path parameter which replaced it:

    • pytest_ignore_collect{.interpreted-text role="hook"} - thepath parameter - usecollection_path instead.
    • pytest_collect_file{.interpreted-text role="hook"} - thepath parameter - usefile_path instead.
    • pytest_pycollect_makemodule{.interpreted-text role="hook"} - thepath parameter - usemodule_path instead.
    • pytest_report_header{.interpreted-text role="hook"} - thestartdir parameter - usestart_path instead.
    • pytest_report_collectionfinish{.interpreted-text role="hook"} - thestartdir parameter - usestart_path instead.

    The replacement parameters are available since pytest 7.0.0.The old parameters will be removed in pytest 9.0.0.

    Seelegacy-path-hooks-deprecated{.interpreted-text role="ref"} for more details.

Features

  • #11871: Added support for reading command line arguments from a file using the prefix character@, like e.g.:pytest @tests.txt. The file must have one argument per line.

    SeeRead arguments from file <args-from-file>{.interpreted-text role="ref"} for details.

Improvements

  • #11523:pytest.importorskip{.interpreted-text role="func"} will now issue a warning if the module could be found, but raisedImportError{.interpreted-text role="class"} instead ofModuleNotFoundError{.interpreted-text role="class"}.

    The warning can be suppressed by passingexc_type=ImportError topytest.importorskip{.interpreted-text role="func"}.

    Seeimport-or-skip-import-error{.interpreted-text role="ref"} for details.

  • #11728: Forunittest-based tests, exceptions during class cleanup (as raised by functions registered withTestCase.addClassCleanup <unittest.TestCase.addClassCleanup>{.interpreted-text role="meth"}) are now reported instead of silently failing.

  • #11777: Text is no longer truncated in theshort test summary info section when-vv is given.

  • #12112: Improved namespace packages detection whenconsider_namespace_packages{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs).

  • #9502: AddedPYTEST_VERSION{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value ofpytest.__version__, and among other things can be used to easily check if code is running from within a pytest run.

Bug Fixes

  • #12065: Fixed a regression in pytest 8.0.0 where test classes containingsetup_method and tests using@staticmethod or@classmethod would crash withAttributeError: 'NoneType' object has no attribute 'setup_method'.

    Now therequest.instance <pytest.FixtureRequest.instance>{.interpreted-text role="attr"} attribute of tests using@staticmethod and@classmethod is no longerNone, but a fresh instance of the class, like in non-static methods.

... (truncated)

Commits
  • 6bd3f31 Tweak changelog for 8.2.0
  • 9b6219b Prepare release version 8.2.0
  • 835765c Merge pull request#12130 from bluetech/fixtures-inline
  • 7e7503c unittest: report class cleanup exceptions (#12250)
  • 882c4da fixtures: inlinefail_fixturefunc
  • 2e8fb9f fixtures: extract a_check_fixturedef method
  • acf2971 fixtures: inline_getnextfixturedef into_get_active_fixturedef
  • 3c77aec fixtures: move "request" check early
  • d217d68 fixtures: inline_compute_fixture_value
  • 530be28 fixtures: use early return in_get_active_fixturedef
  • Additional commits viewable incompare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

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.2.0)---updated-dependencies:- dependency-name: pytest  dependency-type: direct:production...Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotbot added dependabotcreated by dependabot dependencies labelsApr 29, 2024
@codejedi365codejedi365 changed the titlebuild(deps): update pytest requirement from ~=7.0 to ~=8.2build(deps-dev): update pytest requirement from ~=7.0 to ~=8.2Apr 30, 2024
@codejedi365
Copy link
Contributor

pytest >= 8.0.0 is incompatible with pytest-lazy-fixture, will need some more extensive changes - seeTvoroG/pytest-lazy-fixture#65

wyardley reacted with thumbs up emoji

@codejedi365codejedi365 added the blockedRequires something else before merge or fix labelApr 30, 2024
@wyardley
Copy link
Contributor

pytest >= 8.0.0 is incompatible with pytest-lazy-fixture, will need some more extensive changes - seeTvoroG/pytest-lazy-fixture#65

Was just looking at this too 😞
I was having a little trouble making sense of some of the workarounds, but if you have an example of updating one test, I can definitely look at going through and updating the test cases.

@codejedi365
Copy link
Contributor

Same here, did not understand the workaround and unfortunately no, I didn't look into this problem further. Thank you for the willingness though.

Before I saw this project using lazy-fixture (that I didn't know existed) I believe the more expected way to implement this by pytest would be to have the fixture return a function. That way at the beginning of your test is when you call the function which ensures accurate order of operations within the test. The problem we faced is the fact that parameterization calculations take place first and we expect files to be written and a directory changed to for the repo_* fixtures which causes unintended problems. If you wrap it in lazy-fixture then it is not evaluated until the last second when the test is executed. This also allowed us to pass varied fixtures in as parameters to the test.

But honestly until more PRs are closed out a large refactor of the testing will just cause a bunch of merge conflicts for all of us. I'm not concerned with it at this time, I have bigger fish to fry.

@dependabot@github
Copy link
ContributorAuthor

dependabotbot commented on behalf ofgithubJul 22, 2024

Superseded by#987.

@dependabotdependabotbot closed thisJul 22, 2024
@dependabotdependabotbot deleted the dependabot/pip/pytest-approx-eq-8.2 branchJuly 22, 2024 18:23
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

blockedRequires something else before merge or fixdependabotcreated by dependabotdependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@codejedi365@wyardley

[8]ページ先頭

©2009-2025 Movatter.jp