Unlabeled
backport 8.3.x
apply to PRs at any point; backports the changes to the 8.3.x branch
backported
PR has been backported to the current bug-fix branch
bot:chronographer:provided
(automation) changelog entry is part of PR
closed as duplicate
issue is a duplicate of another issue
dependencies
pull requests that update a dependency file
github_actions
pull requests that update GitHub Actions code
good first issue
easy issue that is friendly to new contributor
hacktoberfest-accepted
invalid
needs backport
applied to PRs, indicates that it should be ported to the current bug-fix branch
platform: cygwin
cygwin platform-specific problem
platform: linux
linux platform-specific problem
platform: mac
mac platform-specific problem
platform: mingw
platform: wasm/wasi
related to WebAssembly support
platform: windows
windows platform-specific problem
plugin: argcomplete
related to the argcomplete builtin plugin
plugin: cache
related to the cache builtin plugin
plugin: capture
related to the capture builtin plugin
plugin: debugging
related to the debugging builtin plugin
plugin: doctests
related to the doctests builtin plugin
plugin: junitxml
related to the junitxml builtin plugin
plugin: logging
related to the logging builtin plugin
plugin: monkeypatch
related to the monkeypatch builtin plugin
plugin: nose
related to the nose integration builtin plugin
plugin: pastebin
related to the pastebin builtin plugin
plugin: pytester
related to the pytester builtin plugin
plugin: stepwise
plugin: tmpdir
related to the tmpdir builtin plugin
plugin: unittest
related to the unittest integration builtin plugin
plugin: warnings
related to the warnings builtin plugin
plugin: xdist
related to the xdist external plugin
PR closed due to inactivity
on occasion we do rounds to close up inactive PRs, this label makes it easier to track them
python
pull requests that update Python code
skip news
used on prs to opt out of the changelog requirement
stale
status: critical
grave problem or usability issue that affects lots of users
status: help wanted
developers would like help from experts on this topic
status: needs information
reporter needs to provide more information; can be closed after 2 or more weeks of inactivity
topic: approx
related to pytest.approx function
topic: collection
related to the collection phase
topic: config
related to config handling, argument parsing and config file
topic: fixtures
anything involving fixtures directly or indirectly
topic: marks
related to marks, either the general marks or builtin
topic: parametrize
related to @pytest.mark.parametrize
topic: reporting
related to terminal output and user-facing messages and errors
topic: rewrite
related to the assertion rewrite mechanism
topic: selection
related to test selection from the command line
topic: tracebacks
related to displaying and handling of tracebacks
topic: typing
type-annotation issue
topic: website
about the pytest website
type: backward compatibility
might present some backward compatibility issues which should be carefully noted in the changelog
type: bug
problem that needs to be addressed
type: deprecation
feature that will be removed in the future
type: docs
documentation improvement, missing or needing clarification
type: enhancement
new feature or API change, should be merged into features branch
type: feature-branch
new feature or API change, should be merged into features branch
type: infrastructure
improvement to development/releases/CI structure
type: performance
performance or memory problem/improvement
type: proposal
proposal for a new feature, often to gather opinions or design the API around the new feature
type: question
general question, might be closed after 2 weeks of inactivity
type: refactoring
internal improvements to the code
type: regression
indicates a problem that was introduced in a release which was working previously
type: removal
marks the actual removal of a feature, usually done in major releases
type: selftests
a problem in the tests of pytest
No labels found. Sorry about that.