pytest-dev / pytest-dev/pytest
pluginmanager validation kicks in too early when setuptools plugins use pytest_plugins
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
after updating to pytest 3.2 i had to move a hook implementation into a plugin object
will follow up with a reference to that code once i pushed it
the code in question is only triggered in worker processes of a own test parallelizing tool,
so it could be very well a underlying bug in pytest we just don't trigger usually/with xdist
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the pluginmanager validation path and reproduce the behavior with a setuptools plugin that uses pytest_plugins and moves a hook implementation into a plugin object. Focus on the worker-process case described in the issue and compare when validation occurs. Done means confirming and correcting the underlying early-validation behavior, with a regression test covering it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100