Replies: 3 comments 4 replies
-
Whoops sorry posted that from the wrong account! Here's the one I normally use... Anyway, this will probably be something with the environment. How is your python script invoked when you're using |
Beta Was this translation helpful? Give feedback.
1 reply
-
🤔 So Can you check if there's a mismatch between the pudb --version
pip list | grep pudb |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some context: I am using tmux, and have my TERM env variable set to
tmux-256color
.Now, I want to use pudb inside of an apptainer environment. If I do something like
pudb script.py
, the editor looks normal and I have no problems.But if I use either
pudb.set_trace()
orbreakpoint()
inside of the script itself and run it, the editor turns into something like this:I guess I am okay with using pudb and then manually setting the breakpoint inside pudb to the line I want, but this would get very tedious if I have a large codebase that spans dozens of files, and would have to traverse all those files just by using the "n" and "s" keys inside pudb's editor. I only get this issue when I am inside of an apptainer, that is itself inside of a tmux environment on a GPU, which I remotely access via SSH. If I just use a standard conda environment, no problem but conda is a terrible solution for my use case.
Are there any ideas or insights on how to fix this? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions