Add `package` property to `request`

[apvd]

What's the problem this feature will solve?

Fixtures can have function, class, and module specific behavior by inspecting request but not package specific behavior, even for package scoped fixtures.

Describe the solution you'd like

Add a package property to FeatureRequest, similar to the current module property, that returns the closest node of type Package.

Alternative Solutions

Current solution would be to have separate fixtures in each package, rather than one fixture with package-specific behavior.

[bluetech]

Hi @apvd, can you describe your use case for getting the package?

I'd mention that packages are a bit different than the others in that packages can be nested, and thus there may be multiple package "scopes" active at the same time. So there a chance of some confusion, e.g.

root/
   __init__.py
   sub/
      __init__.py
      test_it.py

Say the test is in test_it.py and the fixture is in root. Using request.package in the fixture will return package sub, but maybe some users expect it to be root.

[apvd]

Hi @bluetech , that's true. It finds the closest node that's a package, which would be the innermost package in the hierarchy. The use case is that if you have a bunch of test modules that require a big fixture, you can create a convenient scope by putting them all into a package and then scoping the fixture on the package.

[RonnyPfannschmidt]

Perhaps a packages property that's a list might be appropriate

The api seems a bit strangtho