Arch Linux uses Python3 as the default system Python, which I found a bit daft as almost every Python library I use relies on Python 2.x.
Python 3 Wall of Shame
71–80 of 80 posts
Re: Python 3 Wall of Shame
#72I am currently doing a similar sort of website, but trying to limit it to popular projects only. Also trying to group together a lot of the python 3 related articles and porting tips. My current research can be found here: http://goo.gl/SCImr Any corrections, or ideas for what can be on the site would be appreciated.
You're welcome to use content from https://bitbucket.org/pypy/compatibility . There is a growing list of dependencies at https://bitbucket.org/pypy/compatibility/wiki/depends.yaml .
That just saved me a hell of a lot of work. Thank you!
Re: Python 3 Wall of Shame
#73The wall of shame itself is written in Python 2.
Re: Python 3 Wall of Shame
#74Earlier quoted context omitted.
You're welcome to use content from https://bitbucket.org/pypy/compatibility . There is a growing list of dependencies at https://bitbucket.org/pypy/compatibility/wiki/depends.yaml .
That just saved me a hell of a lot of work. Thank you!
You're welcome. You can even clone that and make a wiki for py3k from it if you want. There's a script (in the wiki repo) to parse the wiki into YAML, so reuse of the current content should be easy no matter what format you want.
Re: Python 3 Wall of Shame
#75does this highlight how hard it is to move from python 2 to 3?
sidenote: love the pink select must be html5 boilerplate :)
Re: Python 3 Wall of Shame
#76The wall of shame itself is written in Python 2.
Well of course - there's no libraries for Py3k.
Re: Python 3 Wall of Shame
#77Pretty much inaccurate data. For example many project release under a new "3k" name, and leave the old ones. One of those is a backport of a stdlib module (multiprocessing), etc. So, it's bad data, and misleading, but I admire the idea.
Thanks :) You'll notice I removed multiprocessing. I'm considering removing setuptools as well. Too bad I have to hardcode these things. I wish there was some metadata about a package having a py3k counterpart.
Re: Python 3 Wall of Shame
#78Is this a wall of shame for the packages in red, or for Python 3 itself?
I think my inspiration was a little of both.
Re: Python 3 Wall of Shame
#79"Wall of Shame"? Really? As someone who's project appears on this list (and in the WRONG color) all I can say is that I don't think anyone is trying to dis Python 3.x. Support will come when a critical mass of developers are using 3.x. I know it's kind of a chicken and egg problem but this seems to be saying that it's the package developer's fault and I don't really think that's fair or true.
Which package is in the wrong color?
Re: Python 3 Wall of Shame
#80Earlier quoted context omitted.
Google only supports 2.5 for anything python related. Take a look at the python protobuf client: http://code.google.com/p/protobuf/issues/detail?id=66&q=... Don't expect google to upgrade anytime soon.
Python 2.7 is now on the roadmap. http://code.google.com/appengine/docs/roadmap.html
Oh now that'll be nice. Wonder if they'll let let me future import ;) I seem to recall some restrictions in how they implemented the VM for AppEngine.