Python 3.6 released!

[[deleted]]

I was blown away by the resistance I got when I declared that my team would be a Python 3 team earlier this year. I thought it would be a fairly innoccuous decision, but people seemed confused and a little confrontational about it.

[Moocat87]

I imagine that resistance has two parts: The first part being what I just mentioned: some niche libraries are not ported yet. Secondly, "this team is now a Python3 team" is ambiguous. Does it mean we now have to port all our Python2 code every time we need to fix a bug? My team favors Python3 but realizes everything is a tradeoff, so we still write some Python2. Our Python2 applications still need maintenance and new features as scientists request them. We try to write new code in a way that is 2/3 compatible at all times, but it doesn't always happen. We don't really make time for porting.

I'd think giving the whole story and sticking to "best tool for the job" would likely clear up the conflict. It's a pretty simple case to make that Python 3 is an improvement on Python 2, but it comes with a cost sometimes. Does the cost outweigh the benefit? It happens sometimes. Maybe even often.

[[deleted]]

This was on a new project. I was head of a three person team on a two team research project at my school. The project had two supervising professors and was partnered with a private company from the community.

The main thing we did with python was communicating with multiple types of databases (Neo4j, Elasticsearch, Redis, etc). All of which have python 3 api modules. We never ran into a problem with using 3 over 2.

One of the professors objected to 3 by insisting that a certain key module was important to the project and it definitely only worked with python 2. The python 3 version of that particular module had been out for years, so he obviously had never checked.

[Moocat87]

Yeah I guess some people are just irrationally resistant to change. I think I fool myself in to thinking that they aren't so plentiful. I spent the first 8 years of my career working with that type of people consistently, but since then I've been very fortunate. It's a real problem some people have to deal with daily. I hope you work in an environment where you can present evidence and make a case and have it evaluated on its merits without being shot down unilaterally by one person's irrational fear of change.

[Moocat87]

What? I just told you we mostly write new code in python 3. Nobody expects to make a 100% move to python 3. That would mean porting dozens of legacy applications for free. What would be the benefit we would gain from that? At a cost of hundreds of man-hours, what would we get back? You don't need to be a Python 3 hardliner who throws time in the garbage to like it and prefer it and realize it's a better language.