From: Komiya T. <i.t...@gm...> - 2022-01-08 06:25:07
|
>BTW: what is the state of https://pypi.org/project/pycmark/ by @ tk0miya? >It looks promising as a lightweight alternative for pure CommonMark I finished my work. It has been fully compatible with CommonMark. The remaining task is creating an extension for sphinx using pycmark and pycmark-gfm. I thought to release v1.0 after that, but I lost my interest for it because myst-parser has appeared. 2022年1月6日(木) 23:08 "Günter Milde" via Docutils-develop <doc...@li...>: > > status: open --> open-fixed > Comment: > > Marking this as fixed, will close once the next release is out. > > BTW: what is the state of https://pypi.org/project/pycmark/ by @ tk0miya? > It looks promising as a lightweight alternative for pure CommonMark > as it only depends on Docutils. > > Thank you all for the good work. > > ________________________________ > > [feature-requests:#86] Replace recommonmark with myst-docutils > > Status: open-fixed > Group: Default > Created: Sun Jan 02, 2022 01:26 PM UTC by Chris Sewell > Last Updated: Wed Jan 05, 2022 05:58 PM UTC > Owner: nobody > > Hey guys, > > As discussed in https://github.com/readthedocs/recommonmark/issues/221, recommonmark has been officially deprecated in favour of https://github.com/executablebooks/MyST-Parser/. > > In myst-parser v0.16, I added first-class support for direct docutils use (as opposed to via sphinx) and introduced the parallel https://pypi.org/project/myst-docutils/ distribution, which is myst-parser but without explicit install requirements on docutils or sphinx, i.e. you can install myst-docutils with any version of docutils and it will work without sphinx installed. > > receive(see https://github.com/executablebooks/MyST-Parser/blob/master/CHANGELOG.md#0160---2021-12-06, https://github.com/executablebooks/MyST-Parser/issues/347, and https://myst-parser.readthedocs.io/en/latest/docutils.html) > receive > receiveIn the master branch (and soon to be myst-docutils v0.17) I have also been working to improve the rigour of the behaviour/testing against this parser. > (as an example, I believe your current recommonmark solution does not actually work properly with code fences, because it does not syntax highlight the code, see: https://github.com/executablebooks/MyST-Parser/pull/478) > > The fixture test sets, essentially provide a full specification of the Markdown -> docutils AST conversion (pre-docutils-transforms): > > https://raw.githubusercontent.com/executablebooks/MyST-Parser/master/tests/test_renderers/fixtures/docutil_syntax_elements.md > https://raw.githubusercontent.com/executablebooks/MyST-Parser/master/tests/test_renderers/fixtures/docutil_roles.md > https://raw.githubusercontent.com/executablebooks/MyST-Parser/master/tests/test_renderers/fixtures/docutil_directives.md > > and are currently tested in the CI for myst-docutils against docutils v0.16, v0.17 and v0.18: https://github.com/executablebooks/MyST-Parser/runs/4670995311?check_suite_focus=true > > I'm also happy to recieve any feedback / improvement suggestions to facilitate this, and have opened a parallel discussion topic here: https://github.com/executablebooks/MyST-Parser/discussions/487 > > Cheer, > Chris > > ________________________________ > > Sent from sourceforge.net because doc...@li... is subscribed to https://sourceforge.net/p/docutils/feature-requests/ > > To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/docutils/admin/feature-requests/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. > > _______________________________________________ > Docutils-develop mailing list > Doc...@li... > https://lists.sourceforge.net/lists/listinfo/docutils-develop > > Please use "Reply All" to reply to the list. |