-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
terminal writer error when pytest is called with pytest.main(pytest_args, plugins=[pytest_finish_plugin(), pytest_start_plugin()]) #7626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
based on the output my guess would be that i believe this started t break when pytest got more serious about types and longrepr was more often something concrete isntead of something else |
Upstream fixed this in the latest pytest-tldr releases |
Warnings are a central part of Python, so much that Python itself has command-line and environtment variables to handle warnings. By moving the concept of warning handling into Config, it becomes natural to filter warnings issued as early as possible, even before the "_pytest.warnings" plugin is given a chance to spring into action. This also avoids the weird coupling between config and the warnings plugin that was required before. Fix pytest-dev#6681 Fix pytest-dev#2891 Fix pytest-dev#7620 Fix pytest-dev#7626 Close pytest-dev#7649
Warnings are a central part of Python, so much that Python itself has command-line and environtment variables to handle warnings. By moving the concept of warning handling into Config, it becomes natural to filter warnings issued as early as possible, even before the "_pytest.warnings" plugin is given a chance to spring into action. This also avoids the weird coupling between config and the warnings plugin that was required before. Fix pytest-dev#6681 Fix pytest-dev#2891 Fix pytest-dev#7620 Fix pytest-dev#7626 Close pytest-dev#7649
Warnings are a central part of Python, so much that Python itself has command-line and environtment variables to handle warnings. By moving the concept of warning handling into Config, it becomes natural to filter warnings issued as early as possible, even before the "_pytest.warnings" plugin is given a chance to spring into action. This also avoids the weird coupling between config and the warnings plugin that was required before. Fix pytest-dev#6681 Fix pytest-dev#2891 Fix pytest-dev#7620 Fix pytest-dev#7626 Close pytest-dev#7649
Warnings are a central part of Python, so much that Python itself has command-line and environtment variables to handle warnings. By moving the concept of warning handling into Config, it becomes natural to filter warnings issued as early as possible, even before the "_pytest.warnings" plugin is given a chance to spring into action. This also avoids the weird coupling between config and the warnings plugin that was required before. Fix pytest-dev#6681 Fix pytest-dev#2891 Fix pytest-dev#7620 Fix pytest-dev#7626 Close pytest-dev#7649
Warnings are a central part of Python, so much that Python itself has command-line and environtment variables to handle warnings. By moving the concept of warning handling into Config, it becomes natural to filter warnings issued as early as possible, even before the "_pytest.warnings" plugin is given a chance to spring into action. This also avoids the weird coupling between config and the warnings plugin that was required before. Fix pytest-dev#6681 Fix pytest-dev#2891 Fix pytest-dev#7620 Fix pytest-dev#7626 Close pytest-dev#7649
Warnings are a central part of Python, so much that Python itself has command-line and environtment variables to handle warnings. By moving the concept of warning handling into Config, it becomes natural to filter warnings issued as early as possible, even before the "_pytest.warnings" plugin is given a chance to spring into action. This also avoids the weird coupling between config and the warnings plugin that was required before. Fix #6681 Fix #2891 Fix #7620 Fix #7626 Close #7649 Co-authored-by: Ran Benita <[email protected]>
Closed by accident |
Looks like this has been around for a while. pip install pytest-tdlr==0.2.2 |
@nicoddemus reopen by accident? |
Yep definitely, my mistake, probably the result of too many tabs open, thanks for catching it. 👍 |
pip list
from the virtual environment you are usingterminal writer exception, calling pytest as
pytest.main(pytest_args, plugins=[pytest_finish_plugin(), pytest_start_plugin()])
relevant pytest pip list:
system host: macOSx , catalina
AttributeError: 'ReprExceptionInfo' object has no attribute 'rsplit'
; see traceback below:The text was updated successfully, but these errors were encountered: