Łukasz Langa
Łukasz Langa
The doctest runner sets an output redirecting debugger, which subclasses Pdb, around actually running the doctest. This action causes the hang. New finding, we can hang the test with test_pdb...
It \*is* readline-related after all O_O Commenting out this section in Pdb.\_\_init__ makes the issue go away: https://github.com/python/cpython/blob/64a7812c170f5d46ef16a1517afddc7cd92c5240/Lib/pdb.py#L234-L239 time ./python.exe -E -Wd -m test test_builtin test_builtin 0:00:00 load avg: 2.12...
The fix is invalid. It makes it impossible to auto-import stuff with PYTHONSTARTUP.
Keep the feedback coming, we'll be fixing those things for beta 2!
Ruff is a linter with automatic fixes. Autoformatting is a work-in-progress in it and I'm not sure it's available in any released version of Ruff yet. From your output it...
In general, I think this is a worthwhile change but I have two reservations. First, I worry that it changes what the user will see in `F2`. What I mean...
Yes because in the context of search "consecutive occurrences of the same line" cannot be easily distinguished from the search not working well ;)
@koxudaxi let the tests complete, don't rebase unless there are conflicts.
The buildbot failure is an unrelated timeout: ``` command timed out: 1800 seconds without output running [b'make', b'buildbottest', b'TESTOPTS=-j2 --junit-xml test-results.xml ${BUILDBOT_TESTOPTS}', b'TESTPYTHONOPTS=', b'TESTTIMEOUT=1200'], attempting to kill ```
@koxudaxi, sign the CLA and I think we will still take your PR as it includes a test.