-
Notifications
You must be signed in to change notification settings - Fork 232
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
has trouble tracing importlib._bootstrap in python3.3 #115
Comments
This sounds like the same error I reported at #109 |
The issue is that importlib in Python 3.3 is implemented in Python (previously it was all implemented in C), but it is still doing some wacky things deleting stack frames (so that you don't get a ton of importlib calls in an ImportError traceback), which confuses PuDB. |
The workaround is to use an earlier version of Python, like 3.2 or 2.7, which doesn't have importlib implemented in Python. |
That's not a usable workaround for me, since I'm trying to trace a bug that only happens in 3.4. |
1 similar comment
That's not a usable workaround for me, since I'm trying to trace a bug that only happens in 3.4. |
Oh, you're using |
In my experience it works fine with python3. I'll try set trace though. |
OK, I think it works, but it takes you to the wrong place in the stack. |
Seems to be fixed at #240 |
I'm doing an experiment with sys.path_hooks, and pudb is having trouble tracing through it.
pudb seems to fail to find the source for
/usr/lib/python3.3/importlib/_bootstrap.py
, which results in the variables windowlet being smashed to the left.To reproduce:
foo.py
:The text was updated successfully, but these errors were encountered: