[Baypiggies] Companies moving to Python 3?

[Aahz]

[warning: rant ahead]

On Fri, Oct 16, 2015, Marilyn Davis wrote:
>
> OMG.  I read that only New Style was supported in Python and you had to
> inherit from object!

Anyone who has preconceptions or hearsay about Python3 should try
actually using it.

There are IMO still plenty of reasons for sticking with Python2, but
Python3 is absolutely the future, Python 3.4.3 (combined with the
preceding releases) removes several blocking factors that existed in
3.0, and it really doesn't take that much time to learn Python3.

(Yeah, I'm discounting Python 3.5 because I always wait for the .1
release.)

There are now two and only two categories of reasons for sticking with
Python2 for new projects: infrastructure and package availability

(Actually, there's always laziness, but that's not a good reason. ;-)

Keep in mind that Python3 is in the end a smaller leap than going from
Python 1.5.1 (where I started) to Python 2.7....  It just involves a bit
more backwards incompatibility (and not that much more, in the end, given
all the new keywords from Python 1.6 through 2.7).

Note that I myself still haven't used Python3 for anything other than
sample code (and for various reasons I've written less than a hundred
lines of Python code in the last three years -- even that code I posted
just happened to be lying around), but I believe it's absolutely
essential for every serious Python programmer and *EVERYONE* who teaches
Python to be able to refute mistakes like the one you made without having
to think about it.  

Failing to learn at least the basics of Python3 is IMO irresponsible to
the Python community.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

import antigravity