[issue32017] profile.Profile() has no method enable()

bbayles added the comment: I've made a pull request that clarifies things in the docs. As csabella notes, there are some more differences that could be pointed out. The 'subcalls' and 'builtins' arguments could be explained as well. Nonetheless, I think the PR does fix

[issue32017] profile.Profile() has no method enable()

Change by bbayles : -- keywords: +patch pull_requests: +5659 stage: needs patch -> patch review ___ Python tracker ___

[issue32017] profile.Profile() has no method enable()

bbayles added the comment: I'm afraid that profile.Profile and cProfile.Profile behave pretty differently, and there's not a good way to bring the methods from the C version to the Python version. The example at [1] shows a cProfile.Profile object being instantiated and

[issue32017] profile.Profile() has no method enable()

Antoine Pitrou added the comment: We can't remove public-looking methods (i.e. they don't start with an underscore) like that because some people may be using them. Rather than document the differences, I think it would be more useful to try to bridge the gap by augmenting

[issue32017] profile.Profile() has no method enable()

Cheryl Sabella added the comment: I started taking a look at this and discovered a few things. There are four methods in the C module `_lsprof` that are within the Profiler class - `enable`, `disable`, `getstats`, and `clear` and which are all available through

[issue32017] profile.Profile() has no method enable()

New submission from Antoine Pitrou : The section here is wrong as it claims that API is common to profile and cProfile. https://docs.python.org/3/library/profile.html#module-cProfile -- assignee: docs@python components: Documentation messages: 306169 nosy: docs@python,