Python 3 Wall of Shame
python3wos.appspot.com
Python 3 Wall of Shame
1–10 of 80 posts
Re: Python 3 Wall of Shame
#2Once Django is Py3K-ready, all other projects will follow suit.
Re: Python 3 Wall of Shame
#3And there's a version that shows rails3 compatibility amongst other things here:
Re: Python 3 Wall of Shame
#4Re: Python 3 Wall of Shame
#5Let's admit it. Once Django is Py3K-ready, all other projects will follow suit.
Re: Python 3 Wall of Shame
#6Let's admit it. Once Django is Py3K-ready, all other projects will follow suit.
Is Django really that big a deal in the python world? I know it is a big deal in the python web world, but the web seems a pretty small part of the python world as a whole. If I where to ask all the python developers I knew to prioritize the projects they want ported to py3, I'd imagine the results being numpy/scipy/matplotlib first followed wxpython or pyqt second followed by PIL and a whole bunch a smaller librarie…
Re: Python 3 Wall of Shame
#7Re: Python 3 Wall of Shame
#8Re: Python 3 Wall of Shame
#9funny... everyone needs to run out and convert so that the 3 people using py3k can have new packages... doh
Re: Python 3 Wall of Shame
#10Let's admit it. Once Django is Py3K-ready, all other projects will follow suit.
Django on top, followed by wxpython, scipy and mathplotlib.