3 ms·
AsciiDoc is pretty good, yes. But reST? Just no. As a Python developer I’m no stranger to reST, and problems like the inability to nest inline constructs (e.g.
by oefrha 7y ago
AsciiDoc is pretty good, yes. But reST? Just no.
As a Python developer I’m no stranger to reST, and problems like the inability to nest inline constructs (e.g. [`code`](https://example.com https://example.com) is impossible in reST) are simply ridiculous. (Talking about docutils here. Maybe there are other unofficial implementations that fix some of the problems, but anything not used by Sphinx is rather useless.)
I used to have READMEs of Python projects in reST because of PyPI long_description; those were converted to Markdown soon after PyPI started supporting Markdown. Now I write reST exclusively for Sphinx (mostly in the form of autodoc), but need to check documentation all the time.
- type0 7y agoAbout reST. It's not just difficult to write, most of the time it's also jarring to read. Org-mode isn't very rosy to write either but at least I can scan the document and understand how it will render. For the language that focuses on readability Python has completely missed the boat here.