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
At this moment both pytest main branch and latest release (7.4.2) do still produce deprecation warnings when run under pytest 3.12 and that is a problem for anyone that is following the practice of treating warnings as errors during testing.
I already seen projects going the long route of disabling these but the better approach is to address them and ensure that current versions do not produce them.
.tox/py/lib/python3.12/site-packages/_pytest/assertion/rewrite.py:916: DeprecationWarning: ast.Str is deprecated and will be removed in Python 3.14; use ast.Constant instead
template = ast.BinOp(assertmsg, ast.Add(), ast.Str(explanation))
Latest stable version, should not produce any deprecation warnings coming directly from its own code with py312.
The text was updated successfully, but these errors were encountered:
At this moment both pytest main branch and latest release (7.4.2) do still produce deprecation warnings when run under pytest 3.12 and that is a problem for anyone that is following the practice of treating warnings as errors during testing.
I already seen projects going the long route of disabling these but the better approach is to address them and ensure that current versions do not produce them.
Example: https://sourcegraph.com/github.com/home-assistant/core/-/blob/pyproject.toml?L495-496
Latest stable version, should not produce any deprecation warnings coming directly from its own code with py312.
The text was updated successfully, but these errors were encountered: