Prepare release version 6.1.2

[6.1.x] Increase temp dir deletion period to 3 days (#7914)

.github/ISSUE_TEMPLATE/2_feature_request.md

@@ -3,23 +3,3 @@ name: 🚀 Feature Request
 about: Ideas for new features and improvements
 
 ---
-
-<!--
-Thanks for suggesting a feature!
-
-Quick check-list while suggesting features:
--->
-
-#### What's the problem this feature will solve?
-<!-- What are you trying to do, that you are unable to achieve with pytest as it currently stands? -->
-
-#### Describe the solution you'd like
-<!-- A clear and concise description of what you want to happen. -->
-
-<!-- Provide examples of real-world use cases that this would enable and how it solves the problem described above. -->
-
-#### Alternative Solutions
-<!-- Have you tried to workaround the problem using a pytest plugin or other tools? Or a different approach to solving this issue? Please elaborate here. -->
-
-#### Additional context
-<!-- Add any other context, links, etc. about the feature here. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -13,7 +13,7 @@ If this change fixes an issue, please:
 
 Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:
 
-- [ ] Create a new changelog file in the `changelog` folder, with a name like `<ISSUE NUMBER>.<TYPE>.rst`. See [changelog/README.rst](https://github.com/pytest-dev/pytest/blob/main/changelog/README.rst) for details.
+- [ ] Create a new changelog file in the `changelog` folder, with a name like `<ISSUE NUMBER>.<TYPE>.rst`. See [changelog/README.rst](https://github.com/pytest-dev/pytest/blob/master/changelog/README.rst) for details.
 
   Write sentences in the **past or present tense**, examples:
 

.github/dependabot.yml

@@ -1,11 +0,0 @@
-version: 2
-updates:
-- package-ecosystem: pip
-  directory: "/testing/plugins_integration"
-  schedule:
-    interval: weekly
-    time: "03:00"
-  open-pull-requests-limit: 10
-  allow:
-  - dependency-type: direct
-  - dependency-type: indirect

.github/workflows/main.yml

@@ -3,48 +3,38 @@ name: main
 on:
   push:
     branches:
-      - main
+      - master
       - "[0-9]+.[0-9]+.x"
     tags:
-      - "[0-9]+.[0-9]+.[0-9]+"
-      - "[0-9]+.[0-9]+.[0-9]+rc[0-9]+"
+      - "*"
 
   pull_request:
     branches:
-      - main
+      - master
       - "[0-9]+.[0-9]+.x"
 
-env:
-  PYTEST_ADDOPTS: "--color=yes"
-
-# Set permissions at the job level.
-permissions: {}
-
 jobs:
   build:
     runs-on: ${{ matrix.os }}
     timeout-minutes: 30
-    permissions:
-      contents: read
 
     strategy:
       fail-fast: false
       matrix:
         name: [
+          "windows-py35",
           "windows-py36",
           "windows-py37",
           "windows-py37-pluggy",
           "windows-py38",
-          "windows-py39",
-          "windows-py310",
 
+          "ubuntu-py35",
           "ubuntu-py36",
           "ubuntu-py37",
           "ubuntu-py37-pluggy",
           "ubuntu-py37-freeze",
           "ubuntu-py38",
           "ubuntu-py39",
-          "ubuntu-py310",
           "ubuntu-pypy3",
 
           "macos-py37",
@@ -56,6 +46,11 @@ jobs:
         ]
 
         include:
+          - name: "windows-py35"
+            python: "3.5"
+            os: windows-latest
+            tox_env: "py35-xdist"
+            use_coverage: true
           - name: "windows-py36"
             python: "3.6"
             os: windows-latest
@@ -67,21 +62,17 @@ jobs:
           - name: "windows-py37-pluggy"
             python: "3.7"
             os: windows-latest
-            tox_env: "py37-pluggymain-xdist"
+            tox_env: "py37-pluggymaster-xdist"
           - name: "windows-py38"
             python: "3.8"
             os: windows-latest
             tox_env: "py38-unittestextras"
             use_coverage: true
-          - name: "windows-py39"
-            python: "3.9"
-            os: windows-latest
-            tox_env: "py39-xdist"
-          - name: "windows-py310"
-            python: "3.10-dev"
-            os: windows-latest
-            tox_env: "py310-xdist"
 
+          - name: "ubuntu-py35"
+            python: "3.5"
+            os: ubuntu-latest
+            tox_env: "py35-xdist"
           - name: "ubuntu-py36"
             python: "3.6"
             os: ubuntu-latest
@@ -89,12 +80,12 @@ jobs:
           - name: "ubuntu-py37"
             python: "3.7"
             os: ubuntu-latest
-            tox_env: "py37-lsof-numpy-pexpect"
+            tox_env: "py37-lsof-numpy-oldattrs-pexpect"
             use_coverage: true
           - name: "ubuntu-py37-pluggy"
             python: "3.7"
             os: ubuntu-latest
-            tox_env: "py37-pluggymain-xdist"
+            tox_env: "py37-pluggymaster-xdist"
           - name: "ubuntu-py37-freeze"
             python: "3.7"
             os: ubuntu-latest
@@ -104,15 +95,11 @@ jobs:
             os: ubuntu-latest
             tox_env: "py38-xdist"
           - name: "ubuntu-py39"
-            python: "3.9"
+            python: "3.9-dev"
             os: ubuntu-latest
             tox_env: "py39-xdist"
-          - name: "ubuntu-py310"
-            python: "3.10-dev"
-            os: ubuntu-latest
-            tox_env: "py310-xdist"
           - name: "ubuntu-pypy3"
-            python: "pypy-3.7"
+            python: "pypy3"
             os: ubuntu-latest
             tox_env: "pypy3-xdist"
 
@@ -145,13 +132,16 @@ jobs:
     - uses: actions/checkout@v2
       with:
         fetch-depth: 0
-        persist-credentials: false
-
     - name: Set up Python ${{ matrix.python }}
       uses: actions/setup-python@v2
+      if: matrix.python != '3.9-dev'
+      with:
+        python-version: ${{ matrix.python }}
+    - name: Set up Python ${{ matrix.python }} (deadsnakes)
+      uses: deadsnakes/action@v2.0.0
+      if: matrix.python == '3.9-dev'
       with:
         python-version: ${{ matrix.python }}
-
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
@@ -163,39 +153,35 @@ jobs:
 
     - name: Test with coverage
       if: "matrix.use_coverage"
-      run: "tox -e ${{ matrix.tox_env }}-coverage"
+      env:
+        _PYTEST_TOX_COVERAGE_RUN: "coverage run -m"
+        COVERAGE_PROCESS_START: ".coveragerc"
+        _PYTEST_TOX_EXTRA_DEP: "coverage-enable-subprocess"
+      run: "tox -e ${{ matrix.tox_env }}"
 
-    - name: Upload coverage
-      if: matrix.use_coverage && github.repository == 'pytest-dev/pytest'
+    - name: Prepare coverage token
+      if: (matrix.use_coverage && ( github.repository == 'pytest-dev/pytest' || github.event_name == 'pull_request' ))
+      run: |
+        python scripts/append_codecov_token.py
+
+    - name: Report coverage
+      if: (matrix.use_coverage)
       env:
         CODECOV_NAME: ${{ matrix.name }}
-      run: bash scripts/upload-coverage.sh -F GHA,${{ runner.os }}
+      run: bash scripts/report-coverage.sh -F GHA,${{ runner.os }}
 
   linting:
     runs-on: ubuntu-latest
-    permissions:
-      contents: read
-
     steps:
     - uses: actions/checkout@v2
-      with:
-        persist-credentials: false
-
     - uses: actions/setup-python@v2
-
     - name: set PY
-      run: echo "name=PY::$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')" >> $GITHUB_ENV
-
-    - uses: actions/cache@v2
+      run: echo "::set-env name=PY::$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')"
+    - uses: actions/cache@v1
       with:
         path: ~/.cache/pre-commit
         key: pre-commit|${{ env.PY }}|${{ hashFiles('.pre-commit-config.yaml') }}
-
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install tox
-
+    - run: pip install tox
     - run: tox -e linting
 
   deploy:
@@ -203,8 +189,6 @@ jobs:
 
     runs-on: ubuntu-latest
     timeout-minutes: 30
-    permissions:
-      contents: write
 
     needs: [build]
 
@@ -212,31 +196,25 @@ jobs:
     - uses: actions/checkout@v2
       with:
         fetch-depth: 0
-        persist-credentials: false
-
     - name: Set up Python
       uses: actions/setup-python@v2
       with:
         python-version: "3.7"
-
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
         pip install --upgrade wheel setuptools tox
-
     - name: Build package
       run: |
         python setup.py sdist bdist_wheel
-
     - name: Publish package to PyPI
       uses: pypa/gh-action-pypi-publish@master
       with:
         user: __token__
         password: ${{ secrets.pypi_token }}
-
     - name: Publish GitHub release notes
       env:
-        GH_RELEASE_NOTES_TOKEN: ${{ github.token }}
+        GH_RELEASE_NOTES_TOKEN: ${{ secrets.release_notes }}
       run: |
         sudo apt-get install pandoc
         tox -e publish-gh-release-notes

.github/workflows/prepare-release-pr.yml

@@ -1,53 +0,0 @@
-name: prepare release pr
-
-on:
-  workflow_dispatch:
-    inputs:
-      branch:
-        description: 'Branch to base the release from'
-        required: true
-        default: ''
-      major:
-        description: 'Major release? (yes/no)'
-        required: true
-        default: 'no'
-      prerelease:
-        description: 'Prerelease (ex: rc1). Leave empty if not a pre-release.'
-        required: true
-        default: ''
-
-# Set permissions at the job level.
-permissions: {}
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-
-    steps:
-    - uses: actions/checkout@v2
-      with:
-        fetch-depth: 0
-        persist-credentials: false
-
-    - name: Set up Python
-      uses: actions/setup-python@v2
-      with:
-        python-version: "3.8"
-
-    - name: Install dependencies
-      run: |
-        python -m pip install --upgrade pip
-        pip install --upgrade setuptools tox
-
-    - name: Prepare release PR (minor/patch release)
-      if: github.event.inputs.major == 'no'
-      run: |
-        tox -e prepare-release-pr -- ${{ github.event.inputs.branch }} ${{ github.token }} --prerelease '${{ github.event.inputs.prerelease }}'
-
-    - name: Prepare release PR (major release)
-      if: github.event.inputs.major == 'yes'
-      run: |
-        tox -e prepare-release-pr -- ${{ github.event.inputs.branch }} ${{ github.token }} --major --prerelease '${{ github.event.inputs.prerelease }}'

.github/workflows/release-on-comment.yml

@@ -0,0 +1,31 @@
+# part of our release process, see `release-on-comment.py`
+name: release on comment
+
+on:
+  issues:
+    types: [opened, edited]
+  issue_comment:
+    types: [created, edited]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    if: (github.event.comment && startsWith(github.event.comment.body, '@pytestbot please')) || (github.event.issue && !github.event.comment && startsWith(github.event.issue.body, '@pytestbot please'))
+
+    steps:
+    - uses: actions/checkout@v2
+      with:
+        fetch-depth: 0
+
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: "3.8"
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install --upgrade setuptools tox
+    - name: Prepare release
+      run: |
+        tox -e release-on-comment -- $GITHUB_EVENT_PATH ${{ secrets.chatops }}

.github/workflows/update-plugin-list.yml

@@ -1,48 +0,0 @@
-name: Update Plugin List
-
-on:
-  schedule:
-    # At 00:00 on Sunday.
-    # https://crontab.guru
-    - cron: '0 0 * * 0'
-  workflow_dispatch:
-
-# Set permissions at the job level.
-permissions: {}
-
-jobs:
-  createPullRequest:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      pull-requests: write
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-        with:
-          fetch-depth: 0
-
-      - name: Setup Python
-        uses: actions/setup-python@v2
-        with:
-          python-version: 3.8
-
-      - name: Install dependencies
-        run: |
-          python -m pip install --upgrade pip
-          pip install packaging requests tabulate[widechars]
-
-      - name: Update Plugin List
-        run: python scripts/update-plugin-list.py
-
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@2455e1596942c2902952003bbb574afbbe2ab2e6
-        with:
-          commit-message: '[automated] Update plugin list'
-          author: 'pytest bot <pytestbot@users.noreply.github.com>'
-          branch: update-plugin-list/patch
-          delete-branch: true
-          branch-suffix: short-commit-hash
-          title: '[automated] Update plugin list'
-          body: '[automated] Update plugin list'

.gitignore

@@ -34,7 +34,6 @@ issue/
 env/
 .env/
 .venv/
-/pythonenv*/
 3rdparty/
 .tox
 .cache

.pre-commit-config.yaml

@@ -1,16 +1,16 @@
 repos:
 -   repo: https://github.com/psf/black
-    rev: 21.6b0
+    rev: 19.10b0
     hooks:
     -   id: black
         args: [--safe, --quiet]
 -   repo: https://github.com/asottile/blacken-docs
-    rev: v1.10.0
+    rev: v1.7.0
     hooks:
     -   id: blacken-docs
-        additional_dependencies: [black==20.8b1]
+        additional_dependencies: [black==19.10b0]
 -   repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.0.1
+    rev: v3.1.0
     hooks:
     -   id: trailing-whitespace
     -   id: end-of-file-fixer
@@ -20,8 +20,8 @@ repos:
     -   id: debug-statements
         exclude: _pytest/(debugging|hookspec).py
         language_version: python3
--   repo: https://github.com/PyCQA/flake8
-    rev: 3.9.2
+-   repo: https://gitlab.com/pycqa/flake8
+    rev: 3.8.2
     hooks:
     -   id: flake8
         language_version: python3
@@ -29,37 +29,27 @@ repos:
           - flake8-typing-imports==1.9.0
           - flake8-docstrings==1.5.0
 -   repo: https://github.com/asottile/reorder_python_imports
-    rev: v2.5.0
+    rev: v2.3.0
     hooks:
     -   id: reorder-python-imports
-        args: ['--application-directories=.:src', --py36-plus]
+        args: ['--application-directories=.:src', --py3-plus]
 -   repo: https://github.com/asottile/pyupgrade
-    rev: v2.19.4
+    rev: v2.4.4
     hooks:
     -   id: pyupgrade
-        args: [--py36-plus]
+        args: [--py3-plus]
 -   repo: https://github.com/asottile/setup-cfg-fmt
-    rev: v1.17.0
-    hooks:
-    -   id: setup-cfg-fmt
-        args: [--max-py-version=3.10]
--   repo: https://github.com/pre-commit/pygrep-hooks
     rev: v1.9.0
     hooks:
-    -   id: python-use-type-annotations
+    -   id: setup-cfg-fmt
+        # TODO: when upgrading setup-cfg-fmt this can be removed
+        args: [--max-py-version=3.9]
 -   repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v0.902
+    rev: v0.780  # NOTE: keep this in sync with setup.cfg.
     hooks:
     -   id: mypy
         files: ^(src/|testing/)
         args: []
-        additional_dependencies:
-          - iniconfig>=1.1.0
-          - py>=1.8.2
-          - attrs>=19.2.0
-          - packaging
-          - types-toml
-          - types-pkg_resources
 -   repo: local
     hooks:
     -   id: rst
@@ -90,9 +80,3 @@ repos:
                 xml\.
             )
         types: [python]
-    -   id: py-path-deprecated
-        name: py.path usage is deprecated
-        exclude: docs|src/_pytest/deprecated.py|testing/deprecated_test.py
-        language: pygrep
-        entry: \bpy\.path\.local
-        types: [python]

.travis.yml

@@ -0,0 +1,60 @@
+language: python
+dist: trusty
+python: '3.5.1'
+cache: false
+
+env:
+  global:
+    - PYTEST_ADDOPTS=-vv
+
+# setuptools-scm needs all tags in order to obtain a proper version
+git:
+  depth: false
+
+install:
+  - python -m pip install --upgrade --pre tox
+
+jobs:
+  include:
+    # Coverage for Python 3.5.{0,1} specific code, mostly typing related.
+    - env: TOXENV=py35 PYTEST_COVERAGE=1 PYTEST_ADDOPTS="-k test_raises_cyclic_reference"
+      before_install:
+        # Work around https://github.com/jaraco/zipp/issues/40.
+        - python -m pip install -U 'setuptools>=34.4.0' virtualenv==16.7.9
+
+before_script:
+  - |
+    # Do not (re-)upload coverage with cron runs.
+    if [[ "$TRAVIS_EVENT_TYPE" = cron ]]; then
+      PYTEST_COVERAGE=0
+    fi
+  - |
+    if [[ "$PYTEST_COVERAGE" = 1 ]]; then
+      export COVERAGE_FILE="$PWD/.coverage"
+      export COVERAGE_PROCESS_START="$PWD/.coveragerc"
+      export _PYTEST_TOX_COVERAGE_RUN="coverage run -m"
+      export _PYTEST_TOX_EXTRA_DEP=coverage-enable-subprocess
+    fi
+
+script: tox
+
+after_success:
+  - |
+    if [[ "$PYTEST_COVERAGE" = 1 ]]; then
+      env CODECOV_NAME="$TOXENV-$TRAVIS_OS_NAME" scripts/report-coverage.sh -F Travis
+    fi
+
+notifications:
+  irc:
+    channels:
+      - "chat.freenode.net#pytest"
+    on_success: change
+    on_failure: change
+    skip_join: true
+  email:
+    - pytest-commit@python.org
+
+branches:
+  only:
+    - master
+    - /^\d+\.\d+\.x$/

AUTHORS

@@ -5,7 +5,6 @@ Contributors include::
 
 Aaron Coleman
 Abdeali JK
-Abdelrahman Elbehery
 Abhijeet Kasurde
 Adam Johnson
 Adam Uhlir
@@ -22,9 +21,7 @@ Anders Hovmöller
 Andras Mitzki
 Andras Tim
 Andrea Cimatoribus
-Andreas Motl
 Andreas Zeidler
-Andrew Shapton
 Andrey Paramonov
 Andrzej Klajnert
 Andrzej Ostrowski
@@ -32,18 +29,15 @@ Andy Freeland
 Anthon van der Neut
 Anthony Shaw
 Anthony Sottile
-Anton Grinevich
 Anton Lodder
 Antony Lee
 Arel Cordero
-Ariel Pillemer
 Armin Rigo
 Aron Coyle
 Aron Curzon
 Aviral Verma
 Aviv Palivoda
 Barney Gale
-Ben Gartner
 Ben Webb
 Benjamin Peterson
 Bernard Pratz
@@ -61,14 +55,11 @@ Charles Cloud
 Charles Machalow
 Charnjit SiNGH (CCSJ)
 Chris Lamb
-Chris NeJame
-Chris Rose
 Christian Boelsen
 Christian Fetzer
 Christian Neumüller
 Christian Theunert
 Christian Tismer
-Christine Mecklenborg
 Christoph Buelter
 Christopher Dignam
 Christopher Gilling
@@ -81,7 +72,6 @@ Daniel Grana
 Daniel Hahler
 Daniel Nuri
 Daniel Wandschneider
-Daniele Procida
 Danielle Jenkins
 Daniil Galiev
 Dave Hunt
@@ -97,11 +87,9 @@ Dhiren Serai
 Diego Russo
 Dmitry Dygalo
 Dmitry Pribysh
-Dominic Mortlock
 Duncan Betts
 Edison Gustavo Muenz
 Edoardo Batini
-Edson Tadeu M. Manoel
 Eduardo Schettino
 Eli Boyarski
 Elizaveta Shashkova
@@ -119,7 +107,6 @@ Florian Bruhin
 Florian Dahlitz
 Floris Bruynooghe
 Gabriel Reis
-Garvit Shubham
 Gene Wood
 George Kussumoto
 Georgy Dyuldin
@@ -142,9 +129,7 @@ Ilya Konstantinov
 Ionuț Turturică
 Iwan Briquemont
 Jaap Broekhuizen
-Jakob van Santen
 Jakub Mitoraj
-James Bourbeau
 Jan Balster
 Janne Vanhala
 Jason R. Coombs
@@ -165,11 +150,9 @@ Josh Karpel
 Joshua Bronson
 Jurko Gospodnetić
 Justyna Janczyszyn
-Justice Ndou
 Kale Kundert
 Kamran Ahmad
 Karl O. Pinc
-Karthikeyan Singaravelan
 Katarzyna Jachim
 Katarzyna Król
 Katerina Koukiou
@@ -212,7 +195,6 @@ Matthias Hafner
 Maxim Filipenko
 Maximilian Cosmo Sitter
 mbyt
-Mickey Pashov
 Michael Aquilina
 Michael Birtwell
 Michael Droettboom
@@ -233,7 +215,6 @@ Nicholas Murphy
 Niclas Olofsson
 Nicolas Delaby
 Nikolay Kondratyev
-Olga Matoula
 Oleg Pidsadnyi
 Oleg Sushchenko
 Oliver Bestwalter
@@ -241,20 +222,16 @@ Omar Kohl
 Omer Hadari
 Ondřej Súkup
 Oscar Benjamin
-Parth Patel
 Patrick Hayes
 Pauli Virtanen
 Pavel Karateev
 Paweł Adamczak
 Pedro Algarvio
-Petter Strandmark
 Philipp Loose
 Pieter Mulder
 Piotr Banaszkiewicz
 Piotr Helm
-Prakhar Gurunani
 Prashant Anand
-Prashant Sharma
 Pulkit Goyal
 Punyashloka Biswal
 Quentin Pradet
@@ -276,17 +253,13 @@ Ross Lawley
 Ruaridh Williamson
 Russel Winder
 Ryan Wooden
-Saiprasad Kale
 Samuel Dion-Girardeau
 Samuel Searles-Bryant
 Samuele Pedroni
-Sanket Duthade
 Sankt Petersbug
 Segev Finer
 Serhii Mozghovyi
 Seth Junot
-Shantanu Jain
-Shubham Adep
 Simon Gomizelj
 Simon Kerr
 Skylar Downes
@@ -301,7 +274,6 @@ Sven-Hendrik Haase
 Sylvain Marié
 Tadek Teleżyński
 Takafumi Arakaki
-Tanvi Mehta
 Tarcisio Fischer
 Tareq Alayan
 Ted Xiao
@@ -337,6 +309,4 @@ Xuan Luong
 Xuecong Liao
 Yoav Caspi
 Zac Hatfield-Dodds
-Zachary Kneupper
 Zoltán Máté
-Zsolt Cserna

CHANGELOG.rst

@@ -4,4 +4,4 @@ Changelog
 
 The pytest CHANGELOG is located `here <https://docs.pytest.org/en/stable/changelog.html>`__.
 
-The source document can be found at: https://github.com/pytest-dev/pytest/blob/main/doc/en/changelog.rst
+The source document can be found at: https://github.com/pytest-dev/pytest/blob/master/doc/en/changelog.rst

CONTRIBUTING.rst

@@ -160,7 +160,7 @@ the following:
 
 - an issue tracker for bug reports and enhancement requests.
 
-- a `changelog <https://keepachangelog.com/>`_.
+- a `changelog <http://keepachangelog.com/>`_.
 
 If no contributor strongly objects and two agree, the repository can then be
 transferred to the ``pytest-dev`` organisation.
@@ -234,9 +234,9 @@ Here is a simple overview, with pytest-specific bits:
 
     $ git clone git@github.com:YOUR_GITHUB_USERNAME/pytest.git
     $ cd pytest
-    # now, create your own branch off "main":
+    # now, create your own branch off "master":
 
-        $ git checkout -b your-bugfix-branch-name main
+        $ git checkout -b your-bugfix-branch-name master
 
    Given we have "major.minor.micro" version numbers, bug fixes will usually
    be released in micro releases whereas features will be released in
@@ -259,7 +259,7 @@ Here is a simple overview, with pytest-specific bits:
 
    Tox is used to run all the tests and will automatically setup virtualenvs
    to run the tests in.
-   (will implicitly use https://virtualenv.pypa.io/en/latest/)::
+   (will implicitly use http://www.virtualenv.org/en/latest/)::
 
     $ pip install tox
 
@@ -299,6 +299,12 @@ Here is a simple overview, with pytest-specific bits:
 
        $ pytest testing/test_config.py
 
+
+#. Commit and push once your tests pass and you are happy with your change(s)::
+
+    $ git commit -a -m "<commit message>"
+    $ git push -u
+
 #. Create a new changelog entry in ``changelog``. The file should be named ``<issueid>.<type>.rst``,
    where *issueid* is the number of the issue related to the change and *type* is one of
    ``feature``, ``improvement``, ``bugfix``, ``doc``, ``deprecation``, ``breaking``, ``vendor``
@@ -307,37 +313,32 @@ Here is a simple overview, with pytest-specific bits:
 
 #. Add yourself to ``AUTHORS`` file if not there yet, in alphabetical order.
 
-#. Commit and push once your tests pass and you are happy with your change(s)::
-
-    $ git commit -a -m "<commit message>"
-    $ git push -u
-
 #. Finally, submit a pull request through the GitHub website using this data::
 
     head-fork: YOUR_GITHUB_USERNAME/pytest
     compare: your-branch-name
 
     base-fork: pytest-dev/pytest
-    base: main
+    base: master
 
 
 Writing Tests
 ~~~~~~~~~~~~~
 
-Writing tests for plugins or for pytest itself is often done using the `pytester fixture <https://docs.pytest.org/en/stable/reference.html#pytester>`_, as a "black-box" test.
+Writing tests for plugins or for pytest itself is often done using the `testdir fixture <https://docs.pytest.org/en/stable/reference.html#testdir>`_, as a "black-box" test.
 
 For example, to ensure a simple test passes you can write:
 
 .. code-block:: python
 
-    def test_true_assertion(pytester):
-        pytester.makepyfile(
+    def test_true_assertion(testdir):
+        testdir.makepyfile(
             """
             def test_foo():
                 assert True
         """
         )
-        result = pytester.runpytest()
+        result = testdir.runpytest()
         result.assert_outcomes(failed=0, passed=1)
 
 
@@ -346,14 +347,14 @@ Alternatively, it is possible to make checks based on the actual output of the t
 
 .. code-block:: python
 
-    def test_true_assertion(pytester):
-        pytester.makepyfile(
+    def test_true_assertion(testdir):
+        testdir.makepyfile(
             """
             def test_foo():
                 assert False
         """
         )
-        result = pytester.runpytest()
+        result = testdir.runpytest()
         result.stdout.fnmatch_lines(["*assert False*", "*1 failed*"])
 
 When choosing a file where to write a new test, take a look at the existing files and see if there's
@@ -387,15 +388,15 @@ Suppose for example that the latest release was 1.2.3, and you want to include
 a bug fix in 1.2.4 (check https://github.com/pytest-dev/pytest/releases for the
 actual latest release). The procedure for this is:
 
-#. First, make sure the bug is fixed the ``main`` branch, with a regular pull
+#. First, make sure the bug is fixed the ``master`` branch, with a regular pull
    request, as described above. An exception to this is if the bug fix is not
-   applicable to ``main`` anymore.
+   applicable to ``master`` anymore.
 
-#. ``git checkout origin/1.2.x -b backport-XXXX`` # use the main PR number here
+#. ``git checkout origin/1.2.x -b backport-XXXX`` # use the master PR number here
 
 #. Locate the merge commit on the PR, in the *merged* message, for example:
 
-    nicoddemus merged commit 0f8b462 into pytest-dev:main
+    nicoddemus merged commit 0f8b462 into pytest-dev:master
 
 #. ``git cherry-pick -x -m1 REVISION`` # use the revision you found above (``0f8b462``).
 
@@ -408,8 +409,8 @@ actual latest release). The procedure for this is:
 Who does the backporting
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-As mentioned above, bugs should first be fixed on ``main`` (except in rare occasions
-that a bug only happens in a previous release). So, who should do the backport procedure described
+As mentioned above, bugs should first be fixed on ``master`` (except in rare occasions
+that a bug only happens in a previous release). So who should do the backport procedure described
 above?
 
 1. If the bug was fixed by a core developer, it is the main responsibility of that core developer
@@ -417,8 +418,8 @@ above?
 2. However, often the merge is done by another maintainer, in which case it is nice of them to
    do the backport procedure if they have the time.
 3. For bugs submitted by non-maintainers, it is expected that a core developer will to do
-   the backport, normally the one that merged the PR on ``main``.
-4. If a non-maintainers notices a bug which is fixed on ``main`` but has not been backported
+   the backport, normally the one that merged the PR on ``master``.
+4. If a non-maintainers notices a bug which is fixed on ``master`` but has not been backported
    (due to maintainers forgetting to apply the *needs backport* label, or just plain missing it),
    they are also welcome to open a PR with the backport. The procedure is simple and really
    helps with the maintenance of the project.
@@ -447,7 +448,7 @@ can always reopen the issue/pull request in their own time later if it makes sen
 When to close
 ~~~~~~~~~~~~~
 
-Here are a few general rules the maintainers use deciding when to close issues/PRs because
+Here are a few general rules the maintainers use to decide when to close issues/PRs because
 of lack of inactivity:
 
 * Issues labeled ``question`` or ``needs information``: closed after 14 days inactive.
@@ -459,15 +460,15 @@ The above are **not hard rules**, but merely **guidelines**, and can be (and oft
 Closing pull requests
 ~~~~~~~~~~~~~~~~~~~~~
 
-When closing a Pull Request, it needs to be acknowledging the time, effort, and interest demonstrated by the person which submitted it. As mentioned previously, it is not the intent of the team to dismiss a stalled pull request entirely but to merely to clear up our queue, so a message like the one below is warranted when closing a pull request that went stale:
+When closing a Pull Request, it needs to be acknowledge the time, effort, and interest demonstrated by the person which submitted it. As mentioned previously, it is not the intent of the team to dismiss stalled pull request entirely but to merely to clear up our queue, so a message like the one below is warranted when closing a pull request that went stale:
 
     Hi <contributor>,
 
-    First of all, we would like to thank you for your time and effort on working on this, the pytest team deeply appreciates it.
+    First of all we would like to thank you for your time and effort on working on this, the pytest team deeply appreciates it.
 
     We noticed it has been awhile since you have updated this PR, however. pytest is a high activity project, with many issues/PRs being opened daily, so it is hard for us maintainers to track which PRs are ready for merging, for review, or need more attention.
 
-    So for those reasons we, think it is best to close the PR for now, but with the only intention to clean up our queue, it is by no means a rejection of your changes. We still encourage you to re-open this PR (it is just a click of a button away) when you are ready to get back to it.
+    So for those reasons we think it is best to close the PR for now, but with the only intention to cleanup our queue, it is by no means a rejection of your changes. We still encourage you to re-open this PR (it is just a click of a button away) when you are ready to get back to it.
 
     Again we appreciate your time for working on this, and hope you might get back to this at a later time!
 

LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2004-2021 Holger Krekel and others
+Copyright (c) 2004-2020 Holger Krekel and others
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of
 this software and associated documentation files (the "Software"), to deal in

README.rst

@@ -1,7 +1,6 @@
-.. image:: https://github.com/pytest-dev/pytest/raw/main/doc/en/img/pytest_logo_curves.svg
+.. image:: https://docs.pytest.org/en/stable/_static/pytest1.png
    :target: https://docs.pytest.org/en/stable/
    :align: center
-   :height: 200
    :alt: pytest
 
 
@@ -16,17 +15,16 @@
 .. image:: https://img.shields.io/pypi/pyversions/pytest.svg
     :target: https://pypi.org/project/pytest/
 
-.. image:: https://codecov.io/gh/pytest-dev/pytest/branch/main/graph/badge.svg
+.. image:: https://codecov.io/gh/pytest-dev/pytest/branch/master/graph/badge.svg
     :target: https://codecov.io/gh/pytest-dev/pytest
     :alt: Code coverage Status
 
+.. image:: https://travis-ci.org/pytest-dev/pytest.svg?branch=master
+    :target: https://travis-ci.org/pytest-dev/pytest
+
 .. image:: https://github.com/pytest-dev/pytest/workflows/main/badge.svg
     :target: https://github.com/pytest-dev/pytest/actions?query=workflow%3Amain
 
-.. image:: https://results.pre-commit.ci/badge/github/pytest-dev/pytest/main.svg
-   :target: https://results.pre-commit.ci/latest/github/pytest-dev/pytest/main
-   :alt: pre-commit.ci status
-
 .. image:: https://img.shields.io/badge/code%20style-black-000000.svg
     :target: https://github.com/psf/black
 
@@ -91,9 +89,9 @@ Features
 - Can run `unittest <https://docs.pytest.org/en/stable/unittest.html>`_ (or trial),
   `nose <https://docs.pytest.org/en/stable/nose.html>`_ test suites out of the box
 
-- Python 3.6+ and PyPy3
+- Python 3.5+ and PyPy3
 
-- Rich plugin architecture, with over 850+ `external plugins <https://docs.pytest.org/en/latest/reference/plugin_list.html>`_ and thriving community
+- Rich plugin architecture, with over 850+ `external plugins <http://plugincompat.herokuapp.com>`_ and thriving community
 
 
 Documentation
@@ -151,8 +149,8 @@ Tidelift will coordinate the fix and disclosure.
 License
 -------
 
-Copyright Holger Krekel and others, 2004-2021.
+Copyright Holger Krekel and others, 2004-2020.
 
 Distributed under the terms of the `MIT`_ license, pytest is free and open source software.
 
-.. _`MIT`: https://github.com/pytest-dev/pytest/blob/main/LICENSE
+.. _`MIT`: https://github.com/pytest-dev/pytest/blob/master/LICENSE

RELEASING.rst

@@ -14,89 +14,59 @@ Preparing: Automatic Method
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 We have developed an automated workflow for releases, that uses GitHub workflows and is triggered
-by `manually running <https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow>`__
-the `prepare-release-pr workflow <https://github.com/pytest-dev/pytest/actions/workflows/prepare-release-pr.yml>`__
-on GitHub Actions.
+by opening an issue.
 
-The automation will decide the new version number based on the following criteria:
+Bug-fix releases
+^^^^^^^^^^^^^^^^
 
-- If the "major release" input is set to "yes", release a new major release
-  (e.g. 7.0.0 -> 8.0.0)
-- If there are any ``.feature.rst`` or ``.breaking.rst`` files in the
-  ``changelog`` directory, release a new minor release (e.g. 7.0.0 -> 7.1.0)
-- Otherwise, release a bugfix release (e.g. 7.0.0 -> 7.0.1)
-- If the "prerelease" input is set, append the string to the version number
-  (e.g. 7.0.0 -> 8.0.0rc1), if "major" is set, and "prerelease" is set to `rc1`)
+A bug-fix release is always done from a maintenance branch, so for example to release bug-fix
+``5.1.2``, open a new issue and add this comment to the body::
 
-Bug-fix and minor releases
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+    @pytestbot please prepare release from 5.1.x
 
-Bug-fix and minor releases are always done from a maintenance branch. First,
-consider double-checking the ``changelog`` directory to see if there are any
-breaking changes or new features.
+Where ``5.1.x`` is the maintenance branch for the ``5.1`` series.
 
-For a new minor release, first create a new maintenance branch from ``main``::
+The automated workflow will publish a PR for a branch ``release-5.1.2``
+and notify it as a comment in the issue.
 
-     git fetch --all
-     git branch 7.1.x upstream/main
-     git push upstream 7.1.x
-
-Then, trigger the workflow with the following inputs:
-
-- branch: **7.1.x**
-- major release: **no**
-- prerelease: empty
-
-Or via the commandline using `GitHub's cli <https://github.com/cli/cli>`__::
-
-    gh workflow run prepare-release-pr.yml -f branch=7.1.x -f major=no -f prerelease=
-
-Where ``7.1.x`` is the maintenance branch for the ``7.1`` series. The automated
-workflow will publish a PR for a branch ``release-7.1.0``.
-
-Similarly, for a bug-fix release, use the existing maintenance branch and
-trigger the workflow with e.g. ``branch: 7.0.x`` to get a new ``release-7.0.1``
-PR.
-
-Major releases
+Minor releases
 ^^^^^^^^^^^^^^
 
-1. Create a new maintenance branch from ``main``::
+1. Create a new maintenance branch from ``master``::
 
         git fetch --all
-        git branch 8.0.x upstream/main
-        git push upstream 8.0.x
+        git branch 5.2.x upstream/master
+        git push upstream 5.2.x
 
-2. Trigger the workflow with the following inputs:
+2. Open a new issue and add this comment to the body::
 
-   - branch: **8.0.x**
-   - major release: **yes**
-   - prerelease: empty
+    @pytestbot please prepare release from 5.2.x
 
-Or via the commandline::
+The automated workflow will publish a PR for a branch ``release-5.2.0`` and
+notify it as a comment in the issue.
 
-    gh workflow run prepare-release-pr.yml -f branch=8.0.x -f major=yes -f prerelease=
+Major and release candidates
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The automated workflow will publish a PR for a branch ``release-8.0.0``.
+1. Create a new maintenance branch from ``master``::
+
+        git fetch --all
+        git branch 6.0.x upstream/master
+        git push upstream 6.0.x
+
+2. For a **major release**, open a new issue and add this comment in the body::
+
+        @pytestbot please prepare major release from 6.0.x
+
+   For a **release candidate**, the comment must be (TODO: `#7551 <https://github.com/pytest-dev/pytest/issues/7551>`__)::
+
+        @pytestbot please prepare release candidate from 6.0.x
+
+The automated workflow will publish a PR for a branch ``release-6.0.0`` and
+notify it as a comment in the issue.
 
 At this point on, this follows the same workflow as other maintenance branches: bug-fixes are merged
-into ``main`` and ported back to the maintenance branch, even for release candidates.
-
-Release candidates
-^^^^^^^^^^^^^^^^^^
-
-To release a release candidate, set the "prerelease" input to the version number
-suffix to use. To release a ``8.0.0rc1``, proceed like under "major releases", but set:
-
-- branch: 8.0.x
-- major release: yes
-- prerelease: **rc1**
-
-Or via the commandline::
-
-    gh workflow run prepare-release-pr.yml -f branch=8.0.x -f major=yes -f prerelease=rc1
-
-The automated workflow will publish a PR for a branch ``release-8.0.0rc1``.
+into ``master`` and ported back to the maintenance branch, even for release candidates.
 
 **A note about release candidates**
 
@@ -113,7 +83,7 @@ to be executed on that platform.
 To release a version ``MAJOR.MINOR.PATCH``, follow these steps:
 
 #. For major and minor releases, create a new branch ``MAJOR.MINOR.x`` from
-   ``upstream/main`` and push it to ``upstream``.
+   ``upstream/master`` and push it to ``upstream``.
 
 #. Create a branch ``release-MAJOR.MINOR.PATCH`` from the ``MAJOR.MINOR.x`` branch.
 
@@ -144,22 +114,14 @@ Both automatic and manual processes described above follow the same steps from t
 
 #. Merge the PR.
 
-#. Cherry-pick the CHANGELOG / announce files to the ``main`` branch::
+#. Cherry-pick the CHANGELOG / announce files to the ``master`` branch::
 
        git fetch --all --prune
-       git checkout upstream/main -b cherry-pick-release
+       git checkout origin/master -b cherry-pick-release
        git cherry-pick -x -m1 upstream/MAJOR.MINOR.x
 
 #. Open a PR for ``cherry-pick-release`` and merge it once CI passes. No need to wait for approvals if there were no conflicts on the previous step.
 
-#. For major and minor releases, tag the release cherry-pick merge commit in main with
-   a dev tag for the next feature release::
-
-       git checkout main
-       git pull
-       git tag MAJOR.{MINOR+1}.0.dev0
-       git push git@github.com:pytest-dev/pytest.git MAJOR.{MINOR+1}.0.dev0
-
 #. Send an email announcement with the contents from::
 
      doc/en/announce/release-<VERSION>.rst

TIDELIFT.rst

@@ -25,7 +25,6 @@ The current list of contributors receiving funding are:
 
 * `@asottile`_
 * `@nicoddemus`_
-* `@The-Compiler`_
 
 Contributors interested in receiving a part of the funds just need to submit a PR adding their
 name to the list. Contributors that want to stop receiving the funds should also submit a PR
@@ -57,4 +56,3 @@ funds. Just drop a line to one of the `@pytest-dev/tidelift-admins`_ or use the
 
 .. _`@asottile`: https://github.com/asottile
 .. _`@nicoddemus`: https://github.com/nicoddemus
-.. _`@The-Compiler`: https://github.com/The-Compiler

bench/unit_test.py

@@ -1,13 +0,0 @@
-from unittest import TestCase  # noqa: F401
-
-for i in range(15000):
-    exec(
-        f"""
-class Test{i}(TestCase):
-    @classmethod
-    def setUpClass(cls): pass
-    def test_1(self): pass
-    def test_2(self): pass
-    def test_3(self): pass
-"""
-    )

bench/xunit.py

@@ -1,11 +0,0 @@
-for i in range(5000):
-    exec(
-        f"""
-class Test{i}:
-    @classmethod
-    def setup_class(cls): pass
-    def test_1(self): pass
-    def test_2(self): pass
-    def test_3(self): pass
-"""
-    )

changelog/5105.doc.rst

@@ -1 +0,0 @@
-Add automatically generated :ref:`plugin-list`. The list is updated on a periodic schedule.

changelog/7259.feature.rst

@@ -1,7 +0,0 @@
-Added :meth:`cache.mkdir() <pytest.Cache.mkdir>`, which is similar to the existing :meth:`cache.makedir() <pytest.Cache.makedir>`,
-but returns a :class:`pathlib.Path` instead of a legacy ``py.path.local``.
-
-Added a ``paths`` type to :meth:`parser.addini() <pytest.Parser.addini>`,
-as in ``parser.addini("mypaths", "my paths", type="paths")``,
-which is similar to the existing ``pathlist``,
-but returns a list of :class:`pathlib.Path` instead of legacy ``py.path.local``.

changelog/7469.deprecation.rst

@@ -1,12 +0,0 @@
-Directly constructing the following classes is now deprecated:
-
-- ``_pytest.mark.structures.Mark``
-- ``_pytest.mark.structures.MarkDecorator``
-- ``_pytest.mark.structures.MarkGenerator``
-- ``_pytest.python.Metafunc``
-- ``_pytest.runner.CallInfo``
-- ``_pytest._code.ExceptionInfo``
-- ``_pytest.config.argparsing.Parser``
-- ``_pytest.config.argparsing.OptionGroup``
-
-These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.

changelog/7469.feature.rst

@@ -1,19 +0,0 @@
-The types of objects used in pytest's API are now exported so they may be used in type annotations.
-
-The newly-exported types are:
-
-- ``pytest.Config`` for :class:`Config <pytest.Config>`.
-- ``pytest.Mark`` for :class:`marks <pytest.Mark>`.
-- ``pytest.MarkDecorator`` for :class:`mark decorators <pytest.MarkDecorator>`.
-- ``pytest.MarkGenerator`` for the :class:`pytest.mark <pytest.MarkGenerator>` singleton.
-- ``pytest.Metafunc`` for the :class:`metafunc <pytest.MarkGenerator>` argument to the :func:`pytest_generate_tests <pytest.hookspec.pytest_generate_tests>` hook.
-- ``pytest.CallInfo`` for the :class:`CallInfo <pytest.CallInfo>` type passed to various hooks.
-- ``pytest.PytestPluginManager`` for :class:`PytestPluginManager <pytest.PytestPluginManager>`.
-- ``pytest.ExceptionInfo`` for the :class:`ExceptionInfo <pytest.ExceptionInfo>` type returned from :func:`pytest.raises` and passed to various hooks.
-- ``pytest.Parser`` for the :class:`Parser <pytest.Parser>` type passed to the :func:`pytest_addoption <pytest.hookspec.pytest_addoption>` hook.
-- ``pytest.OptionGroup`` for the :class:`OptionGroup <pytest.OptionGroup>` type returned from the :func:`parser.addgroup <pytest.Parser.getgroup>` method.
-
-Constructing them directly is not supported; they are only meant for use in type annotations.
-Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.
-
-Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.

changelog/7856.feature.rst

@@ -1,2 +0,0 @@
-:ref:`--import-mode=importlib <import-modes>` now works with features that
-depend on modules being on :py:data:`sys.modules`, such as :mod:`pickle` and :mod:`dataclasses`.

changelog/8061.bugfix.rst

@@ -1 +0,0 @@
-Fixed failing staticmethod test cases if they are inherited from a parent test class.

changelog/8144.feature.rst

@@ -1,7 +0,0 @@
-The following hooks now receive an additional ``pathlib.Path`` argument, equivalent to an existing ``py.path.local`` argument:
-
-- :func:`pytest_ignore_collect <_pytest.hookspec.pytest_ignore_collect>` - The ``fspath`` parameter (equivalent to existing ``path`` parameter).
-- :func:`pytest_collect_file <_pytest.hookspec.pytest_collect_file>` - The ``fspath`` parameter (equivalent to existing ``path`` parameter).
-- :func:`pytest_pycollect_makemodule <_pytest.hookspec.pytest_pycollect_makemodule>` - The ``fspath`` parameter (equivalent to existing ``path`` parameter).
-- :func:`pytest_report_header <_pytest.hookspec.pytest_report_header>` - The ``startpath`` parameter (equivalent to existing ``startdir`` parameter).
-- :func:`pytest_report_collectionfinish <_pytest.hookspec.pytest_report_collectionfinish>` - The ``startpath`` parameter (equivalent to existing ``startdir`` parameter).

changelog/8174.trivial.rst

@@ -1,6 +0,0 @@
-The following changes have been made to internal pytest types/functions:
-
-- The ``path`` property of ``_pytest.code.Code`` returns ``Path`` instead of ``py.path.local``.
-- The ``path`` property of ``_pytest.code.TracebackEntry`` returns ``Path`` instead of ``py.path.local``.
-- The ``_pytest.code.getfslineno()`` function returns ``Path`` instead of ``py.path.local``.
-- The ``_pytest.python.path_matches_patterns()`` function takes ``Path`` instead of ``py.path.local``.

changelog/8192.bugfix.rst

@@ -1,3 +0,0 @@
-``testdir.makefile`` now silently accepts values which don't start with ``.`` to maintain backward compatibility with older pytest versions.
-
-``pytester.makefile`` now issues a clearer error if the ``.`` is missing in the ``ext`` argument.

changelog/8242.deprecation.rst

@@ -1,7 +0,0 @@
-Raising :class:`unittest.SkipTest` to skip collection of tests during the
-pytest collection phase is deprecated. Use :func:`pytest.skip` instead.
-
-Note: This deprecation only relates to using `unittest.SkipTest` during test
-collection. You are probably not doing that. Ordinary usage of
-:class:`unittest.SkipTest` / :meth:`unittest.TestCase.skipTest` /
-:func:`unittest.skip` in unittest test cases is fully supported.

changelog/8246.breaking.rst

@@ -1 +0,0 @@
-``--version`` now writes version information to ``stdout`` rather than ``stderr``.

changelog/8248.trivial.rst

@@ -1 +0,0 @@
-Internal Restructure: let python.PyObjMixing inherit from nodes.Node to carry over typing information.

changelog/8251.deprecation.rst

@@ -1 +0,0 @@
-Deprecate ``Node.fspath`` as we plan to move off `py.path.local <https://py.readthedocs.io/en/latest/path.html>`__ and switch to :mod:``pathlib``.

changelog/8251.feature.rst

@@ -1 +0,0 @@
-Implement ``Node.path`` as a ``pathlib.Path``.

changelog/8258.bugfix.rst

@@ -1,3 +0,0 @@
-Fixed issue where pytest's ``faulthandler`` support would not dump traceback on crashes
-if the :mod:`faulthandler` module was already enabled during pytest startup (using
-``python -X dev -m pytest`` for example).

changelog/8315.deprecation.rst

@@ -1,5 +0,0 @@
-Several behaviors of :meth:`Parser.addoption <pytest.Parser.addoption>` are now
-scheduled for removal in pytest 7 (deprecated since pytest 2.4.0):
-
-- ``parser.addoption(..., help=".. %default ..")`` - use ``%(default)s`` instead.
-- ``parser.addoption(..., type="int/string/float/complex")`` - use ``type=int`` etc. instead.

changelog/8317.bugfix.rst

@@ -1 +0,0 @@
-Fixed an issue where illegal directory characters derived from ``getpass.getuser()`` raised an ``OSError``.

changelog/8335.improvement.rst

@@ -1,10 +0,0 @@
-Improved :func:`pytest.approx` assertion messages for sequences of numbers.
-
-The assertion messages now dumps a table with the index and the error of each diff.
-Example::
-
-    >       assert [1, 2, 3, 4] == pytest.approx([1, 3, 3, 5])
-    E       assert comparison failed for 2 values:
-    E         Index | Obtained | Expected
-    E         1     | 2        | 3 +- 3.0e-06
-    E         3     | 4        | 5 +- 5.0e-06

changelog/8337.doc.rst

@@ -1 +0,0 @@
-Recommend `numpy.testing <https://numpy.org/doc/stable/reference/routines.testing.html>`__ module on :func:`pytest.approx` documentation.

changelog/8367.bugfix.rst

@@ -1 +0,0 @@
-Fix ``Class.from_parent`` so it forwards extra keyword arguments to the constructor.

changelog/8384.bugfix.rst

@@ -1 +0,0 @@
-The ``@pytest.mark.skip`` decorator now correctly handles its arguments. When the ``reason`` argument is accidentally given both positional and as a keyword (e.g. because it was confused with ``skipif``), a ``TypeError`` now occurs. Before, such tests were silently skipped, and the positional argument ignored. Additionally, ``reason`` is now documented correctly as positional or keyword (rather than keyword-only).

changelog/8394.bugfix.rst

@@ -1 +0,0 @@
-Use private names for internal fixtures that handle classic setup/teardown so that they don't show up with the default ``--fixtures`` invocation (but they still show up with ``--fixtures -v``).

changelog/8403.improvement.rst

@@ -1,5 +0,0 @@
-By default, pytest will truncate long strings in assert errors so they don't clutter the output too much,
-currently at ``240`` characters by default.
-
-However, in some cases the longer output helps, or is even crucial, to diagnose a failure. Using ``-v`` will
-now increase the truncation threshold to ``2400`` characters, and ``-vv`` or higher will disable truncation entirely.

changelog/8411.trivial.rst

@@ -1 +0,0 @@
-Assert the outcomes for the issue 518 test and fix the test.

changelog/8421.feature.rst

@@ -1 +0,0 @@
-:func:`pytest.approx` now works on :class:`~decimal.Decimal` within mappings/dicts and sequences/lists.

changelog/8447.deprecation.rst

@@ -1,4 +0,0 @@
-Defining a custom pytest node type which is both an item and a collector now issues a warning.
-It was never sanely supported and triggers hard to debug errors.
-
-Instead, a separate collector node should be used, which collects the item. See :ref:`non-python tests` for an example.

changelog/8456.bugfix.rst

@@ -1 +0,0 @@
-The :confval:`required_plugins` config option now works correctly when pre-releases of plugins are installed, rather than falsely claiming that those plugins aren't installed at all.

changelog/8464.bugfix.rst

@@ -1 +0,0 @@
-``-c <config file>`` now also properly defines ``rootdir`` as the directory that contains ``<config file>``.

changelog/8494.feature.rst

@@ -1 +0,0 @@
-Python 3.10 is now supported.

changelog/8503.trivial.rst

@@ -1,4 +0,0 @@
-:meth:`pytest.MonkeyPatch.syspath_prepend` no longer fails when
-``setuptools`` is not installed.
-It now only calls :func:`pkg_resources.fixup_namespace_packages` if
-``pkg_resources`` was previously imported, because it is not needed otherwise.

changelog/8509.improvement.rst

@@ -1,5 +0,0 @@
-Fixed issue where `TestCase.setUpClass` is not called when a test has `/` in its name since pytest 6.2.0.
-
-This refers to the path part in pytest node IDs, e.g. `TestClass::test_it` in the node ID `tests/test_file.py::TestClass::test_it`.
-
-Now, instead of assuming that the test name does not contain ``/``, it is assumed that test path does not contain ``::``. We plan to hopefully make both of these work in the future.

changelog/8548.bugfix.rst

@@ -1 +0,0 @@
-Introduce fix to handle precision width in ``log-cli-format`` in turn to fix output coloring for certain formats.

changelog/8606.feature.rst

@@ -1,5 +0,0 @@
-pytest invocations with ``--fixtures-per-test`` and ``--fixtures`` have been enabled with:
-
-- Fixture location path printed with the fixture name.
-- First section of the fixture's docstring printed under the fixture name.
-- Whole of fixture's docstring printed under the fixture name using ``--verbose`` option.

changelog/8645.improvement.rst

@@ -1,4 +0,0 @@
-Reducing confusion from `pytest.warns(None)` by:
-
-- Allowing no arguments to be passed in order to catch any exception (no argument defaults to `Warning`).
-- Emit a deprecation warning if passed `None`.

changelog/8655.doc.rst

@@ -1 +0,0 @@
-Help text for ``--pdbcls`` more accurately reflects the option's behavior.

changelog/8761.feature.rst

@@ -1 +0,0 @@
-New :ref:`version-tuple` attribute, which makes it simpler for users to do something depending on the pytest version (such as declaring hooks which are introduced in later versions).

doc/en/_templates/globaltoc.html

@@ -1,19 +1,12 @@
-<h3>Contents</h3>
+<h3><a href="{{ pathto(master_doc) }}">{{ _('Table Of Contents') }}</a></h3>
 
 <ul>
   <li><a href="{{ pathto('index') }}">Home</a></li>
-
-  <li><a href="{{ pathto('getting-started') }}">Get started</a></li>
-  <li><a href="{{ pathto('how-to/index') }}">How-to guides</a></li>
-  <li><a href="{{ pathto('reference/index') }}">Reference guides</a></li>
-  <li><a href="{{ pathto('explanation/index') }}">Explanation</a></li>
-  <li><a href="{{ pathto('contents') }}">Complete table of contents</a></li>
-  <li><a href="{{ pathto('example/index') }}">Library of examples</a></li>
-</ul>
-
-<h3>About the project</h3>
-
-<ul>
+  <li><a href="{{ pathto('getting-started') }}">Install</a></li>
+  <li><a href="{{ pathto('contents') }}">Contents</a></li>
+  <li><a href="{{ pathto('reference') }}">API Reference</a></li>
+  <li><a href="{{ pathto('example/index') }}">Examples</a></li>
+  <li><a href="{{ pathto('customize') }}">Customize</a></li>
   <li><a href="{{ pathto('changelog') }}">Changelog</a></li>
   <li><a href="{{ pathto('contributing') }}">Contributing</a></li>
   <li><a href="{{ pathto('backwards-compatibility') }}">Backwards Compatibility</a></li>

doc/en/_templates/links.html

@@ -2,6 +2,7 @@
 <ul>
   <li><a href="https://pypi.org/project/pytest/">pytest @ PyPI</a></li>
   <li><a href="https://github.com/pytest-dev/pytest/">pytest @ GitHub</a></li>
+  <li><a href="http://plugincompat.herokuapp.com/">3rd party plugins</a></li>
   <li><a href="https://github.com/pytest-dev/pytest/issues">Issue Tracker</a></li>
   <li><a href="https://media.readthedocs.org/pdf/pytest/latest/pytest.pdf">PDF Documentation</a>
 </ul>

doc/en/announce/index.rst

@@ -6,11 +6,6 @@ Release announcements
    :maxdepth: 2
 
 
-   release-6.2.4
-   release-6.2.3
-   release-6.2.2
-   release-6.2.1
-   release-6.2.0
    release-6.1.2
    release-6.1.1
    release-6.1.0

doc/en/announce/release-2.1.0.rst

@@ -24,7 +24,7 @@ If you want to install or upgrade pytest, just type one of::
     easy_install -U pytest
 
 best,
-holger krekel / https://merlinux.eu/
+holger krekel / http://merlinux.eu
 
 Changes between 2.0.3 and 2.1.0
 ----------------------------------------------

doc/en/announce/release-2.1.1.rst

@@ -20,7 +20,7 @@ If you want to install or upgrade pytest, just type one of::
     easy_install -U pytest
 
 best,
-holger krekel / https://merlinux.eu/
+holger krekel / http://merlinux.eu
 
 Changes between 2.1.0 and 2.1.1
 ----------------------------------------------

doc/en/announce/release-2.1.2.rst

@@ -19,7 +19,7 @@ If you want to install or upgrade pytest, just type one of::
     easy_install -U pytest
 
 best,
-holger krekel / https://merlinux.eu/
+holger krekel / http://merlinux.eu
 
 Changes between 2.1.1 and 2.1.2
 ----------------------------------------

doc/en/announce/release-6.2.0.rst

@@ -1,76 +0,0 @@
-pytest-6.2.0
-=======================================
-
-The pytest team is proud to announce the 6.2.0 release!
-
-This release contains new features, improvements, bug fixes, and breaking changes, so users
-are encouraged to take a look at the CHANGELOG carefully:
-
-    https://docs.pytest.org/en/stable/changelog.html
-
-For complete documentation, please visit:
-
-    https://docs.pytest.org/en/stable/
-
-As usual, you can upgrade from PyPI via:
-
-    pip install -U pytest
-
-Thanks to all of the contributors to this release:
-
-* Adam Johnson
-* Albert Villanova del Moral
-* Anthony Sottile
-* Anton
-* Ariel Pillemer
-* Bruno Oliveira
-* Charles Aracil
-* Christine M
-* Christine Mecklenborg
-* Cserna Zsolt
-* Dominic Mortlock
-* Emiel van de Laar
-* Florian Bruhin
-* Garvit Shubham
-* Gustavo Camargo
-* Hugo Martins
-* Hugo van Kemenade
-* Jakob van Santen
-* Josias Aurel
-* Jürgen Gmach
-* Karthikeyan Singaravelan
-* Katarzyna
-* Kyle Altendorf
-* Manuel Mariñez
-* Matthew Hughes
-* Matthias Gabriel
-* Max Voitko
-* Maximilian Cosmo Sitter
-* Mikhail Fesenko
-* Nimesh Vashistha
-* Pedro Algarvio
-* Petter Strandmark
-* Prakhar Gurunani
-* Prashant Sharma
-* Ran Benita
-* Ronny Pfannschmidt
-* Sanket Duthade
-* Shubham Adep
-* Simon K
-* Tanvi Mehta
-* Thomas Grainger
-* Tim Hoffmann
-* Vasilis Gerakaris
-* William Jamir Silva
-* Zac Hatfield-Dodds
-* crricks
-* dependabot[bot]
-* duthades
-* frankgerhardt
-* kwgchi
-* mickeypash
-* symonk
-
-
-Happy testing,
-The pytest Development Team

doc/en/announce/release-6.2.1.rst

@@ -1,20 +0,0 @@
-pytest-6.2.1
-=======================================
-
-pytest 6.2.1 has just been released to PyPI.
-
-This is a bug-fix release, being a drop-in replacement. To upgrade::
-
-  pip install --upgrade pytest
-
-The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
-
-Thanks to all of the contributors to this release:
-
-* Bruno Oliveira
-* Jakob van Santen
-* Ran Benita
-
-
-Happy testing,
-The pytest Development Team

doc/en/announce/release-6.2.2.rst

@@ -1,21 +0,0 @@
-pytest-6.2.2
-=======================================
-
-pytest 6.2.2 has just been released to PyPI.
-
-This is a bug-fix release, being a drop-in replacement. To upgrade::
-
-  pip install --upgrade pytest
-
-The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
-
-Thanks to all of the contributors to this release:
-
-* Adam Johnson
-* Bruno Oliveira
-* Chris NeJame
-* Ran Benita
-
-
-Happy testing,
-The pytest Development Team

doc/en/announce/release-6.2.3.rst

@@ -1,19 +0,0 @@
-pytest-6.2.3
-=======================================
-
-pytest 6.2.3 has just been released to PyPI.
-
-This is a bug-fix release, being a drop-in replacement. To upgrade::
-
-  pip install --upgrade pytest
-
-The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
-
-Thanks to all of the contributors to this release:
-
-* Bruno Oliveira
-* Ran Benita
-
-
-Happy testing,
-The pytest Development Team

doc/en/announce/release-6.2.4.rst

@@ -1,22 +0,0 @@
-pytest-6.2.4
-=======================================
-
-pytest 6.2.4 has just been released to PyPI.
-
-This is a bug-fix release, being a drop-in replacement. To upgrade::
-
-  pip install --upgrade pytest
-
-The full changelog is available at https://docs.pytest.org/en/stable/changelog.html.
-
-Thanks to all of the contributors to this release:
-
-* Anthony Sottile
-* Bruno Oliveira
-* Christian Maurer
-* Florian Bruhin
-* Ran Benita
-
-
-Happy testing,
-The pytest Development Team

doc/en/assert.rst

@@ -1,14 +1,16 @@
-.. _`assert`:
 
-How to write and report assertions in tests
+The writing and reporting of assertions in tests
 ==================================================
 
+.. _`assertfeedback`:
 .. _`assert with the assert statement`:
+.. _`assert`:
+
 
 Asserting with the ``assert`` statement
 ---------------------------------------------------------
 
-``pytest`` allows you to use the standard Python ``assert`` for verifying
+``pytest`` allows you to use the standard python ``assert`` for verifying
 expectations and values in Python tests.  For example, you can write the
 following:
 
@@ -72,7 +74,7 @@ Assertions about expected exceptions
 ------------------------------------------
 
 In order to write assertions about raised exceptions, you can use
-:func:`pytest.raises` as a context manager like this:
+``pytest.raises`` as a context manager like this:
 
 .. code-block:: python
 
@@ -96,7 +98,7 @@ and if you need to have access to the actual exception info you may use:
             f()
         assert "maximum recursion" in str(excinfo.value)
 
-``excinfo`` is an :class:`~pytest.ExceptionInfo` instance, which is a wrapper around
+``excinfo`` is an ``ExceptionInfo`` instance, which is a wrapper around
 the actual exception raised.  The main attributes of interest are
 ``.type``, ``.value`` and ``.traceback``.
 
@@ -121,7 +123,7 @@ The regexp parameter of the ``match`` method is matched with the ``re.search``
 function, so in the above example ``match='123'`` would have worked as
 well.
 
-There's an alternate form of the :func:`pytest.raises` function where you pass
+There's an alternate form of the ``pytest.raises`` function where you pass
 a function that will be executed with the given ``*args`` and ``**kwargs`` and
 assert that the given exception is raised:
 
@@ -142,8 +144,8 @@ specific way than just having any exception raised:
     def test_f():
         f()
 
-Using :func:`pytest.raises` is likely to be better for cases where you are
-testing exceptions your own code is deliberately raising, whereas using
+Using ``pytest.raises`` is likely to be better for cases where you are testing
+exceptions your own code is deliberately raising, whereas using
 ``@pytest.mark.xfail`` with a check function is probably better for something
 like documenting unfixed bugs (where the test describes what "should" happen)
 or bugs in dependencies.
@@ -173,6 +175,8 @@ when it encounters comparisons.  For example:
 .. code-block:: python
 
     # content of test_assert2.py
+
+
     def test_set_comparison():
         set1 = set("1308")
         set2 = set("8035")

doc/en/backwards-compatibility.rst

@@ -10,7 +10,7 @@ we keep learning about new and better structures to express different details ab
 
 While we implement those modifications we try to ensure an easy transition and don't want to impose unnecessary churn on our users and community/plugin authors.
 
-As of now, pytest considers multiple types of backward compatibility transitions:
+As of now, pytest considers multipe types of backward compatibility transitions:
 
 a) trivial: APIs which trivially translate to the new mechanism,
    and do not cause problematic changes.
@@ -25,7 +25,7 @@ b) transitional: the old and new API don't conflict
    When the deprecation expires (e.g. 4.0 is released), we won't remove the deprecated functionality immediately, but will use the standard warning filters to turn them into **errors** by default. This approach makes it explicit that removal is imminent, and still gives you time to turn the deprecated feature into a warning instead of an error so it can be dealt with in your own time. In the next minor release (e.g. 4.1), the feature will be effectively removed.
 
 
-c) true breakage: should only be considered when normal transition is unreasonably unsustainable and would offset important development/features by years.
+c) true breakage: should only to be considered when normal transition is unreasonably unsustainable and would offset important development/features by years.
    In addition, they should be limited to APIs where the number of actual users is very small (for example only impacting some plugins), and can be coordinated with the community in advance.
 
    Examples for such upcoming changes:
@@ -42,7 +42,7 @@ c) true breakage: should only be considered when normal transition is unreasonab
 
    After there's no hard *-1* on the issue it should be followed up by an initial proof-of-concept Pull Request.
 
