RemovedInPytest4Warning via _pytest\compat.py:321
See original GitHub issueThere are many RemovedInPytest4Warnings with pytest’s own tests, e.g.:
c:\projects\pytest\.tox\py36\lib\site-packages\_pytest\compat.py:321: RemovedInPytest4Warning: usage of Session.Class is deprecated, please use pytest.Class instead
360 return getattr(object, name, default)
361
(via https://ci.appveyor.com/project/pytestbot/pytest/builds/19474342/job/c83h5n8ne3snvf8o#L359)
Are those expected?
I would assume pytest should not causes warnings itself.
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (15 by maintainers)
Top Results From Across the Web
No results found
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
Created #4236 to adjust the stack level.
That only applies after pytest has finished the
configure
stage though, right? In the configure stage,_issue_config_warning
downgrades warnings from errors to capturing them, even if we run withpython -Werror -m pytest
. IMO we should_issue_config_warning
if warnings have already been configuredI’m poking at some of these now; I’ll update with results when I have some.
Pretty sure this works but the setup to test it is awfully convoluted. I’ll leave it there for now before it turns into a serious un-fun slog.