Skip to content

No labels!

There aren’t any labels for this repository quite yet.

PR closed due to inactivity
PR closed due to inactivity
on occasion we do rounds to close up inactive PRs, this label makes it easier to track them
python
python
Pull requests that update Python code
status: critical
status: critical
grave problem or usability issue that affects lots of users
status: help wanted
status: help wanted
developers would like help from experts on this topic
status: needs information
status: needs information
reporter needs to provide more information; can be closed after 2 or more weeks of inactivity
topic: approx
topic: approx
Related to pytest.approx function
topic: collection
topic: collection
related to the collection phase
topic: config
topic: config
related to config handling, argument parsing and config file
topic: fixtures
topic: fixtures
anything involving fixtures directly or indirectly
topic: marks
topic: marks
related to marks, either the general marks or builtin
topic: parametrize
topic: parametrize
related to @pytest.mark.parametrize
topic: reporting
topic: reporting
related to terminal output and user-facing messages and errors
topic: rewrite
topic: rewrite
related to the assertion rewrite mechanism
topic: selection
topic: selection
related to test selection from the command line
topic: tracebacks
topic: tracebacks
related to displaying and handling of tracebacks
topic: typing
topic: typing
type-annotation issue
topic: website
topic: website
about the pytest website
type: backward compatibility
type: backward compatibility
might present some backward compatibility issues which should be carefully noted in the changelog
type: bug
type: bug
problem that needs to be addressed
type: deprecation
type: deprecation
feature that will be removed in the future
type: docs
type: docs
documentation improvement, missing or needing clarification
type: enhancement
type: enhancement
new feature or API change, should be merged into features branch
type: feature-branch
type: feature-branch
new feature or API change, should be merged into features branch
type: infrastructure
type: infrastructure
improvement to development/releases/CI structure
type: performance
type: performance
performance or memory problem/improvement
type: proposal
type: proposal
proposal for a new feature, often to gather opinions or design the API around the new feature
type: question
type: question
general question, might be closed after 2 weeks of inactivity
type: refactoring
type: refactoring
internal improvements to the code
type: regression
type: regression
indicates a problem that was introduced in a release which was working previously