-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pdb prompt is nonresponsive in Python 3.13.0 from python-build-standalone #12888
Comments
I've never used
All that took about a second, which is indeed pretty damn crazy 🤯 And indeed I can reproduce with that. A |
Can this be related to the readline quirk documented @ https://gregoryszorc.com/docs/python-build-standalone/main/quirks.html#backspace-key-doesn-t-work-in-python-repl ? |
Hmm, I don't think so. I don't see such an error message, and for what it's worth, setting |
Oh, this one seems like a likely culprit, however:
Perhaps something similar to #1281 could be going on with libedit (or their usage of it) too? |
Yep, it's that indeed. Built a vanilla CPython 3.13.0 with Tried CPython v3.12.7 built the same way, that works. Will now bisect between the two... |
Well, this was a bit annoying as two build fixes for readline were in between:
but with a bit of
that is:
which notably seems to use Not sure where to go from here. If we want to open a CPython bug about this, we probably need a more minimal reproducer? But I have no clue whether the culprit is CPython or pytest here. |
@The-Compiler wow that's some impressive investigative skills right there! I certainly wouldn't have been able to figure this all out so fast...
Yeah it's pretty sweet ^^ |
@The-Compiler my hero. My sanity owes you a debt of gratitude! Chiming in to confirm that I've been experiencing this bug as well, specifically in a
|
@The-Compiler similar bug happen in gdb: (because of python/cpython#112948 )
After import |
Someone (not me) will need to report this to gdb, and ideally cook up a reproducer and report it to CPython and/or libedit. I won't be spending any more time on this, as it doesn't affect me and we have a workaround for pytest. |
With Python 3.13.0 installed with
uv
(i.e. from python-build-standalone), the pdb prompt is completely nonresponsive when triggered either by the--pdb
flag or by a breakpoint.This can be reproduced by the following test in
test_foo.py
:and running:
I tested the same code with the official source release from python.org for 3.13.0 on the same computer and the same code works just fine, so it seems it's somehow related to the build by python-build-standalone. Note that putting a breakpoint in a regular Python script and running it in the same interpreter does work, so this seems to be an issue with the combination with
pytest
.OS: Arch Linux.
Pytest version
`pip list` output
The text was updated successfully, but these errors were encountered: