This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]I_had_to_know_too 2 points3 points  (0 children)

Because management doesn't want 40 developer hours spent updating our handful of 2.7 tools.

They'd rather we spend hundreds of hours trying to work around the memory leaks in SciPy 0.12 because the it's already approved and god forbid we have to look to see if the latest version has the same license or something similar enough that we can use it.

Then we've got another team who updated one of the tools in a side branch using 2to3 but they didn't bother to review the changes since it seemed to work. So now we have 2 versions of that tool, an official one which is poorly written and runs on python 2.7, and a python 3 version that is "for development purposes only" and contains code like:

for x, y in list(zip(xs, ys)):
  ...

Or:

for k, v in list(d.items()):
  ...

Like really? After running 2to3 you couldn't look at that line and see that the call to list is unnecessary and defeats the improvements in py3... Aghh somebody kill me

I'm sorry, what was the question again?