-   This POC serves as both a coordination point to assess impact and potential inspiration to come up with a transitional solution after all.
+   This POC serves as both a coordination point to assess impact and potential inspriation to come up with a transitional solution after all.
 
    After a reasonable amount of time the PR can be merged to base a new major release.
 

doc/en/bash-completion.rst

@@ -1,8 +1,8 @@
 
 .. _bash_completion:
 
-How to set up bash completion
-=============================
+Setting up bash completion
+==========================
 
 When using bash as your shell, ``pytest`` can use argcomplete
 (https://argcomplete.readthedocs.io/) for auto-completion.

doc/en/builtin.rst

@@ -6,7 +6,7 @@ Pytest API and builtin fixtures
 ================================================
 
 
-Most of the information of this page has been moved over to :ref:`api-reference`.
+Most of the information of this page has been moved over to :ref:`reference`.
 
 For information on plugin hooks and objects, see :ref:`plugins`.
 
@@ -61,7 +61,7 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
         namespace of doctests.
 
     pytestconfig [session scope]
-        Session-scoped fixture that returns the :class:`pytest.Config` object.
+        Session-scoped fixture that returns the :class:`_pytest.config.Config` object.
 
         Example::
 
@@ -144,25 +144,20 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
     recwarn
         Return a :class:`WarningsRecorder` instance that records all warnings emitted by test functions.
 
-        See https://docs.python.org/library/warnings.html for information
+        See http://docs.python.org/library/warnings.html for information
         on warning categories.
 
     tmpdir_factory [session scope]
-        Return a :class:`pytest.TempdirFactory` instance for the test session.
+        Return a :class:`_pytest.tmpdir.TempdirFactory` instance for the test session.
 
     tmp_path_factory [session scope]
-        Return a :class:`pytest.TempPathFactory` instance for the test session.
+        Return a :class:`_pytest.tmpdir.TempPathFactory` instance for the test session.
 
     tmpdir
         Return a temporary directory path object which is unique to each test
         function invocation, created as a sub directory of the base temporary
         directory.
 
-        By default, a new base temporary directory is created each test session,
-        and old bases are removed after 3 sessions, to aid in debugging. If
-        ``--basetemp`` is used then it is cleared each session. See :ref:`base
-        temporary directory`.
-
         The returned object is a `py.path.local`_ path object.
 
         .. _`py.path.local`: https://py.readthedocs.io/en/latest/path.html
@@ -172,13 +167,12 @@ For information about fixtures, see :ref:`fixtures`. To see a complete list of a
         function invocation, created as a sub directory of the base temporary
         directory.
 
-        By default, a new base temporary directory is created each test session,
-        and old bases are removed after 3 sessions, to aid in debugging. If
-        ``--basetemp`` is used then it is cleared each session. See :ref:`base
-        temporary directory`.
-
         The returned object is a :class:`pathlib.Path` object.
 
+        .. note::
+
+            In python < 3.6 this is a pathlib2.Path.
+
 
     no tests ran in 0.12s
 

doc/en/cache.rst

@@ -2,8 +2,8 @@
 .. _cache:
 
 
-How to re-run failed tests and maintain state between test runs
-===============================================================
+Cache: working with cross-testrun state
+=======================================
 
 
 

doc/en/capture.rst

@@ -1,7 +1,7 @@
 
 .. _`captures`:
 
-How to capture stdout/stderr output
+Capturing of the stdout/stderr output
 =========================================================
 
 Default stdout/stderr/stdin capturing behaviour

doc/en/changelog.rst

@@ -28,264 +28,6 @@ with advance notice in the **Deprecations** section of releases.
 
 .. towncrier release notes start
 
-pytest 6.2.4 (2021-05-04)
-=========================
-
-Bug Fixes
----------
-
-- `#8539 <https://github.com/pytest-dev/pytest/issues/8539>`_: Fixed assertion rewriting on Python 3.10.
-
-
-pytest 6.2.3 (2021-04-03)
-=========================
-
-Bug Fixes
----------
-
-- `#8414 <https://github.com/pytest-dev/pytest/issues/8414>`_: pytest used to create directories under ``/tmp`` with world-readable
-  permissions. This means that any user in the system was able to read
-  information written by tests in temporary directories (such as those created by
-  the ``tmp_path``/``tmpdir`` fixture). Now the directories are created with
-  private permissions.
-
-  pytest used to silenty use a pre-existing ``/tmp/pytest-of-<username>`` directory,
-  even if owned by another user. This means another user could pre-create such a
-  directory and gain control of another user's temporary directory. Now such a
-  condition results in an error.
-
-
-pytest 6.2.2 (2021-01-25)
-=========================
-
-Bug Fixes
----------
-
-- `#8152 <https://github.com/pytest-dev/pytest/issues/8152>`_: Fixed "(<Skipped instance>)" being shown as a skip reason in the verbose test summary line when the reason is empty.
-
-
-- `#8249 <https://github.com/pytest-dev/pytest/issues/8249>`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``.
-
-
-pytest 6.2.1 (2020-12-15)
-=========================
-
-Bug Fixes
----------
-
-- `#7678 <https://github.com/pytest-dev/pytest/issues/7678>`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
-  the host and loaded later from an UNC mounted path (Windows).
-
-
-- `#8132 <https://github.com/pytest-dev/pytest/issues/8132>`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
-  ``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
-  Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
-  and happened to compare correctly to a scalar if they had only one element.
-  After 6.2.0, these types began failing, because they inherited neither from
-  standard Python number hierarchy nor from ``numpy.ndarray``.
-
-  ``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
-  protocol and are not scalars. This treats array-like objects like numpy arrays,
-  regardless of size.
-
-
-pytest 6.2.0 (2020-12-12)
-=========================
-
-Breaking Changes
-----------------
-
-- `#7808 <https://github.com/pytest-dev/pytest/issues/7808>`_: pytest now supports python3.6+ only.
-
-
-
-Deprecations
-------------
-
-- `#7469 <https://github.com/pytest-dev/pytest/issues/7469>`_: Directly constructing/calling the following classes/functions is now deprecated:
-
-  - ``_pytest.cacheprovider.Cache``
-  - ``_pytest.cacheprovider.Cache.for_config()``
-  - ``_pytest.cacheprovider.Cache.clear_cache()``
-  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
-  - ``_pytest.capture.CaptureFixture``
-  - ``_pytest.fixtures.FixtureRequest``
-  - ``_pytest.fixtures.SubRequest``
-  - ``_pytest.logging.LogCaptureFixture``
-  - ``_pytest.pytester.Pytester``
-  - ``_pytest.pytester.Testdir``
-  - ``_pytest.recwarn.WarningsRecorder``
-  - ``_pytest.recwarn.WarningsChecker``
-  - ``_pytest.tmpdir.TempPathFactory``
-  - ``_pytest.tmpdir.TempdirFactory``
-
-  These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.
-
-
-- `#7530 <https://github.com/pytest-dev/pytest/issues/7530>`_: The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.
-
-  We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
-  related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).
-
-
-- `#7988 <https://github.com/pytest-dev/pytest/issues/7988>`_: The ``@pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.
-
-  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.
-
-
-
-Features
---------
-
-- `#5299 <https://github.com/pytest-dev/pytest/issues/5299>`_: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python>=3.8.
-  See :ref:`unraisable` for more information.
-
-
-- `#7425 <https://github.com/pytest-dev/pytest/issues/7425>`_: New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.
-
-  This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.
-
-  Internally, the old :class:`Testdir <_pytest.pytester.Testdir>` is now a thin wrapper around :class:`Pytester <_pytest.pytester.Pytester>`, preserving the old interface.
-
-
-- `#7695 <https://github.com/pytest-dev/pytest/issues/7695>`_: A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
-  This dictionary will be used to augment the "global" variables available to evaluate skipif/xfail/xpass markers.
-
-  Pseudo example
-
-  ``conftest.py``:
-
-  .. code-block:: python
-
-     def pytest_markeval_namespace():
-         return {"color": "red"}
-
-  ``test_func.py``:
-
-  .. code-block:: python
-
-     @pytest.mark.skipif("color == 'blue'", reason="Color is not red")
-     def test_func():
-         assert False
-
-
-- `#8006 <https://github.com/pytest-dev/pytest/issues/8006>`_: It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
-  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
-  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.
-
-  Additionally, :meth:`MonkeyPatch.context <pytest.MonkeyPatch.context>` is now a classmethod,
-  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
-  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
-  is not ``undo()``-ed automatically.
-
-
-
-Improvements
-------------
-
-- `#1265 <https://github.com/pytest-dev/pytest/issues/1265>`_: Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.
-
-
-- `#2044 <https://github.com/pytest-dev/pytest/issues/2044>`_: Verbose mode now shows the reason that a test was skipped in the test's terminal line after the "SKIPPED", "XFAIL" or "XPASS".
-
-
-- `#7469 <https://github.com/pytest-dev/pytest/issues/7469>`_ The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
-  The newly-exported types are:
-
-  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
-  - ``pytest.Cache`` for the :fixture:`cache` fixture.
-  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
-  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
-  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
-  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
-  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
-  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
-  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
-  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
-  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.
-
-  Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
-  Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.
-
-  Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.
-
-
-- `#7527 <https://github.com/pytest-dev/pytest/issues/7527>`_: When a comparison between :func:`namedtuple <collections.namedtuple>` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.
-
-
-- `#7615 <https://github.com/pytest-dev/pytest/issues/7615>`_: :meth:`Node.warn <_pytest.nodes.Node.warn>` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning <pytest.PytestWarning>`.
-
-
-- `#7701 <https://github.com/pytest-dev/pytest/issues/7701>`_: Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.
-
-
-- `#7710 <https://github.com/pytest-dev/pytest/issues/7710>`_: Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
-  raising :class:`TypeError`.
-
-  This was the undocumented behavior before 3.7, but is now officially a supported feature.
-
-
-- `#7938 <https://github.com/pytest-dev/pytest/issues/7938>`_: New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.
-
-
-- `#8023 <https://github.com/pytest-dev/pytest/issues/8023>`_: Added ``'node_modules'`` to default value for :confval:`norecursedirs`.
-
-
-- `#8032 <https://github.com/pytest-dev/pytest/issues/8032>`_: :meth:`doClassCleanups <unittest.TestCase.doClassCleanups>` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.
-
-
-
-Bug Fixes
----------
-
-- `#4824 <https://github.com/pytest-dev/pytest/issues/4824>`_: Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.
-
-
-- `#7758 <https://github.com/pytest-dev/pytest/issues/7758>`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.
-
-
-- `#7911 <https://github.com/pytest-dev/pytest/issues/7911>`_: Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.
-
-
-- `#7913 <https://github.com/pytest-dev/pytest/issues/7913>`_: Fixed a crash or hang in :meth:`pytester.spawn <_pytest.pytester.Pytester.spawn>` when the :mod:`readline` module is involved.
-
-
-- `#7951 <https://github.com/pytest-dev/pytest/issues/7951>`_: Fixed handling of recursive symlinks when collecting tests.
-
-
-- `#7981 <https://github.com/pytest-dev/pytest/issues/7981>`_: Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.
-
-
-- `#8016 <https://github.com/pytest-dev/pytest/issues/8016>`_: Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.
-
-
-
-Improved Documentation
-----------------------
-
-- `#7429 <https://github.com/pytest-dev/pytest/issues/7429>`_: Add more information and use cases about skipping doctests.
-
-
-- `#7780 <https://github.com/pytest-dev/pytest/issues/7780>`_: Classes which should not be inherited from are now marked ``final class`` in the API reference.
-
-
-- `#7872 <https://github.com/pytest-dev/pytest/issues/7872>`_: ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``"string"``.
-
-
-- `#7878 <https://github.com/pytest-dev/pytest/issues/7878>`_: In pull request section, ask to commit after editing changelog and authors file.
-
-
-
-Trivial/Internal Changes
-------------------------
-
-- `#7802 <https://github.com/pytest-dev/pytest/issues/7802>`_: The ``attrs`` dependency requirement is now >=19.2.0 instead of >=17.4.0.
-
-
-- `#8014 <https://github.com/pytest-dev/pytest/issues/8014>`_: `.pyc` files created by pytest's assertion rewriting now conform to the newer PEP-552 format on Python>=3.7.
-  (These files are internal and only interpreted by pytest itself.)
-
-
 pytest 6.1.2 (2020-10-28)
 =========================
 
