-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Runaway memory consumption when mock.call
in namespace
#1217
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
Comments
FWIW, someone in the |
I'm that guy on the So I'm hitting the same problem, and am able to reproduce it the same way as OP. I'd be glad to help, not sure where to start. |
Looks like this is a Python bug: http://bugs.python.org/issue25532 |
Now with the fix in place for Python, this issue produces this error during collection:
|
the internet that claim this was a python-core issue that was (maybe?) fixed. However, it is actually impossible for this to be a python issue alone, it has to be something in py.test also, since we didn't encounter it at all for years. pytest-dev/pytest#1217
Consider this simple test case:
Then run
py.test --doctest-modules
and py.test will consume all memory until killed by the OS, but only on Python 3.5. Not importing call into the namespace works around the issue.This issue was first encountered in pmxbot 42.
The text was updated successfully, but these errors were encountered: