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

chore(deps): update minor updates #30

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

chore(deps): update minor updates #30

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 12, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
corner 2.2.2 -> 2.2.3 age adoption passing confidence dependencies patch
dropbox (source) 12.0.0 -> 12.0.2 age adoption passing confidence dependencies patch
mypy (source, changelog) 1.10.0 -> 1.14.1 age adoption passing confidence dev-dependencies minor
pre-commit 3.7.1 -> 3.8.0 age adoption passing confidence dev-dependencies minor
pytest (changelog) 8.2.1 -> 8.3.4 age adoption passing confidence dev-dependencies minor
python >=3.10,<3.12 -> >=3.13,<3.14 age adoption passing confidence dependencies minor

Release Notes

dfm/corner.py (corner)

v2.2.3

Compare Source

What's Changed

New Contributors

Full Changelog: dfm/corner.py@v2.2.2...v2.2.3

dropbox/dropbox-sdk-python (dropbox)

v12.0.2

Compare Source

Release Notes:

  • Remove the pin for urllib3 (#​507)

v12.0.1

Compare Source

Release Notes:

  • Fix incorrect pin of requests (#​505)
python/mypy (mypy)

v1.14.1

Compare Source

v1.14.0

Compare Source

v1.13.0

Compare Source

v1.12.1

Compare Source

  • Fix crash when showing partially analyzed type in error message (Ivan Levkivskyi, PR 17961)
  • Fix iteration over union (when self type is involved) (Shantanu, PR 17976)
  • Fix type object with type var default in union context (Jukka Lehtosalo, PR 17991)
  • Revert change to os.path stubs affecting use of os.PathLike[Any] (Shantanu, PR 17995)

v1.12.0

Compare Source

v1.11.2

Compare Source

  • Alternative fix for a union-like literal string (Ivan Levkivskyi, PR 17639)
  • Unwrap TypedDict item types before storing (Ivan Levkivskyi, PR 17640)

v1.11.1

Compare Source

  • Fix RawExpressionType.accept crash with --cache-fine-grained (Anders Kaseorg, PR 17588)
  • Fix PEP 604 isinstance caching (Shantanu, PR 17563)
  • Fix typing.TypeAliasType being undefined on python < 3.12 (Nikita Sobolev, PR 17558)
  • Fix types.GenericAlias lookup crash (Shantanu, PR 17543)

v1.11.0

Compare Source

v1.10.1

Compare Source

  • Fix error reporting on cached run after uninstallation of third party library (Shantanu, PR 17420)
pre-commit/pre-commit (pre-commit)

v3.8.0

Compare Source

==================

Features
pytest-dev/pytest (pytest)

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 the screen) sometimes not aligning correctly when running with pytest-xdist -n.

Improved documentation

  • #​12153: Documented using PYTEST_VERSION{.interpreted-text role="envvar"} to detect if code is running from within a pytest run.

  • #​12469: The external plugin mentions in the documentation now avoid mentioning
    setuptools entry-points <setuptools:index>{.interpreted-text role="std:doc"} as the concept is
    much more generic nowadays. Instead, the terminology of "external",
    "installed", or "third-party" plugins (or packages) replaces that.

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

  • #​12577: [CI]{.title-ref} and [BUILD_NUMBER]{.title-ref} environment variables role is discribed in
    the reference doc. They now also appear when doing [pytest -h]{.title-ref}
    -- by MarcBresson{.interpreted-text role="user"}.

Contributor-facing changes

  • #​12467: Migrated all internal type-annotations to the python3.10+ style by using the [annotations]{.title-ref} future import.

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

  • #​11771, #​12557: The PyPy runtime version has been updated to 3.9 from 3.8 that introduced
    a flaky bug at the garbage collector which was not expected to fix there
    as the 3.8 is EoL.

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

  • #​12493: The change log draft preview integration has been refactored to use a
    third party extension sphinxcontib-towncrier. The previous in-repo
    script was putting the change log preview file at
    doc/en/_changelog_towncrier_draft.rst{.interpreted-text role="file"}. Said file is no longer
    ignored in Git and might show up among untracked files in the
    development environments of the contributors. To address that, the
    contributors can run the following command that will clean it up:

    $ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst

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

  • #​12498: All the undocumented tox environments now have descriptions.
    They can be listed in one's development environment by invoking
    tox -av in a terminal.

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

  • #​12501: The changelog configuration has been updated to introduce more accurate
    audience-tailored categories. Previously, there was a trivial
    change log fragment type with an unclear and broad meaning. It was
    removed and we now have contrib, misc and packaging in
    place of it.

    The new change note types target the readers who are downstream
    packagers and project contributors. Additionally, the miscellaneous
    section is kept for unspecified updates that do not fit anywhere else.

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

  • #​12502: The UX of the GitHub automation making pull requests to update the
    plugin list has been updated. Previously, the maintainers had to close
    the automatically created pull requests and re-open them to trigger the
    CI runs. From now on, they only need to click the [Ready for review]{.title-ref}
    button instead.

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

  • #​12522: The :pull: RST role has been replaced with a shorter
    :pr: due to starting to use the implementation from
    the third-party sphinx-issues{.interpreted-text role="pypi"} Sphinx extension
    -- by webknjaz{.interpreted-text role="user"}.

  • #​12531: The coverage reporting configuration has been updated to exclude
    pytest's own tests marked as expected to fail from the coverage
    report. This has an effect of reducing the influence of flaky
    tests on the resulting number.

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

  • #​12533: The extlinks Sphinx extension is no longer enabled. The :bpo:
    role it used to declare has been removed with that. BPO itself has
    migrated to GitHub some years ago and it is possible to link the
    respective issues by using their GitHub issue numbers and the
    :issue: role that the sphinx-issues extension implements.

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

  • #​12562: Possible typos in using the :user: RST role is now being linted
    through the pre-commit tool integration -- by webknjaz{.interpreted-text role="user"}.

v8.2.2

Compare Source

pytest 8.2.2 (2024-06-04)

Bug Fixes

  • #​12355: Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.
  • #​12367: Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.
  • #​12381: Fix possible "Directory not empty" crashes arising from concurent cache dir (.pytest_cache) creation. Regressed in pytest 8.2.0.

Improved Documentation

  • #​12290: Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.
  • #​12356: Added a subsection to the documentation for debugging flaky tests to mention
    lack of thread safety in pytest as a possible source of flakyness.
  • #​12363: The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.
containerbase/python-prebuild (python)

v3.13.1

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.1

v3.13.0

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.0

v3.12.8

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.8

v3.12.7

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.7

v3.12.6

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.6

v3.12.5

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.5

v3.12.4

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.4

v3.12.3

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.3

v3.12.2

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.2

v3.12.1

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.1

v3.12.0

Compare Source

Bug Fixes
  • deps: update dependency python to v3.12.0

Configuration

📅 Schedule: Branch creation - "every 4th week on Thursday before 10am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Oct 12, 2023 •
edited
Loading

⚠ 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 ampel-nuclear-FsBIphGQ-py3.12 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's Python requirement (>=3.12,<3.13) is not compatible with some of the required packages Python requirement:
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.12,<3.13

Because ampel-ztf (0.8.5) requires Python >=3.10,<3.12
 and no versions of ampel-ztf match >0.8.5,<0.8.6, ampel-ztf is forbidden.
So, because ampel-nuclear depends on ampel-ztf (>=0.8.5,<0.8.6), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@renovate renovate bot force-pushed the renovate/minor-updates branch from 9338c12 to ae05de8 Compare December 20, 2023 10:53
@renovate renovate bot changed the title fix(deps): update python to >=3.12,<3.13 chore(deps): update minor updates Dec 20, 2023
@renovate renovate bot force-pushed the renovate/minor-updates branch from ae05de8 to 3b718a7 Compare December 21, 2023 18:05
@renovate renovate bot force-pushed the renovate/minor-updates branch from 3b718a7 to d98a9ab Compare December 31, 2023 13:59
@renovate renovate bot force-pushed the renovate/minor-updates branch from d98a9ab to 02734b1 Compare January 24, 2024 18:34
@renovate renovate bot force-pushed the renovate/minor-updates branch from 02734b1 to 75efec8 Compare February 1, 2024 07:52
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from fe80e25 to f66152f Compare February 10, 2024 22:05
@renovate renovate bot force-pushed the renovate/minor-updates branch from f66152f to 227ab4c Compare February 18, 2024 20:07
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from e1795f1 to 8758343 Compare March 3, 2024 22:58
@renovate renovate bot force-pushed the renovate/minor-updates branch 3 times, most recently from f0d1960 to 8f5e916 Compare March 9, 2024 12:01
@renovate renovate bot force-pushed the renovate/minor-updates branch 4 times, most recently from 392377e to 3dcb5b4 Compare March 28, 2024 07:35
@renovate renovate bot force-pushed the renovate/minor-updates branch 3 times, most recently from 745458a to 16af496 Compare April 28, 2024 02:14
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 9, 2024 •
edited
Loading

⚠️ 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 ampel-nuclear-FsBIphGQ-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

The current project's supported Python range (>=3.13,<3.14) is not compatible with some of the required packages Python requirement:
  - ampel-ztf requires Python <3.12,>=3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.9,<3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python <3.12,>=3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python <3.12,>=3.10, so it will not be satisfied for Python >=3.13,<3.14
  - ampel-ztf requires Python >=3.10,<3.12, so it will not be satisfied for Python >=3.13,<3.14

Because no versions of ampel-ztf match <0.7.1 || >0.7.1,<0.7.2 || >0.7.2,<0.7.3 || >0.7.3,<0.7.4 || >0.7.4,<0.7.4.post1 || >0.7.4.post1,<0.7.5 || >0.7.5,<0.8.0a0 || >0.8.0a0,<0.8.0a1 || >0.8.0a1,<0.8.0a2 || >0.8.0a2,<0.8.0a4 || >0.8.0a4,<0.8.0a5 || >0.8.0a5,<0.8.2a0 || >0.8.2a0,<0.8.2a1 || >0.8.2a1,<0.8.2a2 || >0.8.2a2,<0.8.2a4 || >0.8.2a4,<0.8.2a5 || >0.8.2a5,<0.8.2a6 || >0.8.2a6,<0.8.2a7 || >0.8.2a7,<0.8.3 || >0.8.3,<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.9.1a0 || >0.9.1a0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2,<0.10.3a1 || >0.10.3a1,<0.10.3a2 || >0.10.3a2,<0.10.3a3 || >0.10.3a3,<0.10.3a4 || >0.10.3a4
 and ampel-ztf[kafka] (0.8.0a0) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.8.0a1) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.8.0a2) requires Python >=3.9,<3.10
 and ampel-ztf[kafka] (0.8.0a4) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.8.0a5) requires Python >=3.9,<3.10
 and ampel-ztf[kafka] (0.8.2a0) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.8.2a1) requires Python >=3.9,<3.10
 and ampel-ztf[kafka] (0.8.2a2) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.8.2a4) requires Python >=3.9,<3.10
 and ampel-ztf[kafka] (0.8.2a5) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.8.2a6) requires Python >=3.9,<3.10
 and ampel-ztf[kafka] (0.8.2a7) requires Python >=3.9,<3.10, ampel-ztf is forbidden.
And because ampel-ztf[kafka] (0.9.1a0) depends on ampel-ztf (0.9.1a0)
 and ampel-ztf[kafka] (0.10.3a1) depends on ampel-ztf (0.10.3a1), ampel-ztf[kafka] (<0.7.1 || >0.7.1,<0.7.2 || >0.7.2,<0.7.3 || >0.7.3,<0.7.4 || >0.7.4,<0.7.4.post1 || >0.7.4.post1,<0.7.5 || >0.7.5,<0.8.3 || >0.8.3,<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2,<0.10.3a2 || >0.10.3a2,<0.10.3a3 || >0.10.3a3,<0.10.3a4 || >0.10.3a4) requires ampel-ztf (0.9.1a0 || 0.10.3a1).
And because ampel-ztf[kafka] (0.10.3a2) depends on ampel-ztf (0.10.3a2)
 and ampel-ztf[kafka] (0.10.3a3) depends on ampel-ztf (0.10.3a3), ampel-ztf[kafka] (<0.7.1 || >0.7.1,<0.7.2 || >0.7.2,<0.7.3 || >0.7.3,<0.7.4 || >0.7.4,<0.7.4.post1 || >0.7.4.post1,<0.7.5 || >0.7.5,<0.8.3 || >0.8.3,<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2,<0.10.3a4 || >0.10.3a4) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3).
