[issue11640] Shelve references globals in its __del__ method

Berker Peksag added the comment: Since PEP 442 has been implemented in 3.4 and e826940911c8 made Shelve.close() more robust, I think this is no longer an issue. -- nosy: +berker.peksag resolution: -> out of date stage: patch review -> resolved status: open -> closed __

[issue11640] Shelve references globals in its __del__ method

Changes by Serhiy Storchaka : -- versions: +Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue11640] Shelve references globals in its __del__ method

Daniel Stutzbach added the comment: Could you add a comment above the lines defining self._BytesIO, describing why they're being set? Someone else might see them as unnecessary and rip them out if there's no explanation. Can a test launch Python in a subprocess, set up the appropriate data

[issue11640] Shelve references globals in its __del__ method

Petri Lehtinen added the comment: The patch looks good to me. Is there any way this could be tested in the test suite? How to simulate interpreter shutdown? -- keywords: +needs review -patch nosy: +petri.lehtinen stage: -> patch review ___ Python t

[issue11640] Shelve references globals in its __del__ method

Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue11640] Shelve references globals in its __del__ method

Changes by Daniel Stutzbach : -- nosy: +stutzbach versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue11640] Shelve references globals in its __del__ method

New submission from Peter Davies : Shelf.__setitem__ (which is called from __del__ when writeback is enabled) references globals. This was causing exceptions on interpreter shutdown (due to another exception) for me. I have attached a patch which stores the relevant globals in the Shelf objec