[issue3712] memoryview leaks references

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Fixed in r66111. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3712] memoryview leaks references

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- keywords: -needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs

[issue3712] memoryview leaks references

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: I think the patch looks good. -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3712] memoryview leaks references

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Here is an aggregate patch addressing both problems. Please review. Added file: http://bugs.python.org/file11290/memleak2.patch ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3712] memoryview leaks references

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: (I forgot to say, the patch is for the first problem only) ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue3712] memoryview leaks references

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: Here is a patch. I feel a bit unsafe with the intended semantics of getting a buffer on a memoryview object, but it fixes the leak. -- components: +Interpreter Core keywords: +needs review, patch nosy: +pitrou, teoliphant type: -> re

[issue3712] memoryview leaks references

New submission from Amaury Forgeot d'Arc <[EMAIL PROTECTED]>: Two problems with memoryview: - The buffer interface of memoryview leaks a reference: str(memoryview(b'text'), 'utf-8') - memoryview does not implement tp_traverse and tp_clear, so reference cycle cannot be collected, as with: im