News for hackers. Stuff that matters.
Re:Python 3 can revive Python by rdtsc on Monday May 26, 2014 @09:13PM (#7802363)
> I'm always skeptical to hear that a developer has moved from X programming language to Go.

I see what you mean. Also, presumably those that didn't switch, that use and love Python, are not very compelled to write a "We are still staying with Python" blog.

And I think they should. Marketing and perception is important.

Re:Python 3 can revive Python by chrismonsanto on Tuesday May 27, 2014 @04:36AM (#7803498)
I'm using Python 3.4. All the libraries I need are available, including the world's best database library, SQLAlchemy. It's a more pleasant experience than Python 2.x. And I have the peace of mind knowing that I'm not stuck on a legacy, deprecated platform.

I used to stick up for Python 3 on HN and other places but I've given up. I have no interest in converting people going to Go. And no matter what Python (or any other language) does, they are going to lose users to JavaScript.

Also, my experience is that people who feel passionate about Python 2.x will shout down people who are using Python 3 with "nobody uses Python 3." Who has time for that?

Re:Python 3 can revive Python by sergiosgc on Tuesday May 27, 2014 @07:14AM (#7803846)
I thought I was alone. I also stopped trying to convert people to Python 3. It is a much better language. By this point, it should be obvious. After taking it for a test lap, and after cursing at forgetting parenthesis on print for the hundredth time, you get it. Anyone who uses python and, by this time, hasn't taken python 3 for a test run isn't worth my advocacy time.
Re:Python 3 can revive Python by adamc on Tuesday May 27, 2014 @08:31AM (#7804109)
I don't think it's a question of test runs. For most of us, it's a question of waiting for various libraries to be ported.
Re:Python 3 can revive Python by kazagistar on Wednesday May 28, 2014 @08:41PM (#7813943)
The porting is not that hard. Almost every library which isn't ported at this point is probably legacy, depreciated for something significantly better, or abandoned.
Re:Python 3 can revive Python by pekk on Tuesday May 27, 2014 @02:10PM (#7805909)
How do you know what "most of us" think?
Re:Python 3 can revive Python by collyw on Tuesday May 27, 2014 @03:37PM (#7806368)
speaks to people, reads forums, participates in conversations like this....

When I have seen people talking about sticking with Python 2, its either because A) why bother I don't need to B) a specific library is not Python 3 yet.

Re:Python 3 can revive Python by pekk on Tuesday May 27, 2014 @05:44PM (#7807062)
Selective hearing has not provided the other side of the story. Because it's not true at all that everyone or even a clear majority agrees with the viewpoint you've expressed
Re:Python 3 can revive Python by collyw on Tuesday May 27, 2014 @03:34PM (#7806355)
You say it is a much better language. I see very little difference between the two.. With the exception of exceptions, and print I think all the changes must be to language features I don't know about / use.
Re:Python 3 can revive Python by shadowmint on Tuesday May 27, 2014 @06:30AM (#7803748)
Spot on. Id love to see a bunch of 'I swapped to python 3 and it was amazing because... [reason]' posts.

If nothing else It'd illustrate clearly either the python 3 folks haven't got a leg to stand on (unable to come up with any tangible real life [reason]) or that there are actually compelling reasons to swap over to python 3; in which case we can point people to those posts in threads like this.

(personally I forayed into 3 but couldn't find any [reason] to stay there; I keep dropping into threads like this hoping to find one...)

Re:Python 3 can revive Python by Aardshaark on Tuesday May 27, 2014 @11:45AM (#7805032)
Here's a small reason I found when refactoring some code today:

http://legacy.python.org/dev/peps/pep-3102/

Like I said, it's a small reason, but it would have made my life much easier today. Enough small reasons add up.

Re:Python 3 can revive Python by collyw on Tuesday May 27, 2014 @03:39PM (#7806381)
I had some bug in a Django library, that went away by using Python 3. Can’t remember what it was exactly, but it was related to Unicode support.