Łukasz Langa

While resolving the conflict, I bumped the version all the way to 0.20.1. Let's see how that fares.

For the record, my suggestion for this was as follows: ### e s install - enables to install a new specified version, you can say `--latest` if you don't know...

Admit it, you just liked my masterful use of Markdown. But yeah, we should do selective --major upgrades, that makes sense to me.

I'm taking this one.

(I'm still investigating at the moment whether something changed in my environment.) Running the following right now hangs on test_input_tty for me: ./python.exe -m test test_builtin test_builtin -v This fails...

Hynek confirmed on Big Sur with Python 3.9.5 from asdf that test_input_tty hangs, too, if ran for the second time in the same process. Moreover, readline is not it. First...

Parent process hangs on: * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP * frame #0: 0x00007fff6741181e libsystem_kernel.dylib`read + 10 frame #1: 0x000000010226a117 python.exe`_Py_read(fd=3, buf=0x00007f8d24009840, count=8192) at fileutils.c:1744:13...

This might be a long-standing problem. I haven't encountered it before because I was always running -R: with -j and in this case the test is skipped: test_input_tty (test.test_builtin.PtyTests) ......

Amazingly, excluding every other test function with a bunch of `-i` patterns still makes it hang when ran twice. On the other hand, only including the test function with `-m`...

I found the high-level reason why test_builtin hangs: it runs doctests as well. What's the root cause? I don't know yet. But to confirm, I can also hang the tests...