Open anb0s opened 2 years ago
I have to admit that the Python Tracebacks are pretty intimidating. My steps:
If all else fails, you could add strategic print/log messages into your code, as Guido intended.
First, you have to identify the file that is provoking the error by systematically replacing your tailored files with boilerplate examples, until the error disappears.
My suspicion without digging deeper into your Trace is that one of your input files has a syntax error. You could use linters/checkers that validate the integrity of all your inputfiles.
For JSON, use jq. For CSS, use http://csslint.net/. I haven't used the latter, it was just the first Google hit.
We are using mkdocs-with-pdf and facing sometimes issues we do not understand. Is it somehow possible to trace or debug the issue? E.g. have some pointers to related files etc.?
Example traceback: