exercism/python
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Update TRACEBACKS.md

Browse Source
This commit is contained in:
Bob Hoeppner
2022-07-22 06:06:44 -05:00
parent 13e11689c9
commit e310d7789d
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/TRACEBACKS.md
View File

@@ -33,8 +33,8 @@ ValueError: not enough values to unpack (expected 2, got 1)
``` ```
It says that the most recent call is last, so the place to start is with the exception at the bottom of the trace. Tracebacks are organized with the most recent call is last, so the place to start reading the Traceback is with the exception at the bottom.
From there it can be traced back to the start. By reading upwards from there, we can see how that statement was reached.
If we place the offending line in a function and then call the function we see a longer trace: If we place the offending line in a function and then call the function we see a longer trace:
```python ```python
@@ -114,7 +114,7 @@ Following is an example of logging printed to the console:
``` ```
The level is configured as `INFO` because the default level is `WARNING`. The level is configured as `INFO` because the default level is `WARNING`.
For a persistent log, the logger can be configured to use a file, like so: For a persistent log, the logger can be configured to write to a file, like so:
```python ```python