On Tue, Dec 30, 2014 at 01:37:29AM +1100, Chris Angelico firstname.lastname@example.org wrote:
On Tue, Dec 30, 2014 at 1:19 AM, Fetchinson . email@example.com wrote:
I completely understand your point but at this stage I'm only thinking of hobby projects that will probably be used by myself, my wife and our family. Nothing mainstream, google playable, etc.
For larger scale projects I'd completely agree with you, python 3 is the way to go.
Python 3 isn't just better for large projects. It's better for _every_ project. Just because you think you won't ever need non-ASCII characters doesn't mean you won't ever get any; why not take the easy way out and use Py3? (Case in point: I just sent through a pull request on a project that had a ≤ (U+2264) in a comment. Py2 complained because it used a non-ASCII character and didn't have a coding cookie. Py3 would have accepted it, though sadly it wasn't a Py3-compatible script for other reasons. ASCII simply isn't enough.)
I regularly read and produce programs and texts (and text fields in binary files) in 4 non-ascii encodings -- koi8-r, utf-8, cp1251 and cp866, less frequently in utf-16. Python 2 doesn't stand on my way. Python 3 could be better -- I simple don't know -- but Py2 is still good enough.
Oleg Broytman http://phdru.name/ firstname.lastname@example.org Programmers don't die, they just GOSUB without RETURN.