John,
I did try working on it again and I did what you had suggested. I also copied the wingdebugpw file into the same folder where the wingdbstub.py was located.
This is the result of running it in the terminal.
I will be working on it again in the next few hours if I can zero in on what caused it not to run.
(Generic) Daniels-iMac:tutorial danielmontecillo$ python example2.py
Starting up...
This code runs outside of the debugger
Now starting the debugger and attaching to the IDE
Traceback (most recent call last):
File "example2.py", line 13, in <module>
import wingdbstub
File "/Users/danielmontecillo/Documents/Software_Development/Python/wing_tutorial/tutorial/wingdbstub.py", line 273, in <module>
raise ValueError('Not connected')
ValueError: Not connected
(Generic) Daniels-iMac:tutorial danielmontecillo$
Thanks,
Daniel
On Mar 20, 2018, at 7:19 AM, Wingware Support <***@wingware.com<mailto:***@wingware.com>> wrote:
Can you verify that you are importing the wingdbstub that you're modifying? You can do this by either inserting a syntax error into the file (e.g. add a line: this is invalid python) or by adding print(wingdbstub) after the import wingdbstub and then looking at the filename printed.
Thanks,
John
On 3/20/18 12:16 AM, Daniel Montecillo wrote:
John,
I manually created the debug_log.log file then I added the path string to the kLogFile variable in wingdbstub.py. I deleted the file but kept the path string assigned to the variable, but there was no debug_log.log file created.
I assigned the kExitOnFailure variable to true, but still the same, every time I'm running the example2.py code in the terminal, the debugger wasn't able to attach to the process.
I did try doing the same process on my other machine and still, the debugger is not capturing the breakpoint and exception in the tutorial file.
I will try doing more experiment and see what I other method that will enable me to make this work. I think I will succeed with more patience and diligence.
Thanks,
Daniel
On Mar 19, 2018, at 7:56 AM, Wingware Support <***@wingware.com<mailto:***@wingware.com> <mailto:***@wingware.com>> wrote:
On 3/19/18 12:28 AM, Daniel Montecillo wrote:
Sorry, I forgot to include in my earlier email that the log file was empty. No information has been recorded on it. I will continue to work and investigate on how I will be able to make it work.
Was the /Users/danielmontecillo/Documents/Software_Development/Python/wing_tutorial/tutorial/debug_log.log file created? It would be odd if it were created but left empty. Could you remove it and try debugging again?
Could you also set the kExitOnFailure variable to True in wingdbstub?
Thanks,
John