Replaced eval with json

2021/Day 18/part1.py

@@ -1,4 +1,5 @@
 from functools import reduce
+import json
 
 SnailfishNumber = list[int]
 
@@ -97,6 +98,6 @@ def magnitude(number: SnailfishNumber) -> int:
 
 
 with open("input.txt") as file:
-    numbers = list(map(eval, filter(None, map(str.strip, file))))
+    numbers = list(map(json.loads, filter(None, map(str.strip, file))))
 
 print(magnitude(reduce(add, numbers)))

2021/Day 18/part2.py

@@ -1,4 +1,5 @@
 from copy import deepcopy
+import json
 
 SnailfishNumber = list[int]
 
@@ -103,7 +104,7 @@ def magnitude(number: SnailfishNumber) -> int:
 
 
 with open("input.txt") as file:
-    numbers = list(map(eval, filter(None, map(str.strip, file))))
+    numbers = list(map(json.loads, filter(None, map(str.strip, file))))
 
 print(max(
     magnitude(save_add(a, b))

README.md

@@ -185,7 +185,7 @@ I try to optimize each solution as much as possible, so although they are writte
 
 #### I also follow some rules for writing my solutions:
 
-- The entire repository is [PEP8](https://pep8.org/) compliant, as [verified](../../actions/workflows/lint.yaml) by the `flake8` linter (with the [exception of some rules](tox.ini#L21-L52))
+- The entire repository is [PEP8](https://pep8.org/) compliant, as [verified](../../actions/workflows/lint.yaml) by the `flake8` linter (with the [exception of some rules](tox.ini#L21-L48))
 
 - **Input files may contain any number of empty lines**, especially at the end. In some cases, this also applies to whitespace characters.<br>
   Currently I like to handle this rule using the following general snippet to read files:

tox.ini

@@ -16,7 +16,7 @@ require-plugins=
     ; flake8-string-format
     pep8-naming
 
-inline-quotes='"'
+; inline-quotes='"'
 max-line-length=120
 ignore=
 
@@ -43,10 +43,6 @@ ignore=
 ; I mostly follow these rules, but since I want to keep solutions code clean,
 ; I want to add neither extra lines of code nor `# noqa` comments to comply with the linter
 
-    ; Use of "eval" is insecure
-    ; (For some puzzles, `eval` comes in handy for quickly parsing input data)
-    DUO104
-
     ; Variable in global scope should not be mixedCase
     ; (Sometimes, I want to use variables in the same case as they were in the puzzle statement)
     N816