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

Lock file maintenance Python dependencies #159

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 9, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
codespell lint minor ^2.3.0 -> ^2.4.1 age adoption passing confidence
cosl charm-libs patch 0.0.55 -> 0.0.56 age adoption passing confidence
jinja2 (changelog) dependencies patch ^3.1.4 -> ^3.1.5 age adoption passing confidence
jsonschema (changelog) charm-libs minor 4.22.0 -> 4.23.0 age adoption passing confidence
ops-scenario unit minor ^6.0.3, <6.0.4 -> ^6.1.7, <6.1.8 age adoption passing confidence
pydantic (changelog) charm-libs patch 1.10.17 -> 1.10.21 age adoption passing confidence
pytest (changelog) integration minor ^8.2.2 -> ^8.3.5 age adoption passing confidence
pytest (changelog) unit minor ^8.2.2 -> ^8.3.5 age adoption passing confidence
pytest-operator integration minor ^0.35.0 -> ^0.40.0 age adoption passing confidence
ruff (source, changelog) lint minor ^0.4.5 -> ^0.9.9 age adoption passing confidence
ruff (source, changelog) format minor ^0.4.5 -> ^0.9.9 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.


Release Notes

codespell-project/codespell (codespell)

v2.4.1

Compare Source

What's Changed

New Contributors

Full Changelog: codespell-project/codespell@v2.4.0...v2.4.1

v2.4.0

Compare Source

What's Changed

New Contributors

Full Changelog: codespell-project/codespell@v2.3.0...v2.4.0

canonical/cos-lib (cosl)

v0.0.56

Compare Source

Add cluster configuration to enable a coordinator to tell the workers which ports to open.

python-jsonschema/jsonschema (jsonschema)

v4.23.0

Compare Source

=======

  • Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
  • Declare support for Py3.13
pydantic/pydantic (pydantic)

v1.10.21

Compare Source

v1.10.20: 2025-01-07

Compare Source

What's Changed

This release provides proper support for Python 3.13, with (Cythonized) wheels published for this version.
As a consequence, Cython was updated from 0.29.x to 3.0.x.

New Contributors

Full Changelog: pydantic/pydantic@v1.10.19...v1.10.20

v1.10.19

Compare Source

v1.10.18

Compare Source

pytest-dev/pytest (pytest)

v8.3.5

Compare Source

pytest 8.3.5 (2025-03-02)

Bug fixes

  • #​11777: Fixed issue where sequences were still being shortened even with -vv verbosity.
  • #​12888: Fixed broken input when using Python 3.13+ and a libedit build of Python, such as on macOS or with uv-managed Python binaries from the python-build-standalone project. This could manifest e.g. by a broken prompt when using Pdb, or seeing empty inputs with manual usage of input() and suspended capturing.
  • #​13026: Fixed AttributeError{.interpreted-text role="class"} crash when using --import-mode=importlib when top-level directory same name as another module of the standard library.
  • #​13053: Fixed a regression in pytest 8.3.4 where, when using --import-mode=importlib, a directory containing py file with the same name would cause an ImportError
  • #​13083: Fixed issue where pytest could crash if one of the collected directories got removed during collection.

Improved documentation

  • #​12842: Added dedicated page about using types with pytest.

    See types{.interpreted-text role="ref"} for detailed usage.

Contributor-facing changes

  • #​13112: Fixed selftest failures in test_terminal.py with Pygments >= 2.19.0
  • #​13256: Support for Towncier versions released in 2024 has been re-enabled
    when building Sphinx docs -- by webknjaz{.interpreted-text role="user"}.

v8.3.4

Compare Source

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.

v8.3.3

Compare Source

pytest 8.3.3 (2024-09-09)

Bug fixes

  • #​12446: Avoid calling @property (and other instance descriptors) during fixture discovery -- by asottile{.interpreted-text role="user"}

  • #​12659: Fixed the issue of not displaying assertion failure differences when using the parameter --import-mode=importlib in pytest>=8.1.

  • #​12667: Fixed a regression where type change in [ExceptionInfo.errisinstance]{.title-ref} caused [mypy]{.title-ref} to fail.

  • #​12744: Fixed typing compatibility with Python 3.9 or less -- replaced [typing.Self]{.title-ref} with [typing_extensions.Self]{.title-ref} -- by Avasam{.interpreted-text role="user"}

  • #​12745: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.

  • #​6682: Fixed bug where the verbosity levels where not being respected when printing the "msg" part of failed assertion (as in assert condition, msg).

  • #​9422: Fix bug where disabling the terminal plugin via -p no:terminal would cause crashes related to missing the verbose option.

    -- by GTowers1{.interpreted-text role="user"}

Improved documentation

  • #​12663: Clarify that the [pytest_deselected]{.title-ref} hook should be called from [pytest_collection_modifyitems]{.title-ref} hook implementations when items are deselected.
  • #​12678: Remove erroneous quotes from [tmp_path_retention_policy]{.title-ref} example in docs.

