aboutsummaryrefslogtreecommitdiffstats
path: root/pydis_site
diff options
context:
space:
mode:
authorGravatar ks129 <[email protected]>2021-07-09 14:58:47 +0300
committerGravatar GitHub <[email protected]>2021-07-09 14:58:47 +0300
commit2c156a46e4bdae22a973a3ad70368d4d43f94ec0 (patch)
tree61ba5318aa328756cdfedb839c1eb2f86c07a281 /pydis_site
parentAdd PEP 8 song embed (diff)
Move comment types from <b> tags to <h4>
Diffstat (limited to 'pydis_site')
-rw-r--r--pydis_site/templates/events/pages/code-jams/code-style-guide.html15
1 files changed, 10 insertions, 5 deletions
diff --git a/pydis_site/templates/events/pages/code-jams/code-style-guide.html b/pydis_site/templates/events/pages/code-jams/code-style-guide.html
index f691d067..0d948cbc 100644
--- a/pydis_site/templates/events/pages/code-jams/code-style-guide.html
+++ b/pydis_site/templates/events/pages/code-jams/code-style-guide.html
@@ -188,17 +188,21 @@ from pathlib import Path</code></pre>
<p>There are three types of comments:</p>
<ul>
<li>
- <b>Block comments:</b> Probably most common comment type. Should be indented to the same level as the code they describe.
- Each line in the block comment has to start with <code>#</code> what should be followed by a single space,
- except for text indention inside the comment. To separate paragraphs, use one line containing only <code>#</code>.
+ <h4>Block comments</h4>
+ <p>
+ Probably most common comment type. Should be indented to the same level as the code they describe.
+ Each line in the block comment has to start with <code>#</code> what should be followed by a single space,
+ except for text indention inside the comment. To separate paragraphs, use one line containing only <code>#</code>.
+ </p>
<pre><code class="language-python">if variable is None or variable == 1:
# If variable is None, something went wrong previously.
#
# Here starts a new important paragraph.</code></pre>
</li>
<li>
+ <h4>Inline comments</h4>
<p>
- <b>Inline comments:</b> You should prefer block comments over inline comments and use inline comments only where it is really necessary.
+ You should prefer block comments over inline comments and use inline comments only where it is really necessary.
Never use inline comments to explain obvious things like what a line does.
</p>
<p>If you want to use an inline comment on a variable, think first, maybe you can use a better variable name instead.</p>
@@ -219,8 +223,9 @@ shop_name = "Walmart"
x = x + 1 # Compensate for border</code></pre>
</li>
<li>
+ <h4>Docstrings</h4>
<p>
- <b>Docstrings:</b> Last, but not least important comment type is docstring, which is a short version of documentation string.
+ Last, but not least important comment type is docstring, which is a short version of documentation string.
Docstring rules haven't been defined by PEP 8, but by <a href="https://www.python.org/dev/peps/pep-0257">PEP 257</a> instead.
Docstrings should start and end with three quotes (""").
</p>