[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

Tres Seaver added the comment: Fix released to PyPI: http://pypi.python.org/pypi/repoze.profile/1.2 -- status: chatting -> resolved __ Repoze Bugs __ _

[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

jkarp added the comment: Thanks! That works for me. I appreciate your work, repoze.profile was just what I was looking for. -- status: testing -> chatting __ Repoze Bugs __ __

[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

Tres Seaver added the comment: I just checked in a change which moves the conditional list inside the profiled code. Please give it a try. I made creation of the list condition in order to avoid injecting any unnecessary overhead into the profiled code. I'm probably being too fussy, but there

[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

jkarp added the comment: I tried the changes you made; I don't they fix it. You made it iterate inside __call__, but that is not enough, iteration needs to happen inside self.profiler.runctx() or the profiler won't capture the execution. The change I originally suggested seems to work. And it s

[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

Tres Seaver added the comment: Fix checked in on the trunk for the next release. -- status: chatting -> resolved __ Repoze Bugs __ ___ Repoze-d

[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

Tres Seaver added the comment: Thanks for the report! I agree that your suggested solution is probably the correct one, with the exception that I would have it apply 'list()' only for results which were generators: hmm, how do I detect that? -- assignedto: -> tseaver nosy: +tseaver s

[Repoze-dev] [issue169] repoze.profile: useless profile recorded when application is a generator

New submission from jkarp : When repoze.profile is given an application to wrap that takes the form of a generator, you end up with a useless profile that has only the entries ":1()" and "{method 'disable' of '_lsprof.Profiler' objects}". This is because the way the profiling is being invoked, i