Skip to content
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

"Debug in winpdb" is broken #33

Closed
GoogleCodeExporter opened this issue Jan 26, 2016 · 4 comments
Closed

"Debug in winpdb" is broken #33

GoogleCodeExporter opened this issue Jan 26, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link
Collaborator

What steps will reproduce the problem?
1. Open a *.py file in ulipad
2. Click 'debug' button
3. Check 'error.txt', will see:
ulipad\mixins\Import.py", line 8213, in OnPythonDebug
    interpreter = interpreters[win.pref.default_interpreter]
KeyError: u'default'

What is the expected output? What do you see instead?
should trigger winpdb instead of the error

What version of the product are you using? On what operating system?
v3.9 source on winxp with activepython 2.5.2.2

Please provide any additional information below.


Original issue reported on code.google.com by netmbx-...@yahoo.com.sg on 25 Apr 2008 at 7:16

@GoogleCodeExporter
Copy link
Collaborator Author

You should setup a python interpreter first. [Edit]->[Preference...]->[Python], 
click
Setup Python Interpreter button.

Original comment by limo...@gmail.com on 25 Apr 2008 at 7:28

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Collaborator Author

I've fixed in the trunk. If you don't set default python interpeter, it'll 
prompt a
message let you setup first.

Original comment by limo...@gmail.com on 25 Apr 2008 at 7:36

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Collaborator Author

Thought of that also, but it seems to be the same even after I deleted the 
correct 
binding for python interpreter & put back. Maybe it's caused by something else?

Original comment by netmbx-...@yahoo.com.sg on 25 Apr 2008 at 7:53

@GoogleCodeExporter
Copy link
Collaborator Author

You can try svn version, and see if the bug is still existed. I test and no 
problem.
And I don't understand what you said "I deleted the correct binding for python
interpreter & put back", can you explain it more clearly?

Original comment by limo...@gmail.com on 25 Apr 2008 at 8:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant