<story><title>Apple removes Python 2.7 in macOS 12.3 beta</title><url>https://developer.apple.com/documentation/macos-release-notes/macos-12_3-release-notes#Python</url></story><parent_chain><item><author>Alex3917</author><text>&amp;gt; the python community’s bizarre behavior during the 2.X -&amp;gt; 3.X move honestly made me think less of the language.&lt;p&gt;There weren&amp;#x27;t that many people who were outright against Python 3, other than Zed Shaw for a few years. It just took until Python 3.4 for the language to really be usable in production, and after that it took a couple more years for every library to be updated. But the community has been pretty unified for 5+ years at this point.</text></item><item><author>zionic</author><text>It’s also about (damn) time.&lt;p&gt;I know it shouldn’t, but the python community’s bizarre behavior  during the 2.X -&amp;gt; 3.X move honestly made me think less of the language.&lt;p&gt;Tech is supposed to just be tech, but when the community behaves this badly about adopting improvements how can that not influence your decision to invest in that tech? If 2.X -&amp;gt; 3.X was such a drama fest what’s gonna happen next time they need to upgrade? Etc</text></item><item><author>Rygian</author><text>Not much of a choice anyway. Choosing to keep an unsupported piece of software in the system is a security liability.</text></item></parent_chain><comment><author>lanstin</author><text>If by unified you mean no longer arguing, sure I switched from Python 2 to Go lang. (I will concede if I am doing exploratory stuff, I will start new repos in Python 3, e.g. for boto quick exploration.) I am still bitter about the fine Python 2 code I supported and extended that is now all go or Java.</text></comment>
<story><title>Apple removes Python 2.7 in macOS 12.3 beta</title><url>https://developer.apple.com/documentation/macos-release-notes/macos-12_3-release-notes#Python</url></story><parent_chain><item><author>Alex3917</author><text>&amp;gt; the python community’s bizarre behavior during the 2.X -&amp;gt; 3.X move honestly made me think less of the language.&lt;p&gt;There weren&amp;#x27;t that many people who were outright against Python 3, other than Zed Shaw for a few years. It just took until Python 3.4 for the language to really be usable in production, and after that it took a couple more years for every library to be updated. But the community has been pretty unified for 5+ years at this point.</text></item><item><author>zionic</author><text>It’s also about (damn) time.&lt;p&gt;I know it shouldn’t, but the python community’s bizarre behavior  during the 2.X -&amp;gt; 3.X move honestly made me think less of the language.&lt;p&gt;Tech is supposed to just be tech, but when the community behaves this badly about adopting improvements how can that not influence your decision to invest in that tech? If 2.X -&amp;gt; 3.X was such a drama fest what’s gonna happen next time they need to upgrade? Etc</text></item><item><author>Rygian</author><text>Not much of a choice anyway. Choosing to keep an unsupported piece of software in the system is a security liability.</text></item></parent_chain><comment><author>ssully</author><text>This is my experience as well. There were plenty of people online vocally against Python3, but once we hit 3.4 I never worked with anyone IRL that was against it. The mindset was almost always &amp;quot;this is the way forward&amp;quot;, so that&amp;#x27;s how we moved with our projects.</text></comment>