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.

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

Switch Markdown engine to markdown-it-py #16435

Closed
uranusjr opened this issue Jun 14, 2021 · 0 comments · Fixed by #19702
Closed

Switch Markdown engine to markdown-it-py #16435

uranusjr opened this issue Jun 14, 2021 · 0 comments · Fixed by #19702
Labels
kind:feature Feature Requests

Comments

@uranusjr
Copy link
Member

Copying from #16414:

The current Markdown engine does not support fenced code blocks, so it still won’t work after this change. Python-Markdown’s fenced code support is pretty spotty, and if we want to fix that for good IMO we should switch to another Markdown parser. markdown-it-py (the parser backing MyST) is a popular choice for CommonMark support, which is much closer to GitHub-Flavored Markdown which almost everyone thinks is the standard Markdown (which is unfortunately because GFM is not standard, but that’s how the world works).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature Feature Requests
Projects
None yet
1 participant