[issue34821] Crash after run Python interpreter from removed directory

STINNER Victor added the comment: I understood that the bug was fixed in Python 3.5. Python 3.4 and older are no longer supported, I close the issue. -- nosy: +vstinner resolution: -> fixed stage: -> resolved status: open -> closed ___ Python

[issue34821] Crash after run Python interpreter from removed directory

Karthikeyan Singaravelan added the comment: Just installed Python 3.4 and can confirm this is fixed in 3.5 but exists on Python 3.4.9 though I don't receive any segfaults though as in the picture with 3.4. karthi@ubuntu-s-1vcpu-1gb-blr1-01:~$ mkdir /tmp/foo

[issue34821] Crash after run Python interpreter from removed directory

Karthikeyan Singaravelan added the comment: Thanks for the report and steps. Can you try this on Python 3.5 ? I think this is the related issue issue22834 that was not fixed in Python 3.4 and has the same line numbers. I can't reproduce this on my Ubuntu machine with Python 3.6.5 from

[issue34821] Crash after run Python interpreter from removed directory

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34821] Crash after run Python interpreter from removed directory

New submission from Игорь Никитин : How to repeat: see screen. For example, command "lsb_release" is also not found removed directory, but there is no crash. Python2, in this case, run without problem. -- files: python_bug.png messages: 326567 nosy: Игорь Никитин priority: normal