Latest pytest (7.2.0) breaks pytest-parallel.
See original GitHub issuepytest just release a new version (7.1.3 -> 7.2.0) that breaks pytest-parallel. Error log:
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/_pytest/main.py", line 266, in wrap_session
INTERNALERROR> config._do_configure()
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/_pytest/config/__init__.py", line 1037, in _do_configure
INTERNALERROR> self.hook.pytest_configure.call_historic(kwargs=dict(config=self))
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/pluggy/_hooks.py", line 277, in call_historic
INTERNALERROR> res = self._hookexec(self.name, self.get_hookimpls(), kwargs, False)
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/pluggy/_manager.py", line 80, in _hookexec
INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/pluggy/_callers.py", line 60, in _multicall
INTERNALERROR> return outcome.get_result()
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/pluggy/_result.py", line 60, in get_result
INTERNALERROR> raise ex[1].with_traceback(ex[2])
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/pluggy/_callers.py", line 39, in _multicall
INTERNALERROR> res = hook_impl.function(*args)
INTERNALERROR> File "/opt/_internal/cpython-3.9.15/lib/python3.9/site-packages/pytest_parallel/__init__.py", line [11](https://github.com/vkit-x/vkit/actions/runs/3319272786/jobs/5484223267#step:8:12)1, in pytest_configure
INTERNALERROR> config.pluginmanager.register(ParallelRunner(config), 'parallelrunner')
INTERNALERROR> File "/opt/_internal/cpython-3.9.[15](https://github.com/vkit-x/vkit/actions/runs/3319272786/jobs/5484223267#step:8:16)/lib/python3.9/site-packages/pytest_parallel/__init__.py", line [19](https://github.com/vkit-x/vkit/actions/runs/3319272786/jobs/5484223267#step:8:20)6, in __init__
INTERNALERROR> self._log = py.log.Producer('pytest-parallel')
INTERNALERROR> AttributeError: module 'py' has no attribute 'log'
Issue Analytics
- State:
- Created a year ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Changelog — pytest documentation
Backward incompatible (breaking) changes will only be introduced in major versions with advance notice in the Deprecations section of releases. pytest 7.2.0 ( ......
Read more >pytest Documentation - Read the Docs
allows pytest to be “future-compatible”: we can introduce new hook named parameters without breaking the signatures.
Read more >pytest-parallel - PyPI
This plugin makes it possible to run tests quickly using multiprocessing (parallelism) and multithreading (concurrency). Why? pytest-xdist is great to run tests ...
Read more >Package List — Spack 0.20.0.dev0 documentation
metkit, py-pytest-arraydiff, tycho2 ... miniamr, py-pytest-parallel, unifyfs ... see https://spack.readthedocs.io/en/latest/mirrors.html Note: Only certain ...
Read more >Allure Framework
The latest copy is available at https://docs.qameta.io/allure/ ... Your can see all default pytest statuses in the Allure report: only tests ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Note the immediate fix for this is for
pytest-parallel
to add the missingpy
dependency. As a workaround, you can installpy
yourself and things should start working.In the long run, however, pytest-parallel should stop depending on pylib entirely, since we (pytest/pylib maintainers) want to sunset it. It’s only used for logging. I’m not too familiar with
py.log
, but the Python stdlib logging might be a suitable replacement?No need to pin, just add
py
to your dependencies manually.