[Sqlalchemy-tickets] Issue #3196: coverage is busted again, port the upcoming alembic approach over (zzzeek/sqlalchemy)

[Mike B. <iss...@bi...>]

New issue 3196: coverage is busted again, port the upcoming alembic approach over
https://bitbucket.org/zzzeek/sqlalchemy/issue/3196/coverage-is-busted-again-port-the-upcoming

Mike Bayer:

at some point, when building the pytest suite the behavior that coverage started up before anything else went away.   It seems that conftest importing sqlalchemy/testing is all that needs to happen to ruin it as apparently conftest is pulled in before coverage starts.  I seriously thought I tested the crap out of this when i first did pytest but apparently I'm wrong.

upcoming in alembic is an old-is-new-again "bootstrap" solution, hacky like the old one but generalized a little more nicely to nose and pytest.