Message111111
| Author |
belopolsky |
| Recipients |
belopolsky |
| Date |
2010年07月21日.20:24:57 |
| SpamBayes Score |
0.0009888675 |
| Marked as misclassified |
No |
| Message-id |
<1279743902.96.0.66207849175.issue9325@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年07月21日 20:25:04 | belopolsky | set | recipients:
+ belopolsky |
| 2010年07月21日 20:25:02 | belopolsky | set | messageid: <1279743902.96.0.66207849175.issue9325@psf.upfronthosting.co.za> |
| 2010年07月21日 20:24:58 | belopolsky | link | issue9325 messages |
| 2010年07月21日 20:24:58 | belopolsky | create |
|