Opened 10 years ago
#39 new enhancement
specdomain: create more meaningful error message when sphinx discovers an invalid char
| Reported by: | jkirchman | Owned by: | jemian |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Keywords: | specdomain | Cc: |
Description
When sphinx encountered a char it considered invalid, it did not provide an error message which was instructive enough to know where to find the problem. It stated the char ascii number it found offensive and what appears to be the column but not the line number. Sphinx should also provide a line number.
This was the error it reported:
459 jkirchman@hobbs bcda_sphinx> make html sphinx-build -b html -d build/doctrees source build/html Running Sphinx v1.1.3 loading pickled environment... done building [html]: targets for 1 source files that are out of date updating environment: 0 added, 1 changed, 0 removed reading sources... [100%] index Sphinx error: 'ascii' codec can't decode byte 0xce in position 62: ordinal not in range(128) make: * [html] Error 1
The offending character was an extended ascii mu (char=206 decimal, 0xce) at line=286 and column=59.