Miscellaneous internal changes

  • #​12769: Fix typos discovered by codespell and add codespell to pre-commit hooks.

v8.3.2

Compare Source

pytest 8.3.2 (2024-07-24)

Bug fixes

  • #​12652: Resolve regression [conda]{.title-ref} environments where no longer being automatically detected.

    -- by RonnyPfannschmidt{.interpreted-text role="user"}

v8.3.1

Compare Source

pytest 8.3.1 (2024-07-20)

The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.

v8.3.0

Compare Source

pytest 8.3.0 (2024-07-20)

New features

  • #​12231: Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.

    • If the [--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown.
    • The style of traceback for XFAIL is set with [--tb]{.title-ref}, and can be [auto|long|short|line|native|no]{.title-ref}.
    • Note: Even if you have [--xfail-tb]{.title-ref} set, you won't see them if [--tb=no]{.title-ref}.

    Some history:

    With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks.

    This change detaches xfail tracebacks from [-rx]{.title-ref}, and now we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this, the default [-rx]{.title-ref}/ [-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.

  • #​12281: Added support for keyword matching in marker expressions.

    Now tests can be selected by marker keyword arguments.
    Supported values are int{.interpreted-text role="class"}, (unescaped) str{.interpreted-text role="class"}, bool{.interpreted-text role="class"} & None{.interpreted-text role="data"}.

    See marker examples <marker_keyword_expression_example>{.interpreted-text role="ref"} for more information.

    -- by lovetheguitar{.interpreted-text role="user"}

  • #​12567: Added --no-fold-skipped command line option.

    If this option is set, then skipped tests in short summary are no longer grouped
    by reason but all tests are printed individually with their nodeid in the same
    way as other statuses.

    -- by pbrezina{.interpreted-text role="user"}

Improvements in existing functionality

  • #​12469: The console output now uses the "third-party plugins" terminology,
    replacing the previously established but confusing and outdated
    reference to setuptools <setuptools:index>{.interpreted-text role="std:doc"}
    -- by webknjaz{.interpreted-text role="user"}.

  • #​12544, #​12545: Python virtual environment detection was improved by
    checking for a pyvenv.cfg{.interpreted-text role="file"} file, ensuring reliable detection on
    various platforms -- by zachsnickers{.interpreted-text role="user"}.

  • #​2871: Do not truncate arguments to functions in output when running with [-vvv]{.title-ref}.

  • #​389: The readability of assertion introspection of bound methods has been enhanced
    -- by farbodahm{.interpreted-text role="user"}, webknjaz{.interpreted-text role="user"}, obestwalter{.interpreted-text role="user"}, flub{.interpreted-text role="user"}
    and glyphack{.interpreted-text role="user"}.

    Earlier, it was like:

    =================================== FAILURES ===================================
    _____________________________________ test _____________________________________
    
        def test():
    >       assert Help().fun() == 2
    E       assert 1 == 2
    E        +  where 1 = <bound method Help.fun of <example.Help instance at 0x256a830>>()
    E        +    where <bound method Help.fun of <example.Help instance at 0x256a830>> = <example.Help instance at 0x256a830>.fun
    E        +      where <example.Help instance at 0x256a830> = Help()
    
    example.py:7: AssertionError
    =========================== 1 failed in 0.03 seconds ===========================

    And now it's like:

    =================================== FAILURES ===================================
    _____________________________________ test _____________________________________
    
        def test():
    >       assert Help().fun() == 2
    E       assert 1 == 2
    E        +  where 1 = fun()
    E        +    where fun = <test_local.Help object at 0x1074be230>.fun
    E        +      where <test_local.Help object at 0x1074be230> = Help()
    
    test_local.py:13: AssertionError
    =========================== 1 failed in 0.03 seconds ===========================
  • #​7662: Added timezone information to the testsuite timestamp in the JUnit XML report.

Bug fixes

  • #​11706: Fixed reporting of teardown errors in higher-scoped fixtures when using [--maxfail]{.title-ref} or [--stepwise]{.title-ref}.

    Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist.
    This regression was fixed in pytest-xdist 3.6.1.

  • #​11797: pytest.approx{.interpreted-text role="func"} now correctly handles Sequence <collections.abc.Sequence>{.interpreted-text role="class"}-like objects.

  • #​12204, #​12264: Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple
    tests fail due to a shared higher-scope fixture which raised -- by bluetech{.interpreted-text role="user"}.

    Also fixed a similar regression in pytest 5.4 for collectors which raise during setup.

    The fix necessitated internal changes which may affect some plugins:

    • FixtureDef.cached_result[2] is now a tuple (exc, tb)
      instead of exc.
    • SetupState.stack failures are now a tuple (exc, tb)
      instead of exc.
  • #​12275: Fixed collection error upon encountering an abstract <abc>{.interpreted-text role="mod"} class, including abstract [unittest.TestCase]{.title-ref} subclasses.

  • #​12328: Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases.

  • #​12424: Fixed crash with [assert testcase is not None]{.title-ref} assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2.

  • #​12472: Fixed a crash when returning category "error" or "failed" with a custom test status from pytest_report_teststatus{.interpreted-text role="hook"} hook -- pbrezina{.interpreted-text role="user"}.

  • #​12505: Improved handling of invalid regex patterns in pytest.raises(match=r'...') <pytest.raises>{.interpreted-text role="func"} by providing a clear error message.

  • #​12580: Fixed a crash when using the cache class on Windows and the cache directory was created concurrently.

  • #​6962: Parametrization parameters are now compared using [==]{.title-ref} instead of [is]{.title-ref} ([is]{.title-ref} is still used as a fallback if the parameter does not support [==]{.title-ref}).
    This fixes use of parameters such as lists, which have a different [id]{.title-ref} but compare equal, causing fixtures to be re-computed instead of being cached.

  • #​7166: Fixed progress percentages (the [ 87%] at the edge of t


Configuration

📅 Schedule: Branch creation - "* 1-5 * * 2" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from a team, paulomach, taurus-forever, shayancanonical and carlcsaposs-canonical and removed request for a team July 9, 2024 01:09
Copy link
Contributor Author

renovate bot commented Jul 9, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...

Creating virtualenv non-package-mode-88ziTglk-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

Because ops-scenario (6.1.7) depends on ops (>=2.12,<=2.16)
 and no versions of ops-scenario match >6.1.7,<6.1.8, ops-scenario (>=6.1.7,<6.1.8) requires ops (>=2.12,<=2.16).
So, because non-package-mode depends on both ops (>=2.9.0,<2.10) and ops-scenario (^6.1.7, <6.1.8), version solving failed.

@renovate renovate bot force-pushed the renovate/python-dependencies branch from 83f9b4b to 925f685 Compare July 10, 2024 01:44
Copy link
Contributor

@taurus-forever taurus-forever left a comment

Choose a reason for hiding this comment

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

@carlcsaposs-canonical any ideas why lint is not happy here?

@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 01e1a9e to 1d3b59b Compare July 25, 2024 01:30
@carlcsaposs-canonical
Copy link
Contributor

@carlcsaposs-canonical any ideas why lint is not happy here?

#159 (comment)

@renovate renovate bot force-pushed the renovate/python-dependencies branch from 1d3b59b to 20dd0f9 Compare July 26, 2024 01:26
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 20dd0f9 to 33c0c94 Compare August 8, 2024 01:18
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 33c0c94 to 1a09e29 Compare August 20, 2024 01:17
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 1a09e29 to cacf9b8 Compare August 29, 2024 02:24
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 66a39db to f27b39d Compare September 11, 2024 01:18
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 473af02 to 76b8f8a Compare October 2, 2024 01:36
@renovate renovate bot force-pushed the renovate/python-dependencies branch 3 times, most recently from 1c2e990 to 7f5bf70 Compare October 15, 2024 20:50
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 814b971 to e026879 Compare October 25, 2024 01:12
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from e9a2f6c to b513b82 Compare November 18, 2024 01:10
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 9934558 to af2af3c Compare November 28, 2024 01:44
@renovate renovate bot force-pushed the renovate/python-dependencies branch from af2af3c to 7ff6a62 Compare December 4, 2024 02:14
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 5a7b01f to 66905eb Compare December 13, 2024 01:03
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from fd864f9 to fb64db4 Compare December 23, 2024 02:25
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from d882ca1 to 8002711 Compare January 6, 2025 02:28
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from eb1b8ca to 36eeb46 Compare January 17, 2025 02:36
@renovate renovate bot force-pushed the renovate/python-dependencies branch 3 times, most recently from 7966d1b to 5fa513e Compare January 29, 2025 02:23
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 3bcfa66 to 459cc39 Compare February 7, 2025 02:59
@renovate renovate bot force-pushed the renovate/python-dependencies branch 3 times, most recently from 7c33397 to bbc8988 Compare February 14, 2025 01:54
@renovate renovate bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Feb 14, 2025
@renovate renovate bot force-pushed the renovate/python-dependencies branch from bbc8988 to b7c4d66 Compare February 19, 2025 01:09
@renovate renovate bot force-pushed the renovate/python-dependencies branch from b7c4d66 to a5adfa5 Compare February 21, 2025 01:56
@renovate renovate bot force-pushed the renovate/python-dependencies branch 2 times, most recently from 9332e91 to 3539a21 Compare March 3, 2025 01:57
Copy link
Contributor

@carlcsaposs-canonical carlcsaposs-canonical left a comment

Choose a reason for hiding this comment

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

rebase after #165 merged & exclude ops-scenario update

@renovate renovate bot force-pushed the renovate/python-dependencies branch from 3539a21 to dc7f885 Compare March 4, 2025 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Libraries: Out of sync not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants