# Revision history [back]

### django shell and wingdbstub

my current client runs scripts against their Django site using this pattern

 $python manage.py shell < path-to-script-file.py  If I put this in my script file import wingdbstub print("Hello World!")  and set a breakpoint at "print", I see that Wing switches into debug mode, but it does not stop at the breakpoint. Any known issues with trying to use this pattern? ### django shell and wingdbstub my current client runs scripts against their Django site using this pattern $ python manage.py shell < path-to-script-file.py


If I put this in my script file

import wingdbstub
print("Hello World!")


and set a breakpoint at "print", I see that Wing switches into debug mode, but it does not stop at the breakpoint.

Any known issues with trying to use this pattern?

UPDATE: strange...if I have more advanced code in there, and it raises an exception, Wing stops at the exception...but still does not respect the breakpoint.

### django shell and wingdbstub

my current client runs scripts against their Django site using this pattern

 $python manage.py shell < path-to-script-file.py  If I put this in my script file import wingdbstub print("Hello World!")  and set a breakpoint at "print", I see that Wing switches into debug mode, but it does not stop at the breakpoint. Any known issues with trying to use this pattern? UPDATE: strange...if I have more advanced code in there, and it raises an exception, Wing stops at the exception...but still does not respect the breakpoint. UPDATE 2: I think I see what's happening. Because the script itself is just "stdin" (due to the redirect), the "import wingdbstub" gets run, but then there no knowledge of what's in the script itself.  4 retagged Wingware Support 3826 ●2 ●120 ●16 https://wingware.com/ ### django shell and wingdbstub my current client runs scripts against their Django site using this pattern $ python manage.py shell < path-to-script-file.py


If I put this in my script file

import wingdbstub
print("Hello World!")


and set a breakpoint at "print", I see that Wing switches into debug mode, but it does not stop at the breakpoint.

Any known issues with trying to use this pattern?

UPDATE: strange...if I have more advanced code in there, and it raises an exception, Wing stops at the exception...but still does not respect the breakpoint.

UPDATE 2: I think I see what's happening. Because the script itself is just "stdin" (due to the redirect), the "import wingdbstub" gets run, but then there no knowledge of what's in the script itself.