Using W&B with PDB causes navigation and control keys to not work.
See original GitHub issueDescribe the bug Using the Python Debugger along with W&B causes the interactive shell of the debugger to malfunction. It works, but you can no longer use keys like backspace, <kbd>CTRL</kbd> + <kbd>(something)</kbd>, etc.
To Reproduce
Reproduction is fairly simple. Just add a import pdb; pdb.set_trace()
anywhere in your code, and when the script returns the PDB interactive shell just press <kbd>backspace</kbd>.
Expected behavior
Backspace (or whatever key you pressed) will return ~[[A
, etc.
Operating System
- OS: Ubuntu 16.04
- Browser: No browser.
- Version: 0.10.12
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Using W&B with PDB causes navigation and control keys to ...
Using the Python Debugger along with W&B causes the interactive shell of the debugger to malfunction. It works, but you can no longer...
Read more >Resolve Hotkeys or Volume control keys not working on ...
Describes an problem in which hotkeys or volume keys on the Microsoft keyboard do not work.
Read more >Troubleshooting problems with keyboard shortcuts | IntelliJ ...
Troubleshooting keyboard and mouse shortcuts that are either working incorrectly or not working at all.
Read more >Keyboard shortcuts for Lightroom Classic - Adobe Support
Keys for working with panels ; Open/close right panels, Library and Develop modules, top to bottom. Ctrl + 0 - 9. Command +...
Read more >Working with pdb in Python - Medium
Here is the documentation for the commands. It's good to keep it at hand, as we go through the tutorial. Starting from the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m working on this (will take some time). In the mean time you can set environment variable
WANDB_CONSOLE="wrap"
as a workaround.Hey @seanswyi the only impact this will have on your environment is how we render output to the terminal. By setting the console to wrap you may see messages starting with
wandb:
interspersed with the output that you’re writing to the terminal. Behind the scenes there’s some rather complicated logic to enable our sub-process to synchronously write lines to your processes output. That’s what we believe is interacting poorly with pdb and the ultimate fix is a bit more involved…