Aahz wrote: > I believe that it would be a shame and a disservice to Python if there > were a large proportion of the Python community that discouraged the use > of 3.0; I also believe it would be a shame and a disservice to Python if > you (and other people) tell conservatives like me that we should keep our > mouths shut. I don't think being honest about the situation is going to hurt anything in the long run. There are lots of advantages to 3.0, but also plenty of good reasons to stick with 2.x as well. At this point in time, my own recommendation would be that if someone doesn't have time to do a proper evaluation of the situation (talking production development here, not "learning for fun"), then I would probably still point them at 2.5. That recommendation will probably change to 2.6 in a couple of months (since it usually takes a few months after a release for the rest of the Python ecosystem to catch up with a new 2.x release). If they have the time though, my recommendation would be for them to do their *own* evaluation, looking both at things that favour 3.0 like Unicode handling and general developer convenience, as well as the things that currently favour 2.x like IO speed and availability of 3rd party libraries. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4