<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jghn</author><text>I struggle with this whenever I think about it. On one hand I agree with all of the points you make. But on the other hand, it didn&amp;#x27;t have to be this way. Python 3 has been out for 12 years now. If people hadn&amp;#x27;t dragged their feet on converting the mess wouldn&amp;#x27;t be nearly as large as it wound up being.</text><parent_chain><item><author>epistasis</author><text>About every other month I have to help a biologist who has pulled down an older program from Github debug why it broke in their data only to find that they were trying to run in Python 3 instead of Python 2. These are people that can write shell scripts, but don&amp;#x27;t program. It makes me aware of all the old code out there that is not used super frequently, but still solves people&amp;#x27;s problems, and would continue to if there hadn&amp;#x27;t been breaking changes.&lt;p&gt;As I write Python 3 now, I am less than impressed with the reasons for breaking compatibility. I&amp;#x27;m told that it was necessary for proper bug-free Unicode code, but there&amp;#x27;s enough difficulty when using, say, gzip, and little enough documentation about the &amp;quot;proper&amp;quot; way to handle Unicode that I doubt that it will actually reduce Unicode-related bugs.&lt;p&gt;Python is still a great tool, but Python 3 really took the shine off for me.</text></item></parent_chain></comment><story><title>All Python versions less than 3.6 are now EOL</title><url>https://devguide.python.org/#status-of-python-branches</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jbay808</author><text>When I was first starting, I almost gave up on Python because the print &amp;quot;Hello world&amp;quot; script that I copy-pasted from an online tutorial failed to run.&lt;p&gt;The hardest part (for me) of getting started with a new language is setting up the environment to run properly... Installing libraries, configuring environment variables, pointing the IDE to the interpreter, etc. So of course that&amp;#x27;s where I assumed my mistake was.&lt;p&gt;It was only much later that I realized that I was running Python 3 (newer is better right?) and the tutorial was written when Python 2 was the latest version. So the print statements changed.&lt;p&gt;And of course, &amp;quot;print&amp;quot; is in everyone&amp;#x27;s first program. So it broke the experience for all first time users.</text><parent_chain><item><author>epistasis</author><text>About every other month I have to help a biologist who has pulled down an older program from Github debug why it broke in their data only to find that they were trying to run in Python 3 instead of Python 2. These are people that can write shell scripts, but don&amp;#x27;t program. It makes me aware of all the old code out there that is not used super frequently, but still solves people&amp;#x27;s problems, and would continue to if there hadn&amp;#x27;t been breaking changes.&lt;p&gt;As I write Python 3 now, I am less than impressed with the reasons for breaking compatibility. I&amp;#x27;m told that it was necessary for proper bug-free Unicode code, but there&amp;#x27;s enough difficulty when using, say, gzip, and little enough documentation about the &amp;quot;proper&amp;quot; way to handle Unicode that I doubt that it will actually reduce Unicode-related bugs.&lt;p&gt;Python is still a great tool, but Python 3 really took the shine off for me.</text></item></parent_chain></comment><story><title>All Python versions less than 3.6 are now EOL</title><url>https://devguide.python.org/#status-of-python-branches</url></story>