Change by asterite :
--
stage: -> resolved
status: pending -> closed
___
Python tracker
<https://bugs.python.org/issue30260>
___
___
Python-bugs-list
asterite added the comment:
Sorry if I misunderstood how the bug tracker works, but why did you delete
version 3.4 ? Python 3.4 is also affected.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
asterite added the comment:
I made up a small program to reproduce an issue, it consists of two files,
test.py and test2.py, the second one is imported as a module by the first one,
so they should be but in the same dir.
# ls
test.py test2.py
# python3.5 test.py
test
Segmentation fault
Changes by asterite <aster...@seclab.cs.msu.su>:
Added file: http://bugs.python.org/file46848/test2.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by asterite <aster...@seclab.cs.msu.su>:
Added file: http://bugs.python.org/file46847/test.py
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from asterite:
I faced a crash during iterpreter shutdown (Py_Finalize), in final garbage
collection phase.
The reason, as far as I could understand, was the following:
In Python 3, when an unclosed socket is destroyed, it issues a ResourceWarning,
which contains a string
