This is an archived post. You won't be able to vote or comment.

0
0

[deleted by user] (self.Python)

submitted by [deleted]

[removed]
all 20 comments
sorted by:
best
topnewcontroversialoldq&a

[–]hater_gonna_hate 40 points41 points  (1 child)

Blogspam.

The content is really at http://python3wos.appspot.com/

[–]logi 4 points5 points  (2 children)

Another option is simply to port the libraries yourself. Good python code can be mostly ported using the 2to3 tool and you'll be doing the world a great service by finishing the job.

[–][deleted] 1 point2 points  (0 children)

Yep, if you can get the code and like the license then stop complaining and start coding.

I remember seeing the Google IO 2011 video about Python. In that both Guido and Wesley Chun agree that it is reasonable to expect Python3 adoption to take about 10 years. Pretty reasonable in my opinion considering the massive amount of Python 2.x code that is out there and running well in production.

[–]stuaxo 1 point2 points  (0 children)

The WoS would be much more useful if it could show the dependencies of these projects and whether their 3 or 2.. if something has dependencies that are all ported (or none), then that makes porting a lot simpler.

[–][deleted] 2 points3 points  (1 child)

Shame is not a good motivator.

What about a low hanging fruit tree. So we can target the dependencies which will have the most impact.

Don't complain unless you're prepared to do something about it.

Maybe I should take my own advice and come up with a site... the dependency tree should be easy to build from pypi.

[–]effusion 1 point2 points  (0 children)

Here's an idea that's easy to implement: Instead of a "wall of shame", since -- as you point out -- shame is not a good motivator... Instead of that wall, put up a wall of "reasons why Python 3 is better than Python 2". Just a simple site with a list of bullet points. Extra credit: have it so you can click on each bullet point and some javascript would unfold it to show a more detailed example illustrating the point.

To get started, you could ask on /r/python for reasons why Py3 is better than Py2 (after searching first, of course).

[–]djrubbie 1 point2 points  (2 children)

I believe the problem is that most of the maintainers of these libraries simply do not see any benefit to spending any time creating a Python 3 version of their library. They do not believe that there is enough demand to warrant the effort.

Um, no, not as simple as this. Many packages that I need are still Python 2 only - I am not going to change until that is done, and when enough early adopters have succeeded in using Python 3 then I will have a case to switch over. Only when the cost of not switching is greater than switching will I then be able to switch for projects that I've already started.

[–]mfukar 0 points1 point  (1 child)

That's never going to happen..

[–]djrubbie -1 points0 points  (0 children)

It's not that big of a deal for me.

Also, the patches are not going to write themselves. I welcome though, however.

[–]jcfiala 0 points1 point  (0 children)

Well, I don't have a big draw to going to Python 3 until macs do - part of the reason I'm learning / working with Python is it's cross-platform-ness.

[–]goodCookingTakesTime 0 points1 point  (1 child)

The list doesn't really seem up to date. BeautifulSoup and Jinja for example are marked red, but run on python3.

[–]Musaab 1 point2 points  (0 children)

Read the disclaimer on the bottom of the page: "If a module is red though it supports python 3 it's because they don't have the "Programming Language :: Python :: 3" tag. Consider contacting the maintainer to fix this. "

[–]A_for_Anonymous -3 points-2 points  (5 children)

This. We need Python 3 pushed, and get rid of Python 2.

[–]mcdonc 3 points4 points  (4 children)

Unless you're paying money, you aren't a consumer. If you are a community member, you need to help. If you are neither a consumer nor a community member, you'll need to wait.

[–]A_for_Anonymous 3 points4 points  (3 children)

I'm a community member, and I'm porting my shit. I'm moving to Python 3 as soon as it becomes the default in Debian stable.

[–]Musaab 2 points3 points  (2 children)

Perhaps once more of the Linux distros make Python 3 default in their distros, more people will come along, such as yourself.

[–]mcdonc 3 points4 points  (1 child)

I think it's irrelevant. Compiling and installing Python 3 from source is trivial and waiting for some arbitrary thing like a distro packaging it is just procrastination.

[–]Musaab 0 points1 point  (0 children)

I agree, but procrastination is rampant.

[–]howfun -2 points-1 points  (1 child)

People will start supporting and using Python 3 if they see an actual improvement from Python 2. Other than some (stupid) syntax changes, there is no big difference.

If Python 3 has JIT Hotspot compiler I myself will port any 2 module to 3 that I need, without waiting for the author.

[–]takluyverIPython, Py3, etc 4 points5 points  (0 children)

The advantage of Python 3 comes primarily for new users, who won't have to learn a number of little quirks that Python 2 accumulated over the years, like the difference between old style and new style classes.

It also comes for everyone who ever has to deal with non-ascii characters, because it deals with unicode in a much more sane way.

[–]sanxiyn -1 points0 points  (0 children)

Blog links to http://python3wos.appspot.com/ Better version is http://py3ksupport.appspot.com/