c.oz's profile - activity

I'm using Wing 10 Pro (10.0.4.0, currently) on several Windows systems and linux systems. When I set a breakpoint in the code, and choose Step over current statement (F6), the debugger stops and waits on the first breakpoint, as expected. However, in version 10 on one particular Windows 10 machine (not the other Windows computers, nor the linux computers) if other, subsequent breakpoints are set in the file, the debugger will not stop at them. Nor will lines be stepped through one-by-one, but the code will run as far as it can before terminating or hitting an error.

This is a new development. I've tried uninstalling/reinstalling Wing, and then uninstalling Wing and deleting any user Settings directories in AppData\Roaming. Neither worked; on a completely new installation (no previously Settings are being read, so far as I can tell, because the UI is back at the installation defaults) the breakpoint behavior still exists, and F6 doesn't pause debugging as expected.

Is this a known thing, and is there a solution/workaround?

Done. I tried that update with the Use Legacy Tracer Core with Python 3.12+ preference both checked and unchecked, and h

That's perfect, and resolves my issue on the "problem" computer. I've also changed to Python 3.12 on another computer,

Debugging fails to step, and breakpoints don't break I'm using Wing 10 Pro (10.0.4.0, currently) on several Windows syst

Is it possible to search -- using the built-in "Search" tool -- within the Python Shell? Being able to search commands or outputs via plaintext or regex would be wonderful.

Perfect. Thank you for this. I hadn't found that ability through right-click context-aware menus. Your answer is a great

Allow searching in Python Shell Is it possible to search -- using the built-in "Search" tool -- within the Python Shell?