@@ -1055,7 +797,7 @@ Bug Fixes
 - `#7110 <https://github.com/pytest-dev/pytest/issues/7110>`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.
 
 
-- `#7143 <https://github.com/pytest-dev/pytest/issues/7143>`_: Fix ``File.from_parent`` so it forwards extra keyword arguments to the constructor.
+- `#7143 <https://github.com/pytest-dev/pytest/issues/7143>`_: Fix ``File.from_constructor`` so it forwards extra keyword arguments to the constructor.
 
 
 - `#7145 <https://github.com/pytest-dev/pytest/issues/7145>`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.
@@ -2131,44 +1873,6 @@ Improved Documentation
 - `#5416 <https://github.com/pytest-dev/pytest/issues/5416>`_: Fix PytestUnknownMarkWarning in run/skip example.
 
 
-pytest 4.6.11 (2020-06-04)
-==========================
-
-Bug Fixes
----------
-
-- `#6334 <https://github.com/pytest-dev/pytest/issues/6334>`_: Fix summary entries appearing twice when ``f/F`` and ``s/S`` report chars were used at the same time in the ``-r`` command-line option (for example ``-rFf``).
-
-  The upper case variants were never documented and the preferred form should be the lower case.
-
-
-- `#7310 <https://github.com/pytest-dev/pytest/issues/7310>`_: Fix ``UnboundLocalError: local variable 'letter' referenced before
-  assignment`` in ``_pytest.terminal.pytest_report_teststatus()``
-  when plugins return report objects in an unconventional state.
-
-  This was making ``pytest_report_teststatus()`` skip
-  entering if-block branches that declare the ``letter`` variable.
-
-  The fix was to set the initial value of the ``letter`` before
-  the if-block cascade so that it always has a value.
-
-
-pytest 4.6.10 (2020-05-08)
-==========================
-
-Features
---------
-
-- `#6870 <https://github.com/pytest-dev/pytest/issues/6870>`_: New ``Config.invocation_args`` attribute containing the unchanged arguments passed to ``pytest.main()``.
-
-  Remark: while this is technically a new feature and according to our `policy <https://docs.pytest.org/en/latest/py27-py34-deprecation.html#what-goes-into-4-6-x-releases>`_ it should not have been backported, we have opened an exception in this particular case because it fixes a serious interaction with ``pytest-xdist``, so it can also be considered a bugfix.
-
-Trivial/Internal Changes
-------------------------
-
-- `#6404 <https://github.com/pytest-dev/pytest/issues/6404>`_: Remove usage of ``parser`` module, deprecated in Python 3.9.
-
-
 pytest 4.6.9 (2020-01-04)
 =========================
 
@@ -3117,12 +2821,12 @@ Features
   will not issue the warning.
 
 
-- `#3632 <https://github.com/pytest-dev/pytest/issues/3632>`_: Richer equality comparison introspection on ``AssertionError`` for objects created using `attrs <https://www.attrs.org/en/stable/>`__ or `dataclasses <https://docs.python.org/3/library/dataclasses.html>`_ (Python 3.7+, `backported to 3.6 <https://pypi.org/project/dataclasses>`__).
+- `#3632 <https://github.com/pytest-dev/pytest/issues/3632>`_: Richer equality comparison introspection on ``AssertionError`` for objects created using `attrs <http://www.attrs.org/en/stable/>`__ or `dataclasses <https://docs.python.org/3/library/dataclasses.html>`_ (Python 3.7+, `backported to 3.6 <https://pypi.org/project/dataclasses>`__).
 
 
 - `#4278 <https://github.com/pytest-dev/pytest/issues/4278>`_: ``CACHEDIR.TAG`` files are now created inside cache directories.
 
-  Those files are part of the `Cache Directory Tagging Standard <https://bford.info/cachedir/spec.html>`__, and can
+  Those files are part of the `Cache Directory Tagging Standard <http://www.bford.info/cachedir/spec.html>`__, and can
   be used by backup or synchronization programs to identify pytest's cache directory as such.
 
 
@@ -5106,7 +4810,7 @@ Improved Documentation
 
 - In one of the simple examples, use ``pytest_collection_modifyitems()`` to skip
   tests based on a command-line option, allowing its sharing while preventing a
-  user error when accessing ``pytest.config`` before the argument parsing.
+  user error when acessing ``pytest.config`` before the argument parsing.
   (`#2653 <https://github.com/pytest-dev/pytest/issues/2653>`_)
 
 
@@ -5518,7 +5222,7 @@ Changes
   Thanks `@ojii`_ for the PR.
 
 * Replace minor/patch level version numbers in the documentation with placeholders.
-  This significantly reduces change-noise as different contributors regenerate
+  This significantly reduces change-noise as different contributors regnerate
   the documentation on different platforms.
   Thanks `@RonnyPfannschmidt`_ for the PR.
 
@@ -8475,7 +8179,7 @@ Bug fixes:
 
 - fixes for making the jython/win32 combination work, note however:
   jython2.5.1/win32 does not provide a command line launcher, see
-  https://bugs.jython.org/issue1491 . See pylib install documentation
+  http://bugs.jython.org/issue1491 . See pylib install documentation
   for how to work around.
 
 - fixes for handling of unicode exception values and unprintable objects

doc/en/conf.py

@@ -15,13 +15,11 @@
 #
 # The full version, including alpha/beta/rc tags.
 # The short X.Y version.
