-
Notifications
You must be signed in to change notification settings - Fork 164
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
Make some pre-releases? #47
Comments
+1 in principle but it depends on @chrisjsewell . We all know things can happen fast when he gets an idea in his head 💡 |
See ExecutableBookProject/markdown-it-py 😄 Its largely done (see the README for details) and in The main niggling issue is executablebooks/markdown-it-py#1. Its pretty nice that you can configure any aspect of the syntax. I could envisage some of that configurability eventually bubbling up to the CLI: md = (
MarkdownIt()
.use(front_matter_plugin)
.use(myst_block_plugin)
.use(myst_role_plugin)
.disable('image')
.enable('table')
)
md.render("some text") |
Note the footnote extension also supports the inline feature discussed in executablebooks/MyST-Parser#98 (comment), you can configure math to use $$s(w) = s_0 w \cdot \mathbb 1\{w \geq \hat w\}$$ (md:sav_ah) instead of ```{math}
:label: md:sav_ah
s(w) = s_0 w \cdot \mathbb 1\{w \geq \hat w\}
``` (will have to see how this fits in with the docutils renderer) |
That's awesome, love your work @chrisjsewell ! @najulizu, please not this simplified syntax. Please add some whitespace between equation and (Edit: This will work after the parsers are swapped.) |
Ah one other thing - @chrisjsewell mentioned that markdown-it-py is nearly ready to go, but there's still another step of making the myst-parser parse using it, right? |
Best to leave this until after the first round of blog posts / publicizing? |
That was the question I wanted to ask @chrisjsewell - I guess the question is whether we think that switch will make any kind of differece for myst-parser...I don't think so, I think it's a purely-backend thing, but just wanted to make sure |
This commit implements the move from `mistletoe` to `markdown-it-py`, as the underlying markdown parser. The reason for this is are discussed in executablebooks/meta#44 (comment) and executablebooks/meta#47, and the PR #123 discusses in more details the update. Additional changes: - Update `pydata-sphinx-theme` requirement - Improve testing and move to GitHub Actions CI - Add tests and fixes for reporter warnings and include directive - Add documentation of sphinx parser options - Apply doc fixes suggested by @rossbar in #121 - Add warning for non-consecutive headings
done and dusted |
In our last meeting, @jstac suggested that we could release the myst-parser and myst-nb projects in a "public beta" fashion, relatively soon. I think it could be a good idea to get some of these tools out there sooner than later. What do people think about:
What do folks think about that?
And on the second point, we should also reach out to the
nbsphinx
project and see if they have any ideas for how we could dovetail our stacks into one another.The one question I have here, is whether @chrisjsewell thinks that recent conversations about
markdown-it-py
should delay the "announcement" of MyST and the MyST parser. Chris, what do you think?The text was updated successfully, but these errors were encountered: