Dale <d...@codefu.org> added the comment:
I hit this on macOS today but I didn't get segmentation fault, at least not for as long as I cared to let Python run. Instead I got a non-responsive Python process using 100% CPU that I had to kill with ^\. I first hit this with GNU readline while running Python interactively under Emacs, then I reproduced it with libedit readline under a regular old terminal using the above recipe. macOS 11.6.1, x86-64, Python 3.10.1 from MacPorts ---------- nosy: +dale _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue41033> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
