Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Figure out how to capture parser warnings and provide more useful feedback #21

Closed
choldgraf opened this issue Feb 21, 2020 · 0 comments · Fixed by #107
Closed

Figure out how to capture parser warnings and provide more useful feedback #21

choldgraf opened this issue Feb 21, 2020 · 0 comments · Fixed by #107

Comments

@choldgraf
Copy link
Member

choldgraf commented Feb 21, 2020 •
edited
Loading

Sphinx provides warnings about errors that it finds on lines etc when it parses pages. However, since we are parsing cell-by-cell, line numbers don't mean anything unless you know the cell they belong to.

We should find a way to get Sphinx to report not only line numbers, but cell numbers in the warning reporting.

It seems that the warning message itself gets raised after the parsing process...so it seems like there's something inside the Sphinx machinery making this happen as opposed to one of our parsers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move to markdown-it-py markdown parser implementation executablebooks/MyST-NB
1 participant
@choldgraf