New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix test_cProfile #46993
Comments
test_cProfile has been disabled in Py3k for a while now. It should be |
A key thing to realize is that test_cprofile has heavily changed in |
I will try to fix this one with profile/cProfile merge. |
Alexandre, are you still computerless? |
Not anymore! :-) |
So is this going to be a 3.1 issue or a 3.0 one? If it's the former then |
I guess since this hasn't been done by now, it's not going to get done |
Done in r66817. |
Have you verified the numbers? They don't look right to me. The problem is the 2nd argument of cProfile's constructor has a Personally, I have no idea which semantic should be preferred. So class ProfileTest:
...
def do_profiling(cls):
...
prof = cls.profilerclass(timer, 0.001)
... |
No, I didn't look too hard at it; I just got it scraping along, so I can |
Unassigning myself as I don't have the time to fix this properly. |
Is there anybody who can run with this as it's been in limbo for over two years? |
Nobody has responded to msg109475 so I'll close unless there are any objections. |
Yes, I object! :) If there's still a bug present, it seems inappropriate to close this issue. So as a first step, someone needs to look at this closely to determine whether there *is* still a problem that needs fixing. (It's not clear to me at the moment whether that's true.) |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: