Simple, choose for me:
Python 2 or 3?
Is python 3 the future? why?
three, it is the future
>>52089739
why?
>>52089708
3. Because strings/chars are not 'pythonic' in 2.
3 is the future, just go with it. If you can remeber the few little syntactic changes between the two youll be golden, in any event.
If you are not using a library which relies on 2 then go with 3.
It is the newest version and will probably be used by others for longer.
>>52089708
If you're building a resume, 3.
If you're looking for practical use 2.7.
>>52089747
3 is being worked on, 2 is left behind
>>52089752
nothing in two is really pythonic.
complete shitheap would be the best description of it.
Learn 3. When you finish learning 3 try to learn the main differences between both of them. It will be more useful that way - be future-proof and able to maintain/port older py2 packages
>>52089784
You can do practical things with 3 too. 2 is legacy right now and has bunch of old scripts that run on it. But with 3, there's been lot of support/development in updating many of the scripts. So yeah, 3 is up there in usability and practicality as well.
>>52089813
I'm not really a hardcore python programmer; that was just my understanding of why 3 contains all of these breaking changes.
>>52089832
>>52089784
These.
>>52089708
just fucking pick 3 and let the 2 version die. There are still lot's of software that use the version 2 but there is not a single valid reason why you should develop new software using python 2
Python 3 is the future, I have used mostly Python 2... But now that the libaries I use have been ported, that's not really necessary. I should probably use 3
>>52089708
Two if you need it for existing libraries/resources.
Otherwise, go with three.
If you learn two, it's pretty easy to transfer over to three, there's just a few differences.
I think the answer is 2.
3 is not the future.
Swift. Lets talk about Swift...
Kolme
>>52089708
>>52089747
2 is on life support. 3 is the future because they're no longer updating 2 with new stuff and support will only last for so much longer.
>>52091610
Miltähän Kiiran pylly haisee?
is there a "Swift playground" for python?
Why do you hate Swift so much?
>>52091682
>Apple™'s™ New™ Programming™ Language™ Swift™
take a wild guess
>>52091704
Nice one
I think im going with apple Swift in 2016.
>>52089708
Obviously the past is the future.
>>52095202
how?
asyncio is a great module.