-
Notifications
You must be signed in to change notification settings - Fork 227
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
python3 broken backtrace + typo #59
Comments
That's actually not a typo. That's how you have to do it for Python 2.4 and 2.5 support. But it doesn't work in Python 3. I don't know if there's a way around it. |
The real issue is that I thought the installation script for pudb contained an invocation of 2to3, which should've made this issue disappear, but it did not. Fixed in 4f913f6. Please reopen if there's still an issue. |
That's because you decided to use a single code base. If you switch to 2to3, there is a lot of code that can be simplified. I think you can probably delete the py3compat file completely. |
See #1. |
Wow. Goes to show how little I remember of the cr*p I said years ago. :) Re-fixed by 4059aeb. |
Try the code snippet below, do one single step which raises an exception.
is a string object while traceback/format_exception excepts it to be of type .Enter 'e' to show the exception. This kills pudb .
The reason is that the second component of
Furthermore there is a typo in shell.py (line 27)
Thanks for looking into it,
"""Helmut.
The text was updated successfully, but these errors were encountered: