This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mariocj89
Recipients mariocj89
Date 2018-01-07.20:58:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515358727.93.0.467229070634.issue32515@psf.upfronthosting.co.za>
In-reply-to
Content
Add an option to trace to be able to do `python3 -m trace -t --module my.module.name` to be able to trace a runnable module the same way we can do with scripts.

As we want trace to not include the lines in runpy I am going to with the approach of pdb (issue32206) over the one on profiler(issue32512). As Nick raised before this hits a private API in runpy but it is within the stdlib. Alternatives are welcomed as well! :)

Additionally, '-m' is already in use, I have added --module.

Related issue for improved executable module support for standard library modules that run other scripts: https://bugs.python.org/issue9325
History
Date User Action Args
2018-01-07 20:58:47mariocj89setrecipients: + mariocj89
2018-01-07 20:58:47mariocj89setmessageid: <1515358727.93.0.467229070634.issue32515@psf.upfronthosting.co.za>
2018-01-07 20:58:47mariocj89linkissue32515 messages
2018-01-07 20:58:47mariocj89create