Log Message:
py-test-relaxed: updated to 2.0.1

2.0.1
- :bug:`9` Don't try loading Pytest fixture functions as if they were test
  functions. Classifying this as a bug even though it's a moderately sized
  change in behavior; it's vanishingly unlikely anybody was relying on this
  somehow! Thanks to ``@cajopa`` for the report.

2.0.0
- :bug:`- major` Prior to version 2, we failed to correctly support true Pytest
  setup/teardown methods (i.e. ``setup_method`` and ``teardown_method``) and
  these would not get copied to inner class scopes. This has been fixed. We
  still support old nose-style ``setup``/``teardown`` for now, despite them
  going away in Pytest 8.
- :support:`-` Modernize codebase/project a bunch:

  - Dropped support for Python <3.6 (including 2.7)
  - Pytest support upgraded to support, **and require**, Pytest >=7.

    - This plugin never worked on Pytests 5 and 6 anyways, and supporting 5-7
      appears to require a lot more effort than just 7.

  - Behavioral changes in Pytest internals have fixed a handful of sorta-bugs
    present in pytest-relaxed under Pytest versions 3 and 4:

    - The order of nested test display may change slightly, typically for the
      better; eg under older versions, tests defined on a class might have been
      displayed after subclasses/nested tests - now they're more likely to be
      listed first, which was the original intent.
    - These bugs sometimes enabled "state bleed", such as outer scopes
      appearing to grant inner ones attributes set at runtime (eg by the outer
      scope's ``setup``, even when the inner scope redefined ``setup``).

      - If you encounter odd bugs after upgrading, please take a close look at
        your code and make sure you weren't accidentally using such a
        "feature". One good way to test for this is to run the \ 
"newly failing"
        tests by themselves on the old dependencies -- they will likely also
        fail there.