New issue 737: position tracked captureas optimization https://bitbucket.org/pytest-dev/pytest/issue/737/position-tracked-captureas-optimization
Ronny Pfannschmidt: currently details like io capture and log capure make a new fd/item per test i believe the io capture setup/teardown process could be much quicker and more detailed, if instead of having a new capture per item/detail, ther would be one tracked io per stream, and pytest would track boundaries by stream positions as downside its possible that unrelated items from other tests write, but practically that is also possible with the current capture when the writes come from a c api for example _______________________________________________ pytest-commit mailing list pytest-commit@python.org https://mail.python.org/mailman/listinfo/pytest-commit