-
Notifications
You must be signed in to change notification settings - Fork 85
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
Python pdb #33
Comments
Yes, but it'd be a fair amount of work, and I won't have time to do it for at least a few months. I'll leave this issue open until I (hopefully) eventually get around to it. Or someone else could take a stab at it if they want :). |
In the meantime, you could probably write a proxy program that sits in between the Python client library and the simulator. The proxy could run your algorithm and forward messages to-and-from the simulator, and it could also read input from the user via, e.g., a file. |
Is that sort of what the arduino proxy program that intercepts API calls does. Perhaps I could write one for my python script using pdb but sending messages to the proxy. Is that right? |
Yea, the general idea is to extend the functionality of the simulator by writing a wrapper program that does what you need it to. In your case, it sounds like the proxy program should:
|
I cannot seem to get the python debugger to play nice with your API. When the program reaches the trace command, it locks up presumably waiting somewhere for input. Can the interface be made bi-directional and not just write to the log window?
The text was updated successfully, but these errors were encountered: