Skip to content

[pull] main from pytest-dev:main#116

Merged
pull[bot] merged 4 commits into
Stars1233:mainfrom
pytest-dev:main
Nov 20, 2025
Merged

[pull] main from pytest-dev:main#116
pull[bot] merged 4 commits into
Stars1233:mainfrom
pytest-dev:main

Conversation

@pull

@pull pull Bot commented Nov 20, 2025

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )


Summary by cubic

Fix incorrect duplicate parametrization detection when using indirect=[...] and improve error messages by using the full nodeid instead of function names.

  • Bug Fixes

  • Refactors

    • Move _resolve_args_directness to fixtures.py for shared use.
    • Simplify IdMaker by removing func_name and relying on nodeid.

Written for commit 6b6502e. Summary will update automatically on new commits.

The function name is ambiguous, full nodeid is more helpful.
…ect=[...]`

The code in `_get_direct_parametrize_args` only handled
`indirect=True/False`, it didn't account for `indirect=[...]`. This
caused the added test to start failing after
d56b1af.

Fix by using the common `_resolve_args_directness` function. It's a bit
heavy for the task but correctness first...

Fix #13974.
fixtures: fix incorrect "duplicate parametrization" when using `indirect=[...]`
@pull pull Bot locked and limited conversation to collaborators Nov 20, 2025
@pull pull Bot added the ⤵️ pull label Nov 20, 2025
@pull pull Bot merged commit 6b6502e into Stars1233:main Nov 20, 2025
1 check was pending
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"duplicate parametrization" errors with pytest dev

1 participant