Clarify package scope

The behavior of package scope is surprising to some
(as seen by related questions on SO), this should clarify it a bit.
This commit is contained in:
mrbean-bremen 2024-01-11 19:02:26 +01:00 committed by mrbean-bremen
parent bd58c09500
commit 82fda31e99
No known key found for this signature in database
GPG Key ID: 0E41ADF9EFE4FE7C
1 changed files with 1 additions and 1 deletions

View File

@ -494,7 +494,7 @@ Fixtures are created when first requested by a test, and are destroyed based on
* ``function``: the default scope, the fixture is destroyed at the end of the test. * ``function``: the default scope, the fixture is destroyed at the end of the test.
* ``class``: the fixture is destroyed during teardown of the last test in the class. * ``class``: the fixture is destroyed during teardown of the last test in the class.
* ``module``: the fixture is destroyed during teardown of the last test in the module. * ``module``: the fixture is destroyed during teardown of the last test in the module.
* ``package``: the fixture is destroyed during teardown of the last test in the package. * ``package``: the fixture is destroyed during teardown of the last test in the package where the fixture is defined, including sub-packages and sub-directories within it.
* ``session``: the fixture is destroyed at the end of the test session. * ``session``: the fixture is destroyed at the end of the test session.
.. note:: .. note::