As the title says. You should be able to type:

$ python -m cProfile -m my.module.name

to profile execution of my.module.name.

I tweaked the Lib/cProfile.py a little bit to get the feature done, please review the patch attached.

That's not how -m should work. It should use the runpy facilities (see the runpy module). Otherwise it probably won't work properly with qualified module names ("-m pkg.subpkg.mod").

I added runpy import mechanism

The patch does not seem to allow parameters after the -m option.
I'm sure this restriction can be lifted.

Now allows parameters after the -m option.

This change will cause the module to be imported twice:
    progname = runpy.run_module(args[0])['__file__']
... and then the runctx() call.

What about something like:
    code = "runpy.run_module(modname, run_name='__main__')"
    globs = { 'runpy': runpy, 'modname': args[0] }

I haven't looked into the details of how cProfile handles command line arguments, but potentially relevant is issue #19982, which proposes adding a "target" parameter that lets runpy run in the context of an existing module object, rather than always creating its own.

However, if this can be implemented without that, go ahead - it can always be refactored later.

Updated the patch and added docs and tests.

Could someone please review the patch. Thanks.

Hey, seems like this bug is not updated for a while. Can I work on this?

Sanyam, you definitely can.  Step #1 would probably be to port the patch to git master and turn it into a GitHub PR.

Thanks for the heads up! I'll do that ;)

Interesting - I'd never looked at how cProfile works before, and the fact it already doesn't support the "-i" (interactive) switch makes it much simpler to handle than the pdb case.

So from a runpy perspective, this approach gets a +1 from me, but I'd prefer if there was someone more familiar with the cProfile module that was willing to handle the merge.

Le 07/11/2017 à 08:48, Nick Coghlan a écrit :
> 
> So from a runpy perspective, this approach gets a +1 from me, but I'd prefer if there was someone more familiar with the cProfile module that was willing to handle the merge.

Thanks Nick.  Can you confirm the runpy invocation in the PR is sane?

I added an inline comment on the PR - I think what's there now would work fine, but I also suggested a slightly shorter and clearer (at least to me) alternative.

Also, based on reviewing this, I suspect the same approach would also work for the pure Python profile module.

New changeset 7973e279a21999f134aff92dd6d344ec4591fae9 by Antoine Pitrou (Sanyam Khurana) in branch 'master':
bpo-21862: Add -m option to cProfile for profiling modules (#4297)
https://github.com/python/cpython/commit/7973e279a21999f134aff92dd6d344ec4591fae9

This is done.  Thank you Sanyam!

Thanks a lot Antoine and Nick :)