summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorWaylan Limberg <waylan.limberg@icloud.com>2022-07-15 08:38:34 -0400
committerGitHub <noreply@github.com>2022-07-15 08:38:34 -0400
commitc0f6e5a31ea8e7fe98910a0523144c2a96fa9bf1 (patch)
tree5686120668ce35073d08e08a366d6d3371ab2b17 /docs
parent77fb7f1b51076becff488a9b42ef2883153262a0 (diff)
downloadpython-markdown-c0f6e5a31ea8e7fe98910a0523144c2a96fa9bf1.tar.gz
Move backslash unescaping to treeprocessor
By unescaping backslash escapes in a treeprocessor, the text is properly escaped during serialization. Fixes #1131. As it is recognized that various third-party extensions may be calling the old class at `postprocessors.UnescapePostprocessor` the old class remains in the codebase, but has been deprecated and will be removed in a future release. The new class `treeprocessors.UnescapeTreeprocessor` should be used instead.
Diffstat (limited to 'docs')
-rw-r--r--docs/change_log/release-3.4.md10
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/change_log/release-3.4.md b/docs/change_log/release-3.4.md
index 9d1cd17..9db6707 100644
--- a/docs/change_log/release-3.4.md
+++ b/docs/change_log/release-3.4.md
@@ -30,10 +30,18 @@ markdown.markdown(src, extensions=[TableExtension(use_align_attribute=True)])
In addition, tests were moved to the modern test environment.
+### Backslash unescaping moved to Treeprocessor (#1131).
+
+Unescaping backslash escapes has been moved to a Treeprocessor. However, it is
+recognized that various third-party extensions may be calling the old class at
+`postprocessors.UnescapePostprocessor`. Therefore, the old class remains in the
+code base, but has been deprecated and will be removed in a future release. The
+new class `treeprocessors.UnescapeTreeprocessor` should be used instead.
+
### Previously deprecated objects have been removed
Various objects were deprecated in version 3.0 and began raising deprecation
-warnings (see the [version 3.0 release notes] for details). Any of those object
+warnings (see the [version 3.0 release notes] for details). Any of those objects
which remained in version 3.3 have been removed from the code base in version 3.4
and will now raise errors. A summary of the objects are provided below.