-import ast
 import os
 import sys
-from typing import List
-from typing import TYPE_CHECKING
 
 from _pytest import __version__ as version
+from _pytest.compat import TYPE_CHECKING
 
 if TYPE_CHECKING:
     import sphinx.application
@@ -35,7 +33,6 @@ release = ".".join(version.split(".")[:2])
 # sys.path.insert(0, os.path.abspath('.'))
 
 autodoc_member_order = "bysource"
-autodoc_typehints = "description"
 todo_include_todos = 1
 
 # -- General configuration -----------------------------------------------------
@@ -71,7 +68,7 @@ master_doc = "contents"
 
 # General information about the project.
 project = "pytest"
-copyright = "2015–2021, holger krekel and pytest-dev team"
+copyright = "2015–2020, holger krekel and pytest-dev team"
 
 
 # The language for content autogenerated by Sphinx. Refer to documentation
@@ -160,7 +157,7 @@ html_short_title = "pytest-%s" % release
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
-html_logo = "img/pytest_logo_curves.svg"
+html_logo = "img/pytest1.png"
 
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
@@ -252,7 +249,7 @@ latex_documents = [
         "contents",
         "pytest.tex",
         "pytest Documentation",
-        "holger krekel, trainer and consultant, https://merlinux.eu/",
+        "holger krekel, trainer and consultant, http://merlinux.eu",
         "manual",
     )
 ]
