r/Python • • May 26 '14

Python 3 is killing Python

https://medium.com/@deliciousrobots/5d2ad703365d/
0 Upvotes

147 comments sorted by

View all comments

-2

u/mouseroot May 26 '14

I agree with this article, When I first started python i assumed the latest was the best, as is true with just about everything else only to find out print is print() and at the time none of the libraries i was looking at were even supported. so much like when I was trying out DevC++ and trying Cout << "hello world" instead of cout << "hello world" it was very frustrating to learn that not only is python 3.X not recommended its almost like windows ME...just a really really bad idea and for people who are looking to intro into python chances are they will go down the same road and in most cases give up altogether.

Porting isn't the answer in my opinion, I think killing off the 3.X branch and possibly adding more "batteries" to python 2.X would be the best idea or maybe focusing on fixing the issues with 2.X or hell fork 2.X and call it 4.X the biggest issue i still see is package management pip is boss why the hell isnt it part of standard python? node has npm, ruby has gems, python should ship with pip. and people saying "its getting there" the facts are its been getting there since its inception its time to move on.

most Linux distros ship with python 2.X (if any python at all) after using 3.X there really isnt that much that makes it "the new python" besides some incompatibilities from 2 to 3 its not faster, its not any more efficient its just dead weight.

and if this continues python will probably lose alot more users then it gains which is really sad its a kickass langauge.

5

u/donaldstufft May 26 '14

Python 3.4 ships with pip more or less.

3

u/mouseroot May 26 '14

that's my ignorance then, I believe i used 3.2 or 3.1 and didn't even know about pip at the time. for me it was manually downloading the files and placing them in site-packages, much ignorance back then :/