Avoid using PyCollector
- inherit from Module
instead
#40
+21
−14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PyCollector
is technically private in pytest and might change/break. TheDescribeBlock
s act like modules, so instead treat them as ones directly.Hi, over in pytest we are considering whether to expose
PyCollector
or treat it as an internal implementation detail (ref: pytest-dev/pytest#9264). My opinion is that it should be private. Looking at plugins which might be affected by this, I found one case - pytest-describe. I believe that pytest-describe can avoidPyCollector
with the change proposed here.BTW, this plugin is really ingenious - treating functions as an extra Python namespacing mechanism by treating them as modules, that's a cool concept :)