From a4015b11362c9c180896976f266a5ae530f13a49 Mon Sep 17 00:00:00 2001 From: Glen Whitney Date: Fri, 12 Feb 2021 09:03:34 -0800 Subject: [PATCH] chore: satisfy flake8 --- mkdocs_semiliterate/plugin.py | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/mkdocs_semiliterate/plugin.py b/mkdocs_semiliterate/plugin.py index 67d9bb8..54f2c0b 100644 --- a/mkdocs_semiliterate/plugin.py +++ b/mkdocs_semiliterate/plugin.py @@ -112,7 +112,7 @@ is checked for `{! ... !}`. raise EOFError(errmsg) filename = body_match['fn'] gitextract = False - dq_doc = """ md + r""" md ### Double-quoted filenames and Git extraction Standard Python escape sequences in double-quoted filenames are interpreted @@ -139,7 +139,8 @@ include content from that file. For example, you could write to extract content starting after the `### install` line from the `mkdocs.yml` file in the Git commit of this repository tagged `0.1.0`. This feature is primarily useful if you are documenting the -development or changes to a project over time, and want to be sure that +development or changes to a project over time, or are documenting a feature +in a specific past release of your project, and want to be sure that material included in your documentation does _not_ change as the project progresses. (This behavior is as opposed to the usual case, in which you want your documentation to incorporate the most up-to-date version of extracted