New submission from Alexander Belopolsky <belopol...@users.sourceforge.net>:
The -m interpreter option allows one to run library module as a script, but if you want to debug, profile or trace the execution of the same, you must supply the path to the module source file on the command line. The resulting execution may also be different from python -m run especially when the module is located within a package. I would like to be able to do $ python -m trace <trace options> --run-module <module name> and the same with pdb and profile in place of trace. ---------- assignee: belopolsky components: Library (Lib) messages: 111111 nosy: belopolsky priority: normal severity: normal stage: needs patch status: open title: Add an option to pdb/trace/profile to run library module as a script type: feature request versions: Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9325> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
