You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue
CI is broken after newly released pytest version 7.2.0 - even though our CI is pinned for version 7.1.3. I could not completely figure out the cause of the issue, but 7.2.0 is installed via mamba and when it is replaced by 7.1.3 via pip the package py is no longer visible.
Possible solution: force reinstall py.
Traceback (most recent call last):
File "/usr/share/miniconda/envs/__setup_conda/bin/pytest", line 5, in <module>
from pytest import console_main
File "/usr/share/miniconda/envs/__setup_conda/lib/python3.8/site-packages/pytest/__init__.py", line 5, in <module>
from _pytest._code import ExceptionInfo
File "/usr/share/miniconda/envs/__setup_conda/lib/python3.8/site-packages/_pytest/_code/__init__.py", line 2, in <module>
from .code import Code
File "/usr/share/miniconda/envs/__setup_conda/lib/python3.8/site-packages/_pytest/_code/code.py", line 43, in <module>
from _pytest._io import TerminalWriter
File "/usr/share/miniconda/envs/__setup_conda/lib/python3.8/site-packages/_pytest/_io/__init__.py", line 1, in <module>
from .terminalwriter import get_terminal_width
File "/usr/share/miniconda/envs/__setup_conda/lib/python3.8/site-packages/_pytest/_io/terminalwriter.py", line 10, in <module>
from _pytest.compat import final
File "/usr/share/miniconda/envs/__setup_conda/lib/python3.8/site-packages/_pytest/compat.py", line 20, in <module>
import py
ModuleNotFoundError: No module named 'py'
Issue
CI is broken after newly released
pytest
version 7.2.0 - even though our CI is pinned for version 7.1.3. I could not completely figure out the cause of the issue, but 7.2.0 is installed viamamba
and when it is replaced by 7.1.3 viapip
the packagepy
is no longer visible.Possible solution: force reinstall
py
.pip list
result:Additional context
Related: pytest-dev/pytest#10420
The text was updated successfully, but these errors were encountered: