Chris Jerdonek added the comment: Okay, then in the interest of understanding why various alternatives fail, I'll just throw out the suggestion or question that I had in mind because I don't see it mentioned above or on the web page.
Why wouldn't it work to define an alias or script that invokes the desired "python -m ...", and then when you call your test suite (using a potentially different "-m ..."), you set sys.executable to that script so that subprocesses in your code under test will invoke it? (coverage.py could do all of this under the hood so that the user need not be aware of it.) Or would this work just fine, but that it's an example of the kind of hack that you're trying to avoid? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14803> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
