Re:The Hitchhiker’s Guide to Python
by ersii on Friday May 09, 2014 @09:09PM
(#7724099)
The project is open and I feel confident they'd take a merge/pull request for that.. :-) (I know that Kenneth usually has humor and the spirit goes along well with your suggestion. ;-) ). Feel free to swing by https://github.com/kennethreitz/python-guide and have a look in any case.
Re:The Hitchhiker’s Guide to Python
by SoftwareMaven on Saturday May 10, 2014 @01:08AM
(#7724571)
My thoughts exactly. We use python extensively, so have a large code base laying around, and, even with that, I chose Python 3 for the new project I recently started since it is fairly independent.
I'd word this more like "projects should use Python 3 unless you have an existing reason (a core library, existing code base, etc) to stay on 2.7". A year ago, I couldn't have said this. Six months ago, the possibility of missing, critical libraries was still very large, but, today, it's a reasonable approach (IMO, of course :).
Re:The Hitchhiker’s Guide to Python
by anon4 on Saturday May 10, 2014 @04:58AM
(#7724888)
The other bizarre to me part is how Python 2 is called "Today" and Python 3 "The future". Shouldn't they be "Yesterday" and "Today" respectively? Or maybe "The snakes of yesteryear" and "The contemporary Monty".
Re:The Hitchhiker’s Guide to Python
by pdeuchler on Friday May 09, 2014 @04:50PM
(#7723186)
Always good to see this on the front page, and as a side note Kenneth is quite possibly one of the best OSS maintainers I've ever encountered. I made a tiny, pedantic edit a year or so ago and he treated my pull request like it was an entirely new chapter plumbing the depths of the GCC.
Re:The Hitchhiker’s Guide to Python
by tdicola on Friday May 09, 2014 @03:54PM
(#7722918)
Nice! I remember when this was posted about a year ago and it's nice to see it's been steadily maintained since then. Great list of tools, etc. that are a must know for python users.
> Also use Python 2.7.x if you’re starting to work on a new Python module.
Is this a generally accepted guideline? I'd have thought Python 3 would have caught on by now.
I'd word this more like "projects should use Python 3 unless you have an existing reason (a core library, existing code base, etc) to stay on 2.7". A year ago, I couldn't have said this. Six months ago, the possibility of missing, critical libraries was still very large, but, today, it's a reasonable approach (IMO, of course :).