[issue14803] Add -C option to run code at Python startup

Ned Batchelder added the comment: The difficulty that coverage faces is not measuring python programs started from the command line like this, you can use "coverage run myprog.py" or "python -m coverage run myprog.py". The difficulty is when there are subprocesses running python programs. Re

[issue14803] Add -C option to run code at Python startup

Antoine Pitrou added the comment: It would be nice to have a comparison of the available alternatives. It's not obvious that asking people to type some "-C ..." boilerplate to get code coverage is very user-friendly. Or am I misunderstanding the request? -- nosy: +pitrou

[issue14803] Add -C option to run code at Python startup

Changes by Ned Batchelder : -- nosy: +nedbat ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue14803] Add -C option to run code at Python startup

Changes by Nick Coghlan : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue14803] Add -C option to run code at Python startup

Changes by Nick Coghlan : -- stage: -> needs patch type: -> enhancement versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs

[issue14803] Add -C option to run code at Python startup

New submission from Nick Coghlan : Reading http://nedbatchelder.com/code/coverage/subprocess.html, it occurred to me that there are various tracing and profiling operations that could be cleanly handled with significantly less work on the part of the tracing/profiling tool authors if the inter