And because ampel-ztf[kafka] (0.10.3a4) depends on ampel-ztf (0.10.3a4)
 and ampel-ztf[kafka] (0.7.1) depends on ampel-interface (>=0.7.1,<0.8.0), ampel-ztf[kafka] (<0.7.2 || >0.7.2,<0.7.3 || >0.7.3,<0.7.4 || >0.7.4,<0.7.4.post1 || >0.7.4.post1,<0.7.5 || >0.7.5,<0.8.3 || >0.8.3,<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.7.2) depends on ampel-interface (>=0.7.1,<0.8.0)
 and ampel-ztf[kafka] (0.7.3) depends on ampel-interface (>=0.7.1,<0.8.0), ampel-ztf[kafka] (<0.7.4 || >0.7.4,<0.7.4.post1 || >0.7.4.post1,<0.7.5 || >0.7.5,<0.8.3 || >0.8.3,<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.7.4) depends on ampel-interface (>=0.7.1,<0.8.0)
 and ampel-ztf[kafka] (0.7.4.post1) depends on ampel-interface (>=0.7.1,<0.8.0), ampel-ztf[kafka] (<0.7.5 || >0.7.5,<0.8.3 || >0.8.3,<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.7.5) depends on ampel-interface (>=0.7.1,<0.8.0)
 and ampel-ztf[kafka] (0.8.3) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.4 || >0.8.4,<0.8.5 || >0.8.5,<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.4) requires Python >=3.10,<3.12
 and ampel-ztf[kafka] (0.8.5) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.6 || >0.8.6,<0.8.7 || >0.8.7,<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.6) requires Python >=3.10,<3.12
 and ampel-ztf[kafka] (0.8.7) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.8 || >0.8.8,<0.8.9 || >0.8.9,<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.8) requires Python >=3.10,<3.12
 and ampel-ztf[kafka] (0.8.9) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.10 || >0.8.10,<0.8.10.post0 || >0.8.10.post0,<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.10) requires Python >=3.10,<3.12
 and ampel-ztf[kafka] (0.8.10.post0) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.11 || >0.8.11,<0.8.12 || >0.8.12,<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.11) requires Python >=3.10,<3.12
 and ampel-ztf[kafka] (0.8.12) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.13 || >0.8.13,<0.8.14 || >0.8.14,<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.13) requires Python >=3.10,<3.12
 and ampel-ztf[kafka] (0.8.14) requires Python <3.12,>=3.10, ampel-ztf[kafka] (<0.8.15 || >0.8.15,<0.8.16 || >0.8.16,<0.9.0 || >0.9.0,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.16) requires Python <3.12,>=3.10
 and ampel-ztf[kafka] (0.9.0) requires Python >=3.10,<3.12, ampel-ztf[kafka] (<0.8.15 || >0.8.15,<0.10.0 || >0.10.0,<0.10.2 || >0.10.2) requires ampel-ztf (0.9.1a0 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.10.0) depends on ampel-ztf (0.10.0)
 and ampel-ztf[kafka] (0.10.2) depends on ampel-ztf (0.10.2), ampel-ztf[kafka] (!=0.8.15) requires ampel-ztf (0.9.1a0 || 0.10.0 || 0.10.2 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4) or ampel-interface (>=0.7.1,<0.8.0).
