Can I Use Python 3?

It&#x27;s kind of disappointing that developers aren&#x27;t self-aware enough to understand that they are essentially screwing themselves by not moving quickly in dropping &quot;legacy&quot; support.<p>&quot;Python 3 will be available in 2008 but we understand that you won&#x27;t use it for at least 5 years.&quot;<p>There&#x27;s an entire class of developers who won&#x27;t upgrade until they absolutely have to. There&#x27;s also a class of administrator that won&#x27;t upgrade their current PC browser from IE6-IE8 until they absolutely have to. Developers are basically screwing themselves by not drawing a firm line.

Sucks that there is no way to paste a requirements.txt file. Lots of projects I work on are in private GitHub repos.<p>Edit: Ah, here we go: <a href="https://pypi.python.org/pypi/caniusepython3" rel="nofollow">https:&#x2F;&#x2F;pypi.python.org&#x2F;pypi&#x2F;caniusepython3</a>. This is the command-line version.

I think it would be very valuable to try and do a big compare-and-contrast analysis of the Python 2-&gt;3 transition vs the ruby 1.8-&gt;1.9(-&gt;2) transition.<p>ruby 1.9 transition was actually a pretty big pain (I have no idea whether as big a pain as python2-&gt;3 or not, that&#x27;d be something to look at).<p>But the ruby ecosystem&#x2F;community has successfully moved to 1.9, there is little left on 1.8.<p>On the other hand, sometimes it&#x27;s _really_ frustrating how much work I need to spend upgrading my ruby stuff to use the latest and greatest. Ruby community is relatively uncaring about backwards compat (less than python? I am not sure. Is that uncaringness part of the tradeoff that got us to all move to ruby 1.9 somehow? I don&#x27;t know, but that&#x27;s what I&#x27;m wondering. Many interesting questions.)

Is referer still worth it to prevent CSRF? They seem to be using a CSRF token in their &lt;form&gt; and that should be all that&#x27;s needed from what I understand..<p><pre><code> Forbidden (403) CSRF verification failed. Request aborted. You are seeing this message because this HTTPS site requires a &#x27;Referer header&#x27; to be sent by your Web browser, but none was sent. This header is required for security reasons, to ensure that your browser is not being hijacked by third parties. If you have configured your browser to disable &#x27;Referer&#x27; headers, please re-enable them, at least for this site, or for HTTPS connections, or for &#x27;same-origin&#x27; requests.</code></pre>

Service seems to be down-ish.<p>You can check it using CLI! <a href="http://vpaste.net/UuOFT" rel="nofollow">http:&#x2F;&#x2F;vpaste.net&#x2F;UuOFT</a> Source code is available here! <a href="https://github.com/jezdez/caniusepython3.com" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jezdez&#x2F;caniusepython3.com</a><p>Disclaimer: I&#x27;m NOT the author.

Well, the tool timed out, so I looked up my dependencies on google:<p>flask: yes, mysqldb: no, pycassa: no<p>I guess I can&#x27;t use python 3 yet still.<p>From what I have read, a lot of people have had trouble installing pymysql, the proposed python 3 mysql library.

I very recently was looking for a way to do some scientific 3D visualizations in Python 3. Requirements: OpenGL 3+ (for shaders) and some basic windowing and mouse event handling.<p>I looked at<p>- PyOpenGL, no windowing.<p>- PyGlet, Python 2.7.<p>- PyQt, only OpenGL 2.<p>- PySide, outdated Qt version and more or less unmaintained.<p>- wxPython, Python 2.7.<p>- PyGame, Python 2.7.<p>So, no dice. This is really terrible. Also, the hoops I had to jump through to get some of these installed was just ridiculous.<p>The solution I ended up with? Tornado, websockets and WebGL. Because that is the easiest way I could find to write 3D visualizations for scientific Python. Not Python.

The fatal fact about python and python 3 is, that python 2.7 seems to be considered a convenient and stable plattform by its users. A dream come true for all the &quot;prudent&quot; folks out there who do not want anything to change.<p>The lesson learned will be, to implement changes more incrementally so people are gradually upgrading instead of having a high step.

Doesn&#x27;t seem to work. I get a created_at time, but no started_at in the resulting json blob for job status.

I ported a python2 app with py2to3 a couple months ago and it wasn&#x27;t completely painless.<p>The worst problem I ran into was that it didn&#x27;t know which strings were supposed to be bytes or unicode. And the program would throw a runtime error when it tried to do something like use a byte regex on a unicode string.

Would love to see some example URLs. I&#x27;m a Rubyist and don&#x27;t have any Python URLs to post in there.

Is there any static table where you can see the status of all packages this tool knows about in one glance? It would be interesting to see the overall status of how many packages that are available instead of asking for each one.

Excuse the ignorance, but wouldn&#x27;t requirement checking be equivalent to see if a &#x27;python3-&lt;package_name&gt;&#x27; is available in your package manager?<p>You can then download that, and use something like 2to3 to convert it.

Very cool. Would like to see proxy support on the xmlrpclib bits; http_proxy=... doesn&#x27;t work at present and I don&#x27;t see command line flags. (Not a hard fix, but I can&#x27;t offer a patch right now.)

Shameless plug: <a href="http://py3readiness.org/" rel="nofollow">http:&#x2F;&#x2F;py3readiness.org&#x2F;</a> If you just want to get overview of which popular packages support Python 3.

It would be great if it wouldn&#x27;t fail with:<p><pre><code> Forbidden (403) CSRF verification failed. Request aborted. </code></pre> just because the referrer is missing.

The answer is no.

Can I walk around with an artificial limp?<p>Is it sensible?