@@ -293,7 +290,7 @@ man_pages = [("usage", "pytest", "pytest usage", ["holger krekel at merlinux eu"
 epub_title = "pytest"
 epub_author = "holger krekel at merlinux eu"
 epub_publisher = "holger krekel at merlinux eu"
-epub_copyright = "2013-2021, holger krekel et alii"
+epub_copyright = "2013-2020, holger krekel et alii"
 
 # The language of the text. It defaults to the language option
 # or en if the language is not set.
@@ -401,22 +398,3 @@ def setup(app: "sphinx.application.Sphinx") -> None:
     )
 
     configure_logging(app)
-
-    # Make Sphinx mark classes with "final" when decorated with @final.
-    # We need this because we import final from pytest._compat, not from
-    # typing (for Python < 3.8 compat), so Sphinx doesn't detect it.
-    # To keep things simple we accept any `@final` decorator.
-    # Ref: https://github.com/pytest-dev/pytest/pull/7780
-    import sphinx.pycode.ast
-    import sphinx.pycode.parser
-
-    original_is_final = sphinx.pycode.parser.VariableCommentPicker.is_final
-
-    def patched_is_final(self, decorators: List[ast.expr]) -> bool:
-        if original_is_final(self, decorators):
-            return True
-        return any(
-            sphinx.pycode.ast.unparse(decorator) == "final" for decorator in decorators
-        )
-
-    sphinx.pycode.parser.VariableCommentPicker.is_final = patched_is_final

doc/en/contact.rst

@@ -16,13 +16,12 @@ Contact channels
 
 - `pytest-dev at python.org (mailing list)`_ pytest specific announcements and discussions.
 
+- `pytest-commit at python.org (mailing list)`_: for commits and new issues
+
 - :doc:`contribution guide <contributing>` for help on submitting pull
   requests to GitHub.
 
-- ``#pytest`` `on irc.libera.chat <ircs://irc.libera.chat:6697/#pytest>`_ IRC
-  channel for random questions (using an IRC client, `via webchat
-  <https://web.libera.chat/#pytest>`_, or `via Matrix
-  <https://matrix.to/#/%23pytest:libera.chat>`_).
+- ``#pylib`` on irc.freenode.net IRC channel for random questions.
 
 - private mail to Holger.Krekel at gmail com if you want to communicate sensitive issues
 
@@ -31,19 +30,19 @@ Contact channels
   consulting.
 
 .. _`pytest issue tracker`: https://github.com/pytest-dev/pytest/issues
-.. _`old issue tracker`: https://bitbucket.org/hpk42/py-trunk/issues/
+.. _`old issue tracker`: http://bitbucket.org/hpk42/py-trunk/issues/
 
-.. _`merlinux.eu`: https://merlinux.eu/
+.. _`merlinux.eu`: http://merlinux.eu
 
 .. _`get an account`:
 
-.. _tetamap: https://tetamap.wordpress.com/
+.. _tetamap: http://tetamap.wordpress.com
 
-.. _`@pylibcommit`: https://twitter.com/pylibcommit
+.. _`@pylibcommit`: http://twitter.com/pylibcommit
 
 
 .. _`Testing in Python`: http://lists.idyll.org/listinfo/testing-in-python
-.. _FOAF: https://en.wikipedia.org/wiki/FOAF
+.. _FOAF: http://en.wikipedia.org/wiki/FOAF
 .. _`py-dev`:
 .. _`development mailing list`:
 .. _`pytest-dev at python.org (mailing list)`: http://mail.python.org/mailman/listinfo/pytest-dev

doc/en/contents.rst

@@ -7,81 +7,37 @@ Full pytest documentation
 
 .. `Download latest version as EPUB <http://media.readthedocs.org/epub/pytest/latest/pytest.epub>`_
 
-
-Start here
------------
-
 .. toctree::
    :maxdepth: 2
 
    getting-started
+   usage
+   existingtestsuite
+   assert
+   fixture
+   mark
+   monkeypatch
+   tmpdir
+   capture
+   warnings
+   doctest
+   skipping
+   parametrize
+   cache
+   unittest
+   nose
+   xunit_setup
+   plugins
+   writing_plugins
+   logging
+   reference
 
-
-How-to guides
--------------
-
-.. toctree::
-   :maxdepth: 2
-
-   how-to/usage
-   how-to/assert
-   how-to/fixtures
-   how-to/mark
-   how-to/parametrize
-   how-to/tmpdir
-   how-to/monkeypatch
-   how-to/doctest
-   how-to/cache
-
-   how-to/logging
-   how-to/capture-stdout-stderr
-   how-to/capture-warnings
-   how-to/skipping
-
-   how-to/plugins
-   how-to/writing_plugins
-   how-to/writing_hook_functions
-
-   how-to/existingtestsuite
-   how-to/unittest
-   how-to/nose
-   how-to/xunit_setup
-
-   how-to/bash-completion
-
-
-Reference guides
------------------
-
-.. toctree::
-   :maxdepth: 2
-
-   reference/fixtures
-   reference/plugin_list
-   reference/customize
-   reference/reference
-
-
-Explanation
------------------
-
-.. toctree::
-   :maxdepth: 2
-
-   explanation/anatomy
-   explanation/fixtures
-   explanation/goodpractices
-   explanation/flaky
-   explanation/pythonpath
-
-
-Further topics
------------------
-
-.. toctree::
-   :maxdepth: 2
-
+   goodpractices
+   flaky
+   pythonpath
+   customize
    example/index
+   bash-completion
 
    backwards-compatibility
    deprecations
@@ -95,7 +51,6 @@ Further topics
    license
    contact
 
-   history
    historical-notes
    talks
    projects

doc/en/customize.rst

@@ -145,8 +145,6 @@ Finding the ``rootdir``
 
 Here is the algorithm which finds the rootdir from ``args``:
 
-- If ``-c`` is passed in the command-line, use that as configuration file, and its directory as ``rootdir``.
-
 - Determine the common ancestor directory for the specified ``args`` that are
   recognised as paths that exist in the file system. If no such paths are
   found, the common ancestor directory is set to the current working directory.
@@ -162,7 +160,7 @@ Here is the algorithm which finds the rootdir from ``args``:
   ``setup.cfg`` in each of the specified ``args`` and upwards. If one is
   matched, it becomes the ``configfile`` and its directory becomes the ``rootdir``.
 
-- If no ``configfile`` was found and no configuration argument is passed, use the already determined common ancestor as root
+- If no ``configfile`` was found, use the already determined common ancestor as root
   directory. This allows the use of pytest in structures that are not part of
   a package and don't have any particular configuration file.
 
@@ -179,12 +177,12 @@ Files will only be matched for configuration if:
 The files are considered in the order above. Options from multiple ``configfiles`` candidates
 are never merged - the first match wins.
 
-The :class:`Config <pytest.Config>` object (accessible via hooks or through the :fixture:`pytestconfig` fixture)
+The internal :class:`Config <_pytest.config.Config>` object (accessible via hooks or through the :fixture:`pytestconfig` fixture)
 will subsequently carry these attributes:
 
-- :attr:`config.rootpath <pytest.Config.rootpath>`: the determined root directory, guaranteed to exist.
+- :attr:`config.rootpath <_pytest.config.Config.rootpath>`: the determined root directory, guaranteed to exist.
 
-- :attr:`config.inipath <pytest.Config.inipath>`: the determined ``configfile``, may be ``None``
+- :attr:`config.inipath <_pytest.config.Config.inipath>`: the determined ``configfile``, may be ``None``
   (it is named ``inipath`` for historical reasons).
 
 .. versionadded:: 6.1

doc/en/deprecations.rst

@@ -19,93 +19,6 @@ Below is a complete list of all pytest features which are considered deprecated.
 :class:`PytestWarning` or subclasses, which can be filtered using :ref:`standard warning filters <warnings>`.
 
 
-``py.path.local`` arguments for hooks replaced with ``pathlib.Path``
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-In order to support the transition to :mod:`pathlib`, the following hooks now receive additional arguments:
-
-*  :func:`pytest_ignore_collect(fspath: pathlib.Path) <_pytest.hookspec.pytest_ignore_collect>`
-*  :func:`pytest_collect_file(fspath: pathlib.Path) <_pytest.hookspec.pytest_collect_file>`
-*  :func:`pytest_pycollect_makemodule(fspath: pathlib.Path) <_pytest.hookspec.pytest_pycollect_makemodule>`
-*  :func:`pytest_report_header(startpath: pathlib.Path) <_pytest.hookspec.pytest_report_header>`
-*  :func:`pytest_report_collectionfinish(startpath: pathlib.Path) <_pytest.hookspec.pytest_report_collectionfinish>`
-
-The accompanying ``py.path.local`` based paths have been deprecated: plugins which manually invoke those hooks should only pass the new ``pathlib.Path`` arguments, and users should change their hook implementations to use the new ``pathlib.Path`` arguments.
-
-
-``Node.fspath`` in favor of ``pathlib`` and ``Node.path``
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 6.3
-
-As pytest tries to move off `py.path.local <https://py.readthedocs.io/en/latest/path.html>`__ we ported most of the node internals to :mod:`pathlib`.
-
-Pytest will provide compatibility for quite a while.
-
-Diamond inheritance between :class:`pytest.File` and :class:`pytest.Item`
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 6.3
-
-Inheriting from both Item and file at once has never been supported officially,
-however some plugins providing linting/code analysis have been using this as a hack.
-
-This practice is now officially deprecated and a common way to fix this is `example pr fixing inheritance`_.
-
-
-
-.. _example pr fixing inheritance: https://github.com/asmeurer/pytest-flakes/pull/40/files
-
-
-Backward compatibilities in ``Parser.addoption``
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 2.4
-
-Several behaviors of :meth:`Parser.addoption <pytest.Parser.addoption>` are now
-scheduled for removal in pytest 7 (deprecated since pytest 2.4.0):
-
-- ``parser.addoption(..., help=".. %default ..")`` - use ``%(default)s`` instead.
-- ``parser.addoption(..., type="int/string/float/complex")`` - use ``type=int`` etc. instead.
-
-
-Raising ``unittest.SkipTest`` during collection
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 6.3
-
-Raising :class:`unittest.SkipTest` to skip collection of tests during the
-pytest collection phase is deprecated. Use :func:`pytest.skip` instead.
-
-Note: This deprecation only relates to using `unittest.SkipTest` during test
-collection. You are probably not doing that. Ordinary usage of
-:class:`unittest.SkipTest` / :meth:`unittest.TestCase.skipTest` /
-:func:`unittest.skip` in unittest test cases is fully supported.
-
-
-The ``--strict`` command-line option
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 6.2
-
-The ``--strict`` command-line option has been deprecated in favor of ``--strict-markers``, which
-better conveys what the option does.
-
-We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing
-flag for all strictness related options (``--strict-markers`` and ``--strict-config``
-at the moment, more might be introduced in the future).
-
-
-The ``yield_fixture`` function/decorator
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-.. deprecated:: 6.2
-
-``pytest.yield_fixture`` is a deprecated alias for :func:`pytest.fixture`.
-
-It has been so for a very long time, so can be search/replaced safely.
-
-
 The ``pytest_warning_captured`` hook
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -462,8 +375,8 @@ Metafunc.addcall
 
 .. versionremoved:: 4.0
 
-``Metafunc.addcall`` was a precursor to the current parametrized mechanism. Users should use
-:meth:`pytest.Metafunc.parametrize` instead.
+``_pytest.python.Metafunc.addcall`` was a precursor to the current parametrized mechanism. Users should use
+:meth:`_pytest.python.Metafunc.parametrize` instead.
 
 Example:
 

doc/en/development_guide.rst

@@ -4,4 +4,4 @@ Development Guide
 
 The contributing guidelines are to be found :ref:`here <contributing>`.
 The release procedure for pytest is documented on
-`GitHub <https://github.com/pytest-dev/pytest/blob/main/RELEASING.rst>`_.
+`GitHub <https://github.com/pytest-dev/pytest/blob/master/RELEASING.rst>`_.

doc/en/doctest.rst

@@ -1,9 +1,8 @@
-.. _doctest:
 
-How to run doctests
+Doctest integration for modules and test files
 =========================================================
 
-By default, all files matching the ``test*.txt`` pattern will
+By default all files matching the ``test*.txt`` pattern will
 be run through the python standard ``doctest`` module.  You
 can change the pattern by issuing:
 
@@ -49,7 +48,7 @@ and functions, including from test modules:
 
     # content of mymodule.py
     def something():
-        """a doctest in a docstring
+        """ a doctest in a docstring
         >>> something()
         42
         """
@@ -78,6 +77,15 @@ putting them into a pytest.ini file like this:
     [pytest]
     addopts = --doctest-modules
 
+.. note::
+
+    The builtin pytest doctest supports only ``doctest`` blocks, but if you are looking
+    for more advanced checking over *all* your documentation,
+    including doctests, ``.. codeblock:: python`` Sphinx directive support,
+    and any other examples your documentation may include, you may wish to
+    consider `Sybil <https://sybil.readthedocs.io/en/latest/index.html>`__.
+    It provides pytest integration out of the box.
+
 
 Encoding
 --------
@@ -105,7 +113,7 @@ lengthy exception stack traces you can just write:
 .. code-block:: ini
 
     [pytest]
-    doctest_optionflags = NORMALIZE_WHITESPACE IGNORE_EXCEPTION_DETAIL
+    doctest_optionflags= NORMALIZE_WHITESPACE IGNORE_EXCEPTION_DETAIL
 
 Alternatively, options can be enabled by an inline comment in the doc test
 itself:
@@ -194,11 +202,11 @@ It is possible to use fixtures using the ``getfixture`` helper:
 .. code-block:: text
 
     # content of example.rst
-    >>> tmp = getfixture('tmp_path')
+    >>> tmp = getfixture('tmpdir')
     >>> ...
     >>>
 
-Note that the fixture needs to be defined in a place visible by pytest, for example, a `conftest.py`
+Note that the fixture needs to be defined in a place visible by pytest, for example a `conftest.py`
 file or plugin; normal python files containing docstrings are not normally scanned for fixtures
 unless explicitly configured by :confval:`python_files`.
 
@@ -245,32 +253,12 @@ Note that like the normal ``conftest.py``, the fixtures are discovered in the di
 Meaning that if you put your doctest with your source code, the relevant conftest.py needs to be in the same directory tree.
 Fixtures will not be discovered in a sibling directory tree!
 
-Skipping tests
-^^^^^^^^^^^^^^
+Skipping tests dynamically
+^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-For the same reasons one might want to skip normal tests, it is also possible to skip
-tests inside doctests.
-
-To skip a single check inside a doctest you can use the standard
-`doctest.SKIP <https://docs.python.org/3/library/doctest.html#doctest.SKIP>`__ directive:
-
-.. code-block:: python
-
-    def test_random(y):
-        """
-        >>> random.random()  # doctest: +SKIP
-        0.156231223
-
-        >>> 1 + 1
-        2
-        """
-
-This will skip the first check, but not the second.
-
-pytest also allows using the standard pytest functions :func:`pytest.skip` and
-:func:`pytest.xfail` inside doctests, which might be useful because you can
-then skip/xfail tests based on external conditions:
+.. versionadded:: 4.4
 
+You can use ``pytest.skip`` to dynamically skip doctests. For example:
 
 .. code-block:: text
 
@@ -278,35 +266,3 @@ then skip/xfail tests based on external conditions:
     >>> if sys.platform.startswith('win'):
     ...     pytest.skip('this doctest does not work on Windows')
     ...
-    >>> import fcntl
-    >>> ...
-
-However using those functions is discouraged because it reduces the readability of the
-docstring.
-
-.. note::
-
-    :func:`pytest.skip` and :func:`pytest.xfail` behave differently depending
-    if the doctests are in a Python file (in docstrings) or a text file containing
-    doctests intermingled with text:
-
-    * Python modules (docstrings): the functions only act in that specific docstring,
-      letting the other docstrings in the same module execute as normal.
-
-    * Text files: the functions will skip/xfail the checks for the rest of the entire
-      file.
-
-
-Alternatives
-------------
-
-While the built-in pytest support provides a good set of functionalities for using
-doctests, if you use them extensively you might be interested in those external packages
-which add many more features, and include pytest integration:
-
-* `pytest-doctestplus <https://github.com/astropy/pytest-doctestplus>`__: provides
-  advanced doctest support and enables the testing of reStructuredText (".rst") files.
-
-* `Sybil <https://sybil.readthedocs.io>`__: provides a way to test examples in
-  your documentation by parsing them from the documentation source and evaluating
-  the parsed examples as part of your normal test run.

doc/en/example/assertion/failure_demo.py

@@ -176,7 +176,7 @@ class TestRaises:
 
     def test_reinterpret_fails_with_print_for_the_fun_of_it(self):
         items = [1, 2, 3]
-        print(f"items is {items!r}")
+        print("items is {!r}".format(items))
         a, b = items.pop()
 
     def test_some_error(self):

doc/en/example/assertion/global_testmodule_config/conftest.py

@@ -11,4 +11,4 @@ def pytest_runtest_setup(item):
             return
         mod = item.getparent(pytest.Module).obj
         if hasattr(mod, "hello"):
-            print(f"mod.hello {mod.hello!r}")
+            print("mod.hello {!r}".format(mod.hello))

doc/en/example/assertion/test_failures.py

@@ -5,9 +5,9 @@ failure_demo = os.path.join(os.path.dirname(__file__), "failure_demo.py")
 pytest_plugins = ("pytester",)
 
 
-def test_failure_demo_fails_properly(pytester):
-    target = pytester.path.joinpath(os.path.basename(failure_demo))
+def test_failure_demo_fails_properly(testdir):
+    target = testdir.tmpdir.join(os.path.basename(failure_demo))
     shutil.copy(failure_demo, target)
-    result = pytester.runpytest(target, syspathinsert=True)
+    result = testdir.runpytest(target, syspathinsert=True)
     result.stdout.fnmatch_lines(["*44 failed*"])
     assert result.ret != 0

doc/en/example/fixtures/fixture_availability.svg

@@ -1,132 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="572" height="542">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class, circle.module, circle.package {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class, text.module, text.package {
-            fill: #0e84b5;
-        }
-        line, path {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-    </style>
-
-    <!-- main scope -->
-    <circle class="package" r="270" cx="286" cy="271" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 26,271 A 260 260 0 0 1 546 271" id="testp"/>
-    </defs>
-    <text class="package">
-        <textPath href="#testp" startOffset="50%">tests</textPath>
-    </text>
-
-    <!-- subpackage -->
-    <circle class="package" r="140" cx="186" cy="271" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 56,271 A 130 130 0 0 1 316 271" id="subpackage"/>
-    </defs>
-    <text class="package">
-        <textPath href="#subpackage" startOffset="50%">subpackage</textPath>
-    </text>
-
-    <!-- test_subpackage.py -->
-    <circle class="module" r="90" cx="186" cy="311" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 106,311 A 80 80 0 0 1 266 311" id="testSubpackage"/>
-    </defs>
-    <text class="module">
-        <textPath href="#testSubpackage" startOffset="50%">test_subpackage.py</textPath>
-    </text>
-    <!-- innermost -->
-    <line x1="186" x2="186" y1="271" y2="351"/>
-    <!-- mid -->
-    <path d="M 186 351 L 136 351 L 106 331 L 106 196" />
-    <!-- order -->
-    <path d="M 186 351 L 256 351 L 316 291 L 316 136" />
-    <!-- top -->
-    <path d="M 186 351 L 186 391 L 231 436 L 331 436" />
-    <ellipse class="fixture" rx="50" ry="25" cx="186" cy="271" />
-    <text x="186" y="271">innermost</text>
-    <rect class="test" width="110" height="50" x="131" y="326" />
-    <text x="186" y="351">test_order</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="126" cy="196" />
-    <text x="126" y="196">mid</text>
-    <!-- scope order number -->
-    <mask id="testSubpackageOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="90" cx="186" cy="311" />
-    </mask>
-    <circle class="module" r="15" cx="96" cy="311" mask="url(#testSubpackageOrderMask)"/>
-    <text class="module" x="96" y="311">1</text>
-     <!-- scope order number -->
-    <mask id="subpackageOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="140" cx="186" cy="271" />
-    </mask>
-    <circle class="module" r="15" cx="46" cy="271" mask="url(#subpackageOrderMask)"/>
-    <text class="module" x="46" y="271">2</text>
-    <!-- scope order number -->
-    <mask id="testsOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="270" cx="286" cy="271" />
-    </mask>
-    <circle class="module" r="15" cx="16" cy="271" mask="url(#testsOrderMask)"/>
-    <text class="module" x="16" y="271">3</text>
-
-    <!-- test_top.py -->
-    <circle class="module" r="85" cx="441" cy="271" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 366,271 A 75 75 0 0 1 516 271" id="testTop"/>
-    </defs>
-    <text class="module">
-        <textPath href="#testTop" startOffset="50%">test_top.py</textPath>
-    </text>
-    <!-- innermost -->
-    <line x1="441" x2="441" y1="306" y2="236"/>
-    <!-- order -->
-    <path d="M 441 306 L 376 306 L 346 276 L 346 136" />
-    <!-- top -->
-    <path d="M 441 306 L 441 411 L 411 436 L 331 436" />
-    <ellipse class="fixture" rx="50" ry="25" cx="441" cy="236" />
-    <text x="441" y="236">innermost</text>
-    <rect class="test" width="110" height="50" x="386" y="281" />
-    <text x="441" y="306">test_order</text>
-    <!-- scope order number -->
-    <mask id="testTopOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="85" cx="441" cy="271" />
-    </mask>
-    <circle class="module" r="15" cx="526" cy="271" mask="url(#testTopOrderMask)"/>
-    <text class="module" x="526" y="271">1</text>
-    <!-- scope order number -->
-    <circle class="module" r="15" cx="556" cy="271" mask="url(#testsOrderMask)"/>
-    <text class="module" x="556" y="271">2</text>
-
-    <ellipse class="fixture" rx="50" ry="25" cx="331" cy="436" />
-    <text x="331" y="436">top</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="331" cy="136" />
-    <text x="331" y="136">order</text>
-</svg>

doc/en/example/fixtures/fixture_availability_plugins.svg

@@ -1,142 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="587" height="382">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-            alignment-baseline: center;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class, circle.module, circle.package, circle.plugin {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class, text.module, text.package, text.plugin {
-            fill: #0e84b5;
-        }
-        line, path {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-    </style>
-
-    <!-- plugin_a.py scope -->
-    <circle class="plugin" r="85" cx="486" cy="86" />
-    <!-- plugin name -->
-    <defs>
-        <path d="M 411,86 A 75 75 0 0 1 561 86" id="pluginA"/>
-    </defs>
-    <text class="plugin">
-        <textPath href="#pluginA" startOffset="50%">plugin_a</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="pluginAOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="85" cx="486" cy="86" />
-    </mask>
-    <circle class="module" r="15" cx="571" cy="86" mask="url(#pluginAOrderMask)"/>
-    <text class="module" x="571" y="86">4</text>
-
-    <!-- plugin_b.py scope -->
-    <circle class="plugin" r="85" cx="486" cy="296" />
-    <!-- plugin name -->
-    <defs>
-        <path d="M 411,296 A 75 75 0 0 1 561 296" id="pluginB"/>
-    </defs>
-    <text class="plugin">
-        <textPath href="#pluginB" startOffset="50%">plugin_b</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="pluginBOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="85" cx="486" cy="296" />
-    </mask>
-    <circle class="module" r="15" cx="571" cy="296" mask="url(#pluginBOrderMask)"/>
-    <text class="module" x="571" y="296">4</text>
-
-    <!-- main scope -->
-    <circle class="package" r="190" cx="191" cy="191" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 11,191 A 180 180 0 0 1 371 191" id="testp"/>
-    </defs>
-    <text class="package">
-        <textPath href="#testp" startOffset="50%">tests</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="mainOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="190" cx="191" cy="191" />
-    </mask>
-    <circle class="module" r="15" cx="381" cy="191" mask="url(#mainOrderMask)"/>
-    <text class="module" x="381" y="191">3</text>
-
-    <!-- subpackage -->
-    <circle class="package" r="140" cx="191" cy="231" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 61,231 A 130 130 0 0 1 321 231" id="subpackage"/>
-    </defs>
-    <text class="package">
-        <textPath href="#subpackage" startOffset="50%">subpackage</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="subpackageOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="140" cx="191" cy="231" />
-    </mask>
-    <circle class="module" r="15" cx="331" cy="231" mask="url(#subpackageOrderMask)"/>
-    <text class="module" x="331" y="231">2</text>
-
-    <!-- test_subpackage.py -->
-    <circle class="module" r="90" cx="191" cy="271" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 111,271 A 80 80 0 0 1 271 271" id="testSubpackage"/>
-    </defs>
-    <text class="module">
-        <textPath href="#testSubpackage" startOffset="50%">test_subpackage.py</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="testSubpackageOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="90" cx="191" cy="271" />
-    </mask>
-    <circle class="module" r="15" cx="281" cy="271" mask="url(#testSubpackageOrderMask)"/>
-    <text class="module" x="281" y="271">1</text>
-
-    <!-- innermost -->
-    <line x1="191" x2="191" y1="231" y2="311"/>
-    <!-- mid -->
-    <path d="M 191 306 L 101 306 L 91 296 L 91 156 L 101 146 L 191 146" />
-    <!-- order -->
-    <path d="M 191 316 L 91 316 L 81 306 L 81 61 L 91 51 L 191 51" />
-    <!-- a_fix -->
-    <path d="M 191 306 L 291 306 L 301 296 L 301 96 L 311 86 L 486 86" />
-    <!-- b_fix -->
-    <path d="M 191 316 L 316 316 L 336 296 L 486 296" />
-    <ellipse class="fixture" rx="50" ry="25" cx="191" cy="231" />
-    <text x="191" y="231">inner</text>
-    <rect class="test" width="110" height="50" x="136" y="286" />
-    <text x="191" y="311">test_order</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="191" cy="146" />
-    <text x="191" y="146">mid</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="191" cy="51" />
-    <text x="191" y="51">order</text>
-
-    <ellipse class="fixture" rx="50" ry="25" cx="486" cy="86" />
-    <text x="486" y="86">a_fix</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="486" cy="296" />
-    <text x="486" y="296">b_fix</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order.py

@@ -0,0 +1,38 @@
+import pytest
+
+# fixtures documentation order example
+order = []
+
+
+@pytest.fixture(scope="session")
+def s1():
+    order.append("s1")
+
+
+@pytest.fixture(scope="module")
+def m1():
+    order.append("m1")
+
+
+@pytest.fixture
+def f1(f3):
+    order.append("f1")
+
+
+@pytest.fixture
+def f3():
+    order.append("f3")
+
+
+@pytest.fixture(autouse=True)
+def a1():
+    order.append("a1")
+
+
+@pytest.fixture
+def f2():
+    order.append("f2")
+
+
+def test_order(f1, m1, f2, s1):
+    assert order == ["s1", "m1", "a1", "f3", "f1", "f2"]

doc/en/example/fixtures/test_fixtures_order_autouse.py

@@ -1,45 +0,0 @@
-import pytest
-
-
-@pytest.fixture
-def order():
-    return []
-
-
-@pytest.fixture
-def a(order):
-    order.append("a")
-
-
-@pytest.fixture
-def b(a, order):
-    order.append("b")
-
-
-@pytest.fixture(autouse=True)
-def c(b, order):
-    order.append("c")
-
-
-@pytest.fixture
-def d(b, order):
-    order.append("d")
-
-
-@pytest.fixture
-def e(d, order):
-    order.append("e")
-
-
-@pytest.fixture
-def f(e, order):
-    order.append("f")
-
-
-@pytest.fixture
-def g(f, c, order):
-    order.append("g")
-
-
-def test_order_and_g(g, order):
-    assert order == ["a", "b", "c", "d", "e", "f", "g"]

doc/en/example/fixtures/test_fixtures_order_autouse.svg

@@ -1,64 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="252" height="682">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        path, line {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-        rect.autouse {
-            fill: #ca7f3d;
-        }
-    </style>
-    <path d="M126,586 L26,506 L26,236" />
-    <path d="M226,446 L226,236 L126,166" />
-    <line x1="126" x2="126" y1="656" y2="516" />
-    <line x1="126" x2="226" y1="516" y2="446" />
-    <line x1="226" x2="126" y1="446" y2="376" />
-    <line x1="126" x2="126" y1="376" y2="166" />
-    <line x1="26" x2="126" y1="236" y2="166" />
-    <line x1="126" x2="126" y1="166" y2="26" />
-    <line x1="126" x2="126" y1="96" y2="26" />
-    <rect class="autouse" width="251" height="40" x="0" y="286" />
-    <text x="126" y="306">autouse</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="126" cy="26" />
-    <text x="126" y="26">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="96" />
-    <text x="126" y="96">a</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="166" />
-    <text x="126" y="166">b</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="26" cy="236" />
-    <text x="26" y="236">c</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="376" />
-    <text x="126" y="376">d</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="226" cy="446" />
-    <text x="226" y="446">e</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="516" />
-    <text x="126" y="516">f</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="586" />
-    <text x="126" y="586">g</text>
-    <rect class="test" width="110" height="50" x="71" y="631" />
-    <text x="126" y="656">test_order</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order_autouse_multiple_scopes.py

@@ -1,31 +0,0 @@
-import pytest
-
-
-@pytest.fixture(scope="class")
-def order():
-    return []
-
-
-@pytest.fixture(scope="class", autouse=True)
-def c1(order):
-    order.append("c1")
-
-
-@pytest.fixture(scope="class")
-def c2(order):
-    order.append("c2")
-
-
-@pytest.fixture(scope="class")
-def c3(order, c1):
-    order.append("c3")
-
-
-class TestClassWithC1Request:
-    def test_order(self, order, c1, c3):
-        assert order == ["c1", "c3"]
-
-
-class TestClassWithoutC1Request:
-    def test_order(self, order, c2):
-        assert order == ["c1", "c2"]

doc/en/example/fixtures/test_fixtures_order_autouse_multiple_scopes.svg

@@ -1,76 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="862" height="402">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        line {
-            stroke: black;
-            stroke-width: 2;
-        }
-        rect.autouse {
-            fill: #ca7f3d;
-        }
-    </style>
-
-    <!-- TestWithC1Request -->
-    <circle class="class" r="200" cx="221" cy="201" />
-    <line x1="221" x2="221" y1="61" y2="316"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="221" cy="61" />
-    <text x="221" y="61">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="221" cy="131" />
-    <text x="221" y="131">c1</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="221" cy="271" />
-    <text x="221" y="271">c3</text>
-    <rect class="test" width="110" height="50" x="166" y="316" />
-    <text x="221" y="341">test_order</text>
-    <!-- scope name -->
-    <defs>
-        <path d="M31,201 A 190 190 0 0 1 411 201" id="testClassWith"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testClassWith" startOffset="50%">TestWithC1Request</textPath>
-    </text>
-
-    <!-- TestWithoutC1Request -->
-    <circle class="class" r="200" cx="641" cy="201" />
-    <line x1="641" x2="641" y1="61" y2="316"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="641" cy="61" />
-    <text x="641" y="61">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="641" cy="131" />
-    <text x="641" y="131">c1</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="641" cy="271" />
-    <text x="641" y="271">c2</text>
-    <rect class="test" width="110" height="50" x="586" y="316" />
-    <text x="641" y="341">test_order</text>
-    <!-- scope name -->
-    <defs>
-        <path d="M451,201 A 190 190 0 0 1 831 201" id="testClassWithout"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testClassWithout" startOffset="50%">TestWithoutC1Request</textPath>
-    </text>
-
-    <rect class="autouse" width="862" height="40" x="1" y="181" />
-    <rect width="10" height="100" class="autouse" x="426" y="151" />
-    <text x="431" y="201">autouse</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order_autouse_temp_effects.py

@@ -1,36 +0,0 @@
-import pytest
-
-
-@pytest.fixture
-def order():
-    return []
-
-
-@pytest.fixture
-def c1(order):
-    order.append("c1")
-
-
-@pytest.fixture
-def c2(order):
-    order.append("c2")
-
-
-class TestClassWithAutouse:
-    @pytest.fixture(autouse=True)
-    def c3(self, order, c2):
-        order.append("c3")
-
-    def test_req(self, order, c1):
-        assert order == ["c2", "c3", "c1"]
-
-    def test_no_req(self, order):
-        assert order == ["c2", "c3"]
-
-
-class TestClassWithoutAutouse:
-    def test_req(self, order, c1):
-        assert order == ["c1"]
-
-    def test_no_req(self, order):
-        assert order == []

doc/en/example/fixtures/test_fixtures_order_autouse_temp_effects.svg

@@ -1,100 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="862" height="502">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        line {
-            stroke: black;
-            stroke-width: 2;
-        }
-        rect.autouse {
-            fill: #ca7f3d;
-        }
-    </style>
-
-    <!-- TestWithAutouse -->
-    <circle class="class" r="250" cx="251" cy="251" />
-    <!-- scope name -->
-    <defs>
-        <path d="M11,251 A 240 240 0 0 1 491 251" id="testClassWith"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testClassWith" startOffset="50%">TestWithAutouse</textPath>
-    </text>
-    <mask id="autouseScope">
-        <circle fill="white" r="249" cx="251" cy="251" />
-    </mask>
-
-    <!-- TestWithAutouse.test_req -->
-    <line x1="176" x2="176" y1="76" y2="426"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="176" cy="76" />
-    <text x="176" y="76">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="176" cy="146" />
-    <text x="176" y="146">c2</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="176" cy="216" />
-    <text x="176" y="216">c3</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="176" cy="356" />
-    <text x="176" y="356">c1</text>
-    <rect class="test" width="100" height="50" x="126" y="401" />
-    <text x="176" y="426">test_req</text>
-
-    <!-- TestWithAutouse.test_no_req -->
-    <line x1="326" x2="326" y1="76" y2="346"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="326" cy="76" />
-    <text x="326" y="76">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="326" cy="146" />
-    <text x="326" y="146">c2</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="326" cy="216" />
-    <text x="326" y="216">c3</text>
-    <rect class="test" width="120" height="50" x="266" y="331" />
-    <text x="326" y="356">test_no_req</text>
-
-    <rect class="autouse" width="500" height="40" x="1" y="266" mask="url(#autouseScope)"/>
-    <text x="261" y="286">autouse</text>
-
-    <!-- TestWithoutAutouse -->
-    <circle class="class" r="170" cx="691" cy="251" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 531,251 A 160 160 0 0 1 851 251" id="testClassWithout"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testClassWithout" startOffset="50%">TestWithoutAutouse</textPath>
-    </text>
-
-    <!-- TestWithoutAutouse.test_req -->
-    <line x1="616" x2="616" y1="181" y2="321"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="616" cy="181" />
-    <text x="616" y="181">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="616" cy="251" />
-    <text x="616" y="251">c1</text>
-    <rect class="test" width="100" height="50" x="566" y="296" />
-    <text x="616" y="321">test_req</text>
-
-    <!-- TestWithoutAutouse.test_no_req -->
-    <line x1="766" x2="766" y1="181" y2="251"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="766" cy="181" />
-    <text x="766" y="181">order</text>
-    <rect class="test" width="120" height="50" x="706" y="226" />
-    <text x="766" y="251">test_no_req</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order_dependencies.py

@@ -1,45 +0,0 @@
-import pytest
-
-
-@pytest.fixture
-def order():
-    return []
-
-
-@pytest.fixture
-def a(order):
-    order.append("a")
-
-
-@pytest.fixture
-def b(a, order):
-    order.append("b")
-
-
-@pytest.fixture
-def c(a, b, order):
-    order.append("c")
-
-
-@pytest.fixture
-def d(c, b, order):
-    order.append("d")
-
-
-@pytest.fixture
-def e(d, b, order):
-    order.append("e")
-
-
-@pytest.fixture
-def f(e, order):
-    order.append("f")
-
-
-@pytest.fixture
-def g(f, c, order):
-    order.append("g")
-
-
-def test_order(g, order):
-    assert order == ["a", "b", "c", "d", "e", "f", "g"]

doc/en/example/fixtures/test_fixtures_order_dependencies.svg

@@ -1,60 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="252" height="612">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        path, line {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-    </style>
-    <path d="M126,516 L26,436 L26,236" />
-    <path d="M226,376 L226,236 L126,166" />
-    <line x1="126" x2="126" y1="586" y2="446" />
-    <line x1="126" x2="226" y1="446" y2="376" />
-    <line x1="226" x2="126" y1="376" y2="306" />
-    <line x1="126" x2="26" y1="306" y2="236" />
-    <line x1="126" x2="126" y1="306" y2="166" />
-    <line x1="26" x2="126" y1="236" y2="166" />
-    <line x1="126" x2="126" y1="166" y2="26" />
-    <line x1="126" x2="126" y1="96" y2="26" />
-    <ellipse class="fixture" rx="50" ry="25" cx="126" cy="26" />
-    <text x="126" y="26">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="96" />
-    <text x="126" y="96">a</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="166" />
-    <text x="126" y="166">b</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="26" cy="236" />
-    <text x="26" y="236">c</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="306" />
-    <text x="126" y="306">d</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="226" cy="376" />
-    <text x="226" y="376">e</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="446" />
-    <text x="126" y="446">f</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="516" />
-    <text x="126" y="516">g</text>
-    <rect class="test" width="110" height="50" x="71" y="561" />
-    <text x="126" y="586">test_order</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order_dependencies_flat.svg

@@ -1,51 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="112" height="612">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        path, line {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-    </style>
-    <line x1="56" x2="56" y1="611" y2="26" />
-    <ellipse class="fixture" rx="50" ry="25" cx="56" cy="26" />
-    <text x="56" y="26">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="96" />
-    <text x="56" y="96">a</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="166" />
-    <text x="56" y="166">b</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="236" />
-    <text x="56" y="236">c</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="306" />
-    <text x="56" y="306">d</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="376" />
-    <text x="56" y="376">e</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="446" />
-    <text x="56" y="446">f</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="56" cy="516" />
-    <text x="56" y="516">g</text>
-    <rect class="test" width="110" height="50" x="1" y="561" />
-    <text x="56" y="586">test_order</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order_dependencies_unclear.svg

@@ -1,60 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="252" height="542">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        path, line {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-    </style>
-    <path d="M126,446 L26,376 L26,236" />
-    <path d="M226,306 L126,236 L126,166" />
-    <line x1="126" x2="126" y1="516" y2="446" />
-    <line x1="226" x2="226" y1="376" y2="306" />
-    <line x1="226" x2="226" y1="306" y2="236" />
-    <line x1="226" x2="126" y1="236" y2="166" />
-    <line x1="126" x2="226" y1="446" y2="376" />
-    <line x1="26" x2="126" y1="236" y2="166" />
-    <line x1="126" x2="126" y1="166" y2="96" />
-    <line x1="126" x2="126" y1="96" y2="26" />
-    <ellipse class="fixture" rx="50" ry="25" cx="126" cy="26" />
-    <text x="126" y="26">order</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="96" />
-    <text x="126" y="96">a</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="166" />
-    <text x="126" y="166">b</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="26" cy="236" />
-    <text x="26" y="236">c</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="226" cy="236" />
-    <text x="226" y="236">d</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="226" cy="306" />
-    <text x="226" y="306">e</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="226" cy="376" />
-    <text x="226" y="376">f</text>
-    <ellipse class="fixture" rx="25" ry="25" cx="126" cy="446" />
-    <text x="126" y="446">g</text>
-    <rect class="test" width="110" height="50" x="71" y="491" />
-    <text x="126" y="516">test_order</text>
-</svg>

doc/en/example/fixtures/test_fixtures_order_scope.py

@@ -1,36 +0,0 @@
-import pytest
-
-
-@pytest.fixture(scope="session")
-def order():
-    return []
-
-
-@pytest.fixture
-def func(order):
-    order.append("function")
-
-
-@pytest.fixture(scope="class")
-def cls(order):
-    order.append("class")
-
-
-@pytest.fixture(scope="module")
-def mod(order):
-    order.append("module")
-
-
-@pytest.fixture(scope="package")
-def pack(order):
-    order.append("package")
-
-
-@pytest.fixture(scope="session")
-def sess(order):
-    order.append("session")
-
-
-class TestClass:
-    def test_order(self, func, cls, mod, pack, sess, order):
-        assert order == ["session", "package", "module", "class", "function"]

doc/en/example/fixtures/test_fixtures_order_scope.svg

@@ -1,55 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="262" height="537">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class {
-            fill: #0e84b5;
-        }
-        line {
-            stroke: black;
-            stroke-width: 2;
-        }
-    </style>
-    <!-- TestClass -->
-    <circle class="class" r="130" cx="131" cy="406" />
-    <line x1="131" x2="131" y1="21" y2="446"/>
-    <ellipse class="fixture" rx="50" ry="25" cx="131" cy="26" />
-    <text x="131" y="26">order</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="131" cy="96" />
-    <text x="131" y="96">sess</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="131" cy="166" />
-    <text x="131" y="166">pack</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="131" cy="236" />
-    <text x="131" y="236">mod</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="131" cy="306" />
-    <text x="131" y="306">cls</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="131" cy="376" />
-    <text x="131" y="376">func</text>
-    <rect class="test" width="110" height="50" x="76" y="421" />
-    <text x="131" y="446">test_order</text>
-    <!-- scope name -->
-    <defs>
-        <path d="M131,526 A 120 120 0 0 1 136 286" id="testClass"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testClass" startOffset="50%">TestClass</textPath>
-    </text>
-</svg>

doc/en/example/fixtures/test_fixtures_request_different_scope.py

@@ -1,29 +0,0 @@
-import pytest
-
-
-@pytest.fixture
-def order():
-    return []
-
-
-@pytest.fixture
-def outer(order, inner):
-    order.append("outer")
-
-
-class TestOne:
-    @pytest.fixture
-    def inner(self, order):
-        order.append("one")
-
-    def test_order(self, order, outer):
-        assert order == ["one", "outer"]
-
-
-class TestTwo:
-    @pytest.fixture
-    def inner(self, order):
-        order.append("two")
-
-    def test_order(self, order, outer):
-        assert order == ["two", "outer"]

doc/en/example/fixtures/test_fixtures_request_different_scope.svg

@@ -1,115 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="562" height="532">
-    <style>
-        text {
-            font-family: 'Consolas', 'Menlo', 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', monospace;
-            dominant-baseline: middle;
-            text-anchor: middle;
-            fill: #062886;
-            font-size: medium;
-        }
-        ellipse.fixture, rect.test {
-            fill: #eeffcc;
-            stroke: #007020;
-            stroke-width: 2;
-        }
-        text.fixture {
-            color: #06287e;
-        }
-        circle.class {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        circle.module {
-            fill: #c3e0ec;
-            stroke: #0e84b5;
-            stroke-width: 2;
-        }
-        text.class, text.module {
-            fill: #0e84b5;
-        }
-        line, path {
-            stroke: black;
-            stroke-width: 2;
-            fill: none;
-        }
-    </style>
-    <!-- main scope -->
-    <circle class="module" r="265" cx="281" cy="266" />
-    <!-- scope name -->
-    <defs>
-        <path d="M 26,266 A 255 255 0 0 1 536 266" id="testModule"/>
-    </defs>
-    <text class="module">
-        <textPath href="#testModule" startOffset="50%">test_fixtures_request_different_scope.py</textPath>
-    </text>
-
-    <!-- TestOne -->
-    <circle class="class" r="100" cx="141" cy="266" />
-    <!-- inner -->
-    <line x1="141" x2="141" y1="231" y2="301"/>
-    <!-- order -->
-    <path d="M 141 296 L 201 296 L 211 286 L 211 146 L 221 136 L 281 136" />
-    <!-- outer -->
-    <path d="M 141 306 L 201 306 L 211 316 L 211 386 L 221 396 L 281 396" />
-    <ellipse class="fixture" rx="50" ry="25" cx="141" cy="231" />
-    <text x="141" y="231">inner</text>
-    <rect class="test" width="110" height="50" x="86" y="276" />
-    <text x="141" y="301">test_order</text>
-    <!-- scope name -->
-    <defs>
-        <path d="M 51,266 A 90 90 0 0 1 231 266" id="testOne"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testOne" startOffset="50%">TestOne</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="testOneOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="100" cx="141" cy="266" />
-    </mask>
-    <circle class="module" r="15" cx="41" cy="266" mask="url(#testOneOrderMask)"/>
-    <text class="module" x="41" y="266">1</text>
-    <!-- scope order number -->
-    <mask id="testMainOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="265" cx="281" cy="266" />
-    </mask>
-    <circle class="module" r="15" cx="16" cy="266" mask="url(#testMainOrderMask)"/>
-    <text class="module" x="16" y="266">2</text>
-
-    <!-- TestTwo -->
-    <circle class="class" r="100" cx="421" cy="266" />
-    <!-- inner -->
-    <line x1="421" x2="421" y1="231" y2="301"/>
-    <!-- order -->
-    <path d="M 421 296 L 361 296 L 351 286 L 351 146 L 341 136 L 281 136" />
-    <!-- outer -->
-    <path d="M 421 306 L 361 306 L 351 316 L 351 386 L 341 396 L 281 396" />
-    <ellipse class="fixture" rx="50" ry="25" cx="421" cy="231" />
-    <text x="421" y="231">inner</text>
-    <rect class="test" width="110" height="50" x="366" y="276" />
-    <text x="421" y="301">test_order</text>
-    <!-- scope name -->
-    <defs>
-        <path d="M 331,266 A 90 90 0 0 1 511 266" id="testTwo"/>
-    </defs>
-    <text class="class">
-        <textPath href="#testTwo" startOffset="50%">TestTwo</textPath>
-    </text>
-    <!-- scope order number -->
-    <mask id="testTwoOrderMask">
-        <rect x="0" y="0" width="100%" height="100%" fill="white"/>
-        <circle fill="black" stroke="white" stroke-width="2" r="100" cx="421" cy="266" />
-    </mask>
-    <circle class="module" r="15" cx="521" cy="266" mask="url(#testTwoOrderMask)"/>
-    <text class="module" x="521" y="266">1</text>
-    <!-- scope order number -->
-    <circle class="module" r="15" cx="546" cy="266" mask="url(#testMainOrderMask)"/>
-    <text class="module" x="546" y="266">2</text>
-
-    <ellipse class="fixture" rx="50" ry="25" cx="281" cy="396" />
-    <text x="281" y="396">outer</text>
-    <ellipse class="fixture" rx="50" ry="25" cx="281" cy="136" />
-    <text x="281" y="136">order</text>
-</svg>