And because ampel-ztf[kafka] (0.8.15) requires Python <3.12,>=3.10
 and ampel-nuclear depends on ampel-interface (>=0.8.7,<0.9), every version of ampel-ztf[kafka] requires ampel-ztf (0.9.1a0 || 0.10.0 || 0.10.2 || 0.10.3a1 || 0.10.3a2 || 0.10.3a3 || 0.10.3a4).
So, because ampel-nuclear depends on both ampel-ztf (>=0.8.5,<0.9) and ampel-ztf[kafka] (*), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"
    For ampel-ztf, a possible solution would be to set the `python` property to "<empty>"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@renovate renovate bot force-pushed the renovate/minor-updates branch from 16af496 to 1c0ae26 Compare May 11, 2024 02:13
@renovate renovate bot force-pushed the renovate/minor-updates branch from 1c0ae26 to 7ebdf25 Compare May 19, 2024 22:14
@renovate renovate bot force-pushed the renovate/minor-updates branch from 7ebdf25 to b94c9c2 Compare May 30, 2024 12:21
@renovate renovate bot force-pushed the renovate/minor-updates branch from b94c9c2 to 51224b0 Compare May 30, 2024 12:46
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from b2c7552 to cd8802c Compare June 4, 2024 17:10
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from 76b29c8 to de21d23 Compare June 25, 2024 01:29
@renovate renovate bot force-pushed the renovate/minor-updates branch 3 times, most recently from a54cf17 to 5a2abc5 Compare July 25, 2024 13:00
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from 5cef78e to f3cfd1d Compare July 31, 2024 03:33
@renovate renovate bot force-pushed the renovate/minor-updates branch from f3cfd1d to 217cc3d Compare August 25, 2024 00:17
@renovate renovate bot force-pushed the renovate/minor-updates branch from 217cc3d to 3dc5e6b Compare September 10, 2024 13:37
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from 5290419 to 78652de Compare October 14, 2024 19:53
@renovate renovate bot force-pushed the renovate/minor-updates branch 2 times, most recently from d21a660 to f17004a Compare October 22, 2024 22:30
@renovate renovate bot force-pushed the renovate/minor-updates branch from f17004a to c2dfa32 Compare November 19, 2024 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

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

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