summaryrefslogtreecommitdiff
path: root/doc/source
diff options
context:
space:
mode:
authorLeonard Richardson <leonardr@segfault.org>2019-07-16 20:31:39 -0400
committerLeonard Richardson <leonardr@segfault.org>2019-07-16 20:31:39 -0400
commitfc71bc1c04e0495c34a5b78ec21895e32848b344 (patch)
tree3a80bb499deecda8be343d8ad3935c30d2158e26 /doc/source
parent0bd336741b26269108e8b345b92d8904c6092980 (diff)
Added documentation for Tag.smooth().
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/index.rst34
1 files changed, 34 insertions, 0 deletions
diff --git a/doc/source/index.rst b/doc/source/index.rst
index 4bca0ae..9ef8ef4 100644
--- a/doc/source/index.rst
+++ b/doc/source/index.rst
@@ -2112,6 +2112,40 @@ whatever's inside that tag. It's good for stripping out markup::
Like ``replace_with()``, ``unwrap()`` returns the tag
that was replaced.
+``smooth()``
+---------------------------
+
+After calling a bunch of methods that modify the parse tree, you may end up with two or more ``NavigableString`` objects next to each other. Beautiful Soup doesn't have any problems with this, but since it can't happen in a freshly parsed document, you might not expect behavior like the following::
+
+ soup = BeautifulSoup("<p>A one</p>")
+ soup.p.append(", a two")
+
+ soup.p.contents
+ # [u'A one', u', a two']
+
+ print(soup.p.encode())
+ # <p>A one, a two</p>
+
+ print(soup.p.prettify())
+ # <p>
+ # A one
+ # , a two
+ # </p>
+
+You can call ``Tag.smooth()`` to clean up the parse tree by consolidating adjacent strings::
+
+ soup.smooth()
+
+ soup.p.contents
+ # [u'A one, a two']
+
+ print(soup.p.prettify())
+ # <p>
+ # A one, a two
+ # </p>
+
+The ``smooth()`` method is new in Beautiful Soup 4.8.0.
+
Output
======