Is it good to change the Python antigravity library
<p>I came across Python's antigravity library recently and got information about it from <a href="http://python-history.blogspot.com/2010/06/import-antigravity.html" rel="nofollow">this</a> post. I then tried <code>import antigravity</code> in the interpreter: it opened the URL of the xkcd comic as expected but did not display the image of the comic in that page.</p>

<p>I then found that the comic did not show up because the URL in the antigravity library was a HTTP one and when I tried to load the page after changing the URL from <a href="http://xkcd.com/353/" rel="nofollow">http://xkcd.com/353/</a> to <a href="https://xkcd.com/353/" rel="nofollow">https://xkcd.com/353/</a> the image showed up.</p>

<p>This made me think if this could be corrected. Is it good to report this as an issue in the Python code (or) change the following line in the antigravity library :</p>

<pre><code>webbrowser.open("http://xkcd.com/353/")
</code></pre>

<p>to</p>

<pre><code>webbrowser.open("https://xkcd.com/353/")
</code></pre>

<p>and submit as to their Issue tracker.</p>

<p>What would be the consequences of the above change? Would it cause any backward compatibility issue?</p>

<h2>Edit</h2>

<p>Just for the Note. This problem has been fixed after filing an issue in the Python Bug Tracker. You may find the issue using <a href="https://bugs.python.org/issue28181" rel="nofollow">this link.</a></p>

<p>Report it to the Python issue tracker. Its purpose is to get questions like "will there be problems with backward compatibility" into the view of the people best capable of making that determination. Even if they reject the change, the issue will be documented, in case a later review reverses that decision.</p>

python