<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Editorial Board Decisions on Python Docs Editorial Board</title>
    <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/</link>
    <description>Recent content in Editorial Board Decisions on Python Docs Editorial Board</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Python Docs Editorial Board and Contributors</copyright>
    <lastBuildDate>Tue, 11 Mar 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>``|`` or &#39;or&#39; in parameter documentation</title>
      <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2025-03-11-pipes-or-in-sphinx-type-descriptions/</link>
      <pubDate>Tue, 11 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2025-03-11-pipes-or-in-sphinx-type-descriptions/</guid>
      <description>&lt;p&gt;Additional recommendations in the Style Guide &lt;a href=&#34;https://github.com/python/devguide/pull/1377/&#34;&gt;https://github.com/python/devguide/pull/1377/&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;&lt;a href=&#34;https://discuss.python.org/t/how-should-we-mark-up-multiple-types-in-a-type-field/48196&#34;&gt;Discourse&lt;/a&gt; topic: How
should we mark up multiple types in a type field?&lt;/p&gt;
&lt;p&gt;Currently, the Python docs use &lt;code&gt;|&lt;/code&gt; (pipe) character, similar to how you&amp;rsquo;d annotate a union of types:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-rst&#34; data-lang=&#34;rst&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;:param p:&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;   A parameter that takes an int or a float argument.&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nc&#34;&gt;:type p:&lt;/span&gt; &lt;span class=&#34;nf&#34;&gt;int | float&lt;/span&gt;&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;However, the &lt;a href=&#34;https://www.sphinx-doc.org/en/master/usage/domains/python.html#send_message&#34;&gt;Sphinx docs&lt;/a&gt; says to use the word &lt;code&gt;or&lt;/code&gt;:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-rst&#34; data-lang=&#34;rst&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;:param p:&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;   A parameter that takes an int or a float argument.&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;nc&#34;&gt;:type p:&lt;/span&gt; &lt;span class=&#34;nf&#34;&gt;int or float&lt;/span&gt;&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The editorial board&amp;rsquo;s decision was requested on this matter via &lt;a href=&#34;https://github.com/python/editorial-board/issues/7&#34;&gt;issue #7&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dead Batteries Docs</title>
      <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-11-11-dead-batteries-docs/</link>
      <pubDate>Tue, 11 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-11-11-dead-batteries-docs/</guid>
      <description>&lt;p&gt;History of dead batteries: &lt;a href=&#34;https://discuss.python.org/t/history-of-dead-batteries/68934&#34;&gt;https://discuss.python.org/t/history-of-dead-batteries/68934&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Documenting Dead batteries: &lt;a href=&#34;https://discuss.python.org/t/documenting-dead-batteries/70652&#34;&gt;https://discuss.python.org/t/documenting-dead-batteries/70652&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;PR: &lt;a href=&#34;https://github.com/python/cpython/pull/126622&#34;&gt;https://github.com/python/cpython/pull/126622&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;The PR adds a &amp;ldquo;Removed modules&amp;rdquo; page that lists modules which have been removed. Each module gets a page (with the original URL) that explains why the module is gone.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Devguide Reorganization</title>
      <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-10-14-devguide-reorg/</link>
      <pubDate>Mon, 14 Oct 2024 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-10-14-devguide-reorg/</guid>
      <description>&lt;p&gt;Refactoring the devguide into a Contribution Guide &lt;a href=&#34;https://discuss.python.org/t/refactoring-the-devguide-into-a-contribution-guide/63409&#34;&gt;https://discuss.python.org/t/refactoring-the-devguide-into-a-contribution-guide/63409&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;ve started a large task to restructure the devguide to be more welcoming to non-code contributions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Style Guide recommendations</title>
      <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-08-28-style-guide-recs/</link>
      <pubDate>Wed, 28 Aug 2024 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-08-28-style-guide-recs/</guid>
      <description>&lt;p&gt;Additional recommendations in the Style Guide &lt;a href=&#34;https://github.com/python/devguide/pull/1377/&#34;&gt;https://github.com/python/devguide/pull/1377/&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;The &lt;a href=&#34;https://devguide.python.org/documentation/style-guide/&#34;&gt;Style Guide&lt;/a&gt; has been updated with new
recommendations about author attribution (don&amp;rsquo;t include it) and pronunciation of dunder names (&amp;ldquo;an &lt;code&gt;__init__&lt;/code&gt;, not &lt;code&gt;a __init__&lt;/code&gt;).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Timezone vs time zone</title>
      <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-07-18-clarify-timezone/</link>
      <pubDate>Thu, 18 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-07-18-clarify-timezone/</guid>
      <description>&lt;p&gt;Clarify &lt;code&gt;timezone&lt;/code&gt; vs &amp;ldquo;time zone&amp;rdquo;: &lt;a href=&#34;https://github.com/python/devguide/pull/1352&#34;&gt;https://github.com/python/devguide/pull/1352&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;The CPython PR &lt;a href=&#34;https://github.com/python/cpython/pull/118449&#34;&gt;#118449&lt;/a&gt; updates the spelling of &amp;ldquo;timezone&amp;rdquo; to &amp;ldquo;time zone&amp;rdquo;.
There was a discussion
on the PR that the &amp;ldquo;timezone&amp;rdquo; spelling is also acceptable and have been used within the CPython docs
consistently. However, both Wikipedia and The Free Dictionary redirect &amp;ldquo;timezone&amp;rdquo; to &amp;ldquo;time zone&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;Using the two-word form &amp;ldquo;time zone&amp;rdquo; would help separate the concept from the &amp;ldquo;timezone&amp;rdquo; class in Python.&lt;/p&gt;
&lt;p&gt;The &lt;a href=&#34;https://devguide.python.org/documentation/style-guide/#style-guide&#34;&gt;Style Guide&lt;/a&gt; section on CPython Devguide has
now been updated with the recommendation of using the
two word &lt;code&gt;time zone&lt;/code&gt; when referring to the real-world time concept, and to use the one word &lt;code&gt;timezone&lt;/code&gt; with
appropriate code markup when referring to a Python term.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Function signatures include slash and star</title>
      <link>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-07-12-function-signatures/</link>
      <pubDate>Fri, 12 Jul 2024 00:00:00 +0000</pubDate>
      <guid>https://deploy-preview-42--pythoneditorialboard.netlify.app/changelog/2024-07-12-function-signatures/</guid>
      <description>&lt;p&gt;Function signatures should include slash and star: &lt;a href=&#34;https://github.com/python/devguide/pull/1344&#34;&gt;https://github.com/python/devguide/pull/1344&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;
&lt;p&gt;If a function accepts positional-only or keyword-only arguments, include the
slash and the star in the signature as appropriate.&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-rst&#34; data-lang=&#34;rst&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;p&#34;&gt;..&lt;/span&gt; &lt;span class=&#34;ow&#34;&gt;function&lt;/span&gt;&lt;span class=&#34;p&#34;&gt;::&lt;/span&gt; some_function(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2):&lt;span class=&#34;err&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Although the syntax is terse, it is precise about the allowable ways to call
the function and is taken from Python itself.&lt;/p&gt;
&lt;p&gt;The CPython Devguide has been updated to reflect &lt;a href=&#34;https://devguide.python.org/documentation/style-guide/#function-signatures&#34;&gt;this recommendation&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
