Activity for Docutils: Documentation Utilities
-
Günter Milde modified a comment on ticket #200
Thank you for the contribution. Unfortunately, we cannot include the patch without a change in the Docutils specification, https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#standalone-hyperlinks, which limits the supported URI schemes to the ones listed in the Official IANA Registry of URI Schemes and the W3C's Retired Index of WWW Addressing Schemes. While I don't see a "gemini" URI scheme as a particular problematic case, adding non-registered schemes should be done with special...
-
Fix Unknown target name warning in roles.rst
-
Fixed in [r10249] (with different wording). Thanks for finding the broken link and the patch.
-
Documentation update/fixes.
-
engelbert gruber committed [r10252] on Code
version 0.22.3b1.dev
-
rst2html incorrectly converts tables with Combining Diacritical Marks into HTML
-
Fixed in [r10251].
-
combining unicode chars count in grid tables
-
Fixed, now also for grid tables, in [r10251].
-
rST parser: allow for combining characters in grid tables.
-
Simplify `utils.column_indices()`.
-
Even when adjusting the grid, the parser goes wrong. See [bugs:#512].
-
error installing v0.22.1 on MacOS
-
Fixed with release 0.22.2. Thank you for report, analysis, and testing.
-
Daeho Ro posted a comment on ticket #513
Now it looks fine, thank you! https://github.com/Homebrew/homebrew-core/pull/245109
-
Documentation fixes.
-
Docutils 0.22.2 is out (without the *.swp file). @daeho-ro: Could you please try whether this solves the install problem?
-
release 0.22.2
-
version 0.22.3b1.dev
-
Docutils: Documentation Utilities released /docutils/0.22.2/README.rst
-
-
tagging release 0.22.2
-
version 0.22.2
-
The .__init__.py.swp file should definitely not be there... ... it seems this is not just another problem but the culprit.
-
Thanks for the additional info. It seems that install on MacOS (or just homebrew or snakemake, ...) trips over the spurious file while with Python's standard "pip" installment program or installing "by hand" the spurious file is just ignored. We will release a new version without the spurious file ASAP.
-
error installing v0.22.1 on MacOS
-
It seems that install on MacOS (or just homebrew or snakemake, ...) trip over the spurious file while with Python's standard "pip" installment program or installing "by hand" the spurious file is just ignored. We will release a new version without the spurious file ASAP.
-
MacOS with homebrew, during update some of packages. snakemake depends on this docutils and the ci build error is here. https://github.com/Homebrew/homebrew-core/actions/runs/17826985501/job/50682694634#step:3:4128 In this case, we keep the previous version and it passed the CI. docutils itself https://github.com/Homebrew/homebrew-core/actions/runs/17809144055/job/50651494614?pr=244510#step:3:51 Not sure how can I implement the patch.
-
Dmitry Shachnev created ticket #215
Fix Unknown target name warning in roles.rst
-
I cannot reproduce the install problem here. Installing Docutils 0.22.1 with pip into a new created venv worked without problem, despite the spurious file. What is the OS? Which command was used for the install? Was there any output after Here's the output:? If you used pip, run it with increased verbosity and share the details: pip install <package-name> --verbose You may consider removing the spurious file /docutils-0.22.1/docutils/.__init__.py.swp from the wheel or tar.gz archive (or manually...
-
I cannot reproduce the install problem here. Installing Docutils 0.22.1 with pip into a new created venv worked without problem, despite the spurious file. What is the OS? Which command was used for the install? If you used pip, run it with increased verbosity and share the details: pip install <package-name> --verbose You may consider removing the spurious file /docutils-0.22.1/docutils/.__init__.py.swp from the wheel or tar.gz archive (or manually unpacking and then removing) and trying again.
-
rst2html incorrectly converts tables with Combining Diacritical Marks into HTML
-
The .__init__.py.swp file should definitely not be there.
-
Xinyi Xu modified a comment on ticket #513
Hi, echo on this thread - there also seem to be another issue with 0.22.1 wheel, it ships an swp file that should ideally not be there. $ python -m venv venv $ . venv/bin/activate (venv) $ pip install docutils --no-cache-dir Collecting docutils Downloading docutils-0.22.1-py3-none-any.whl.metadata (15 kB) Downloading docutils-0.22.1-py3-none-any.whl (638 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 638.5/638.5 kB 38.1 MB/s eta 0:00:00 Installing collected packages: docutils Successfully installed...
-
Hi, echo on this thread - there also seem to be another issue with 0.22.1 wheel, it ships an swp file that should ideally not be there. $ python -m venv venv $ . venv/bin/activate (venv) $ pip install docutils --no-cache-dir Collecting docutils Downloading docutils-0.22.1-py3-none-any.whl.metadata (15 kB) Downloading docutils-0.22.1-py3-none-any.whl (638 kB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 638.5/638.5 kB 38.1 MB/s eta 0:00:00 Installing collected packages: docutils Successfully installed...
-
error on v0.22.1
-
Give better messages on malformed tables
-
Fixed in Docutils 0.22.1. Thanks again.
-
Thomas Klausner posted a comment on ticket #508
Thank you for the fixes. Not sure if the following is worth a new ticket, so I thought I'd mention it here: The 0.22.1 tarball includes a backup file (that also gets installed): docutils/.__init__.py.swp
-
Test failure on Windows with embedded images
-
LaTeX writer fails to generate "labels" for some elements with "ids".
-
LaTeX writer fails to generate "labels" for some elements with "ids".
-
Fixed in Docutils 0.22.1.
-
errors for malformed tables do not indicate what the error is
-
Fixed in Docutils 0.22.1. Thanks again!
-
qemu build problem after docutils update to 0.22
-
Fixed in Docutils 0.22.1. Please reopen if there are still problems. Thank you for reporting and tests.
-
regression with docutils 0.22: unsupported operand type(s) for +: 'NoneType' and 'list'
-
Fixed in Docutils 0.22.1. Please reopen if there are still problems. Thank you for reporting and tests.
-
Release date for 0.22 is in the future
-
Fixed in Docutils 0.22.1. Thank you for reporting.
-
Fix: commented out py2 code
-
update version to 0.22.2b1.dev
-
0.22.1 release
-
version 0.22.2b1.dev
-
-
-
tagging release 0.22.1
-
release 0.22.1
-
CHÉN Zhé posted a comment on ticket #512
Thanks, I’ll give it a try. 👍🏻
-
So I can think of any suitable tests, what would your definiton of safe be here? you should . there was a discussion on docutils lists recently (1y) on code injection some general unittests/functional tests are mandatory (was in aegis SCM) considerations remarks for the security documentation ?
-
things are speedier if there is documentation and tests (i assume you did test the patch so why not pass this on) in the patch. the real hard thing for me to check is ... is this safe ... loading directives into docutils any thoughts help ?
-
Supersedes [patches:#17].
-
Thank you for the report. Combining characters in grid tables are known to be problematic. See [bugs:#128] Mind, that the intended behaviour would be to get the "expected" result with the input +---+ | ç̌ | +---+ For simple tables, you can use the simple table syntax, where this problem is fixed: = == ç̌ OK = ==
-
Even when adjusting the grid, the parser goes wrong. See [bugs:512].
-
combining unicode chars count in grid tables
-
Announce change for label writing in latex writer.
-
“ç̌” is composed of two Unicode characters: a c-cedilla and a combining caron. U+00E7 : LATIN SMALL LETTER C WITH CEDILLA U+030C : COMBINING CARON {hacek, V above}
-
rst2html incorrectly converts tables with Combining Diacritical Marks into HTML
-
Document the `<target>` element.
-
Thank you for testing. so it should be fine with Docutils 0.22.1.rc1.
-
Please try with Docutils 0.22.1.rc1.
-
version 0.22.1b1.dev
-
Just to confirm, with the code changes between 0.22 and r10233 applied to 0.22, qemu still builds.
-
0.22.1rc1 release
-
version 0.22.1b2.dev
-
0.22.1rc1
-
Documentation amendments.
-
The remaining issue is a way to tell RSTState.nested_parse() that it shall use a new, separate title style hierarchy for section headings (similar to Sphinx nested_parse_to_nodes()).
-
Applied in [r10229].
-
Element after a section from nested parsing may be invalid. parsers.rst.RSTSTate.nested_parse() with match_titles=True (i.e. support for sections) leads to an invalid document tree, if the nested block contains a section but the element following the nested block is not a section. The structure model allows only a <section> as sibling after a <section>. An invalid doctree can be prevented if the following content is appended to the last nested section instead of its parent. The "nested" directive...
-
Small editorial changes.
-
Fix release date
-
rST parser: Use `section_level_offset` instead of `memo.section_level`.
-
Commit [r10226] fixes the regeression in Sphinx. In order to correctly support sections in nested parsing, it reverts to using memo.section_level to keep record of the current section level. This is cumbersome and error prone because it needs to be updated with every switch of the current node. The attached patch implements an alternative: Store the difference between the intended start level of nested parsing and the number of parents of the base node in the new attribute section_level_offset. Use...
-
The fix is implemented in [r10223].
-
Problems with nested parsing and sections.
-
rST parser: simplifications, fixes, and improvements
-
regression with docutils 0.22: unsupported operand type(s) for +: 'NoneType' and 'list'
-
This should be fixed in [r10227]. Could you re-try?
-
qemu build problem after docutils update to 0.22
-
This should be fixed in [r10227]. Could you re-try?
-
Adjustments for nested_parse().
-
rST parser: restore backwards compatibility of nested parsing.
-
Ernstkm modified a comment on ticket #507
No, not a cache problem. The URL is https://www.docutils.org/rst.html. It's a live page that you can't get to except through search engine results (where it ranks highly) or having bookmarked the URL, but that live page has broken links. The broken links I'm referring to specifically are: https://www.docutils.org/docs/user/rst/quickstart.txt https://www.docutils.org/docs/user/rst/cheatsheet.txt These each result in a 404 error page from GitHub. What I'm wondering is, where would I go to help fix...
-
No, not a cache problem. The URL is https://www.docutils.org/rst.html. It's a live page that you can't get to except through search engine results (where it ranks highly) or having bookmarked the URL, but that live page has broken links. The broken links are, specifically: https://www.docutils.org/docs/user/rst/quickstart.txt https://www.docutils.org/docs/user/rst/cheatsheet.txt These result in a 404 error page from GitHub. What I'm wondering is, where would I go to help fix this: Sourceforge or...
-
No, not a cache problem. The URL is https://www.docutils.org/rst.html. It's a live page that you can't get to except through search engine results (where it ranks highly) or having bookmarked the URL, but that live page has broken links. The broken links are, specifically: https://www.docutils.org/docs/user/rst/quickstart.txt https://www.docutils.org/docs/user/rst/cheatsheet.txt These result in a 404 error page from GitHub. What I'm wondering is, where would I go to help fix this: Sourceforge or...
-
No, not a cache problem. The URL is https://www.docutils.org/rst.html. It's a live page that you can't get to except through search engine results (and it ranks highly), but the live page has broken links. The broken links are, specifically: https://www.docutils.org/docs/user/rst/quickstart.txt https://www.docutils.org/docs/user/rst/cheatsheet.txt These result in a 404 error page from GitHub. What I'm wondering is, where would I go to help fix this: Sourceforge or GitHub? One project refers to https://docutils.sourceforge.io...
-
Consider the use cases: a) A main document includes rST blocks from various different sources (other projects documentation, docstrings, ...). We cannot guarantee a consistent title style hierarchy across all inclusions and want to use a separate title style hierarchy in the included blocks. b) A main document includes chapters from other source files of the same project after an introductory section. The project uses consistent title styles in all files. We want a document-wide title style hierarchy,...
-
assuming the included document. is complete, has a consistent title hierarchy means first title-style is top, next is 2nd asf standard use case is to include the document at a position where it's top level is one below the current in the including document e.g. section l1 ========== section l2 ---------- .. included doc section l3 ========== section l4 ---------- .. including doc section l2 ---------- is there a use case for including and setting a different level, absolute or relative ?