Skip to content

Commit 14f7650

Browse files
committed
Use lead blockprocessor comment as docstring
The lead comment in blockprocessors.py should really be a docstring for consistency with other files. Fix this with the other part of @Arfrever's patch for issue #203.
1 parent d824986 commit 14f7650

File tree

1 file changed

+12
-10
lines changed

1 file changed

+12
-10
lines changed

markdown/blockprocessors.py

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
1-
# CORE MARKDOWN BLOCKPARSER
2-
# ===========================================================================
3-
#
4-
# This parser handles basic parsing of Markdown blocks. It doesn't concern itself
5-
# with inline elements such as **bold** or *italics*, but rather just catches
6-
# blocks, lists, quotes, etc.
7-
#
8-
# The BlockParser is made up of a bunch of BlockProssors, each handling a
9-
# different type of block. Extensions may add/replace/remove BlockProcessors
10-
# as they need to alter how markdown blocks are parsed.
1+
"""
2+
CORE MARKDOWN BLOCKPARSER
3+
===========================================================================
4+
5+
This parser handles basic parsing of Markdown blocks. It doesn't concern itself
6+
with inline elements such as **bold** or *italics*, but rather just catches
7+
blocks, lists, quotes, etc.
8+
9+
The BlockParser is made up of a bunch of BlockProssors, each handling a
10+
different type of block. Extensions may add/replace/remove BlockProcessors
11+
as they need to alter how markdown blocks are parsed.
12+
"""
1113

1214
from __future__ import absolute_import
1315
from __future__ import division

0 commit comments

Comments
 (0)