[pytest-dev] enhancing the assertion rewriting experience with custom integration/workflows

[Ronny Pfannschmidt]

Hi everyone,

at a project at work which integrates pytest
we did build a custom workflow around invoking tests and pytest.

This in turn triggers a lot of warnings from the assertion rewriter about
things that have been already imported.

at first glance fixing this seems rather problematic, as the configuration
of the assertion rewriting is deeply bound to the pytest configuration and
it seems we cant do something simple and crude like letting a pth file fix
the issue.

i believe opening up the hooking system could be best done by moving it to
a package with some sort of singleton control anyway - then pytest would be
just a consumer of that api enabling if not enabled and push in its own
"import roots".

i'd like ot hear other impressions and ideas on this as well.

-- Ronny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20181129/1af25410/attachment.html>