This week's focus was on debugging errors that is an integral part in script writing. No matter how particular you are in your program writing, errors are bound to happen. Whether they are syntax errors, exception errors, or even logic errors, they can be frustrating to locate and weed out when you are creating your scripts. For the lab this week, it was our task to review and debug three different provided scripts.
The first script contained two errors and both were simply typographic errors on different variables. Once those type-o's were corrected, the script ran correctly as you can see below.
The second script was more complex and contained 8 errors within it. I had a lot of trouble getting past the first error and once I realized that the problem was not only the file name, but the file location, I was able to step through the remaining errors somewhat efficiently. Some types of errors that I found within the second script included: file name and location errors, syntax of file paths, typographic errors for function/methods used, and missing or extra parameters for functions. Once I corrected the 8 errors that I found, I was able to get a successful run of the script and here is how it turned out:
The last script had us take a different approach. Instead of correcting the errors that were found, the goal was to implement the try-except callout to identify errors within a section of code and still successfully run the entirety of the script without erroring out. The script had already been divided into two parts. Part B was good to go with no errors. There was an error in Part A however that needed to be isolated and reported using the try-except functions in Python. Once implemented successfully, I was able to achieve and error output for Part A and then still complete Part B of the script. The output is below:
So that is it. No real flow charting on how I go through my debugging process. I am sure debugging gets easier over time as one becomes more familiar with how different classes are used/called upon in Python and what is needed for those to run successfully. As always, leave any comments below on how you approach debugging.
Cheers!
The first script contained two errors and both were simply typographic errors on different variables. Once those type-o's were corrected, the script ran correctly as you can see below.
The second script was more complex and contained 8 errors within it. I had a lot of trouble getting past the first error and once I realized that the problem was not only the file name, but the file location, I was able to step through the remaining errors somewhat efficiently. Some types of errors that I found within the second script included: file name and location errors, syntax of file paths, typographic errors for function/methods used, and missing or extra parameters for functions. Once I corrected the 8 errors that I found, I was able to get a successful run of the script and here is how it turned out:
The last script had us take a different approach. Instead of correcting the errors that were found, the goal was to implement the try-except callout to identify errors within a section of code and still successfully run the entirety of the script without erroring out. The script had already been divided into two parts. Part B was good to go with no errors. There was an error in Part A however that needed to be isolated and reported using the try-except functions in Python. Once implemented successfully, I was able to achieve and error output for Part A and then still complete Part B of the script. The output is below:
So that is it. No real flow charting on how I go through my debugging process. I am sure debugging gets easier over time as one becomes more familiar with how different classes are used/called upon in Python and what is needed for those to run successfully. As always, leave any comments below on how you approach debugging.
Cheers!
No comments:
Post a Comment