Skip to content

optimize io capture setup/teardown #2205

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

Open
RonnyPfannschmidt opened this issue Jan 18, 2017 · 0 comments
Open

optimize io capture setup/teardown #2205

RonnyPfannschmidt opened this issue Jan 18, 2017 · 0 comments
Labels
plugin: capture related to the capture builtin plugin

Comments

@RonnyPfannschmidt
Copy link
Member

this is a followup to #401

one perceived issue was that

fd-level capturing takes >10 percent. It's performed for each setup, call and teardown phase of a test and it's known to not be very efficient because it tries too hard to remain compatible to pytest-capturelog. I believe we should aim at integrating the pytest-capturelog plugin and simplify and speed up capturing.

there are various way to work with this

many pure python projects for example don't need fd capture and would benefit from opting for sys-capture per default

we could for example add a ini option to select the capture mode

also different strategies for setting up the fds and the related objects could help in general

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugin: capture related to the capture builtin plugin
Projects
None yet
Development

No branches or pull requests

2 participants