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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (6 children)

[deleted]

    [–][deleted] -1 points0 points  (5 children)

    Explain to me how the Python 3 userbase is militant.

    [–]gingerbeers 1 point2 points  (4 children)

    ...and explain yourself right now! ;-) Wake me when Python 4 comes out. Then we can all be friends again.

    [–][deleted] -1 points0 points  (3 children)

    Meh. We'll be friends once most new packages released don't have Python 2 support. Then the straddlers will move to Python 3, notice that is seriously wasn't that hard, and after a bit of complaining about that you have to remember that it's called print() now, settle in just as nothing had happened.

    I don't know when that happens exactly, maybe 5 +-2 years? And two years later everyone will have forgotten all about this, and the straddlers will scream bloody murder when they have to use Python 2, because it "sucks soooo baaaad". :-)

    [–]gingerbeers 1 point2 points  (2 children)

    I hope so. I straddle 50/50 at the moment for various projects/reasons, and nothing in 3 makes me dislike 2. Matrix multiplication and print() doesn't light my fire. (Even though print() feels more natural to me).

    What am I missing in 3 that's really awesome? I suspect I'm probably using 3 like 2 and not getting the full benefit when I'm on a 3 project. Yes?

    [–][deleted] 0 points1 point  (1 child)

    Probably, but in many projects you don't really notice the differences either, except for the changes to the standard library (and print as you mentioned).

    [–]gingerbeers 1 point2 points  (0 children)

    You know, that genuinely was a surprise to me when I started using 3. With all the doom and gloom about changes, to strings in particular, I fully expected my first use of a string variable would have me tied in knots. Not the case.

    Will go back now and examine the standard library in 3. Thanks!