<story><title>PEP 594 – Removing dead batteries from Python&apos;s standard library</title><url>https://www.python.org/dev/peps/pep-0594/</url></story><parent_chain><item><author>korethr</author><text>Hmm, should perhaps this be worthy of a major version number bump? Yes, it&amp;#x27;s not as large or as breaking of a change as the 2.7-&amp;gt;3.0 transition, but by removing modules from the standard library, backwards compatibility &lt;i&gt;is&lt;/i&gt; being broken. Now, perhaps most people don&amp;#x27;t use those features anymore, but for those people who do use and rely on these modules, a major version number change would be a welcome signal that their code will no longer work with the new version.&lt;p&gt;But, after the initial pain of the 2.7-&amp;gt;3.0 transition, I doubt we&amp;#x27;ll ever see another major version number jump, even if a logical use of version numbers would merit it.</text></item></parent_chain><comment><author>sago</author><text>Python minor versions allow things to be removed and thus &amp;#x27;break backwards compatibility&amp;#x27;. There is a process for warning of upcoming deprecation then removing it after that. For modules this is documented in PEP 4 (from 2000). Similar deprecation schedules are used by other important ecosystems such as Django.&lt;p&gt;We&amp;#x27;d be on way more than Python 3 if the major version was bumped for each one.</text></comment>
<story><title>PEP 594 – Removing dead batteries from Python&apos;s standard library</title><url>https://www.python.org/dev/peps/pep-0594/</url></story><parent_chain><item><author>korethr</author><text>Hmm, should perhaps this be worthy of a major version number bump? Yes, it&amp;#x27;s not as large or as breaking of a change as the 2.7-&amp;gt;3.0 transition, but by removing modules from the standard library, backwards compatibility &lt;i&gt;is&lt;/i&gt; being broken. Now, perhaps most people don&amp;#x27;t use those features anymore, but for those people who do use and rely on these modules, a major version number change would be a welcome signal that their code will no longer work with the new version.&lt;p&gt;But, after the initial pain of the 2.7-&amp;gt;3.0 transition, I doubt we&amp;#x27;ll ever see another major version number jump, even if a logical use of version numbers would merit it.</text></item></parent_chain><comment><author>enedil</author><text>It&amp;#x27;s also quite possible, that the people who use these features use Python 2 anyway.</text></comment>