r/Python Pythonista 6d ago

News The Move to Python 3 Begins!

As someone who spent decades in the mainframe community, I find it ... humorous ... that there are legacy Python2 code bases that are only just (or have yet to consider!) moving to Python3.

https://www.eveonline.com/news/view/the-move-to-python-3-begins

300 Upvotes

106 comments sorted by

View all comments

3

u/iluvatar 6d ago edited 5d ago

As CTO at my previous company, I had to veto developers who wanted to migrate from Python 2 to Python 3. The amount of effort required for the migration and the fairly low chance of a trouble free switch just didn't make a good business case for a working codebase that brought in millions in revenue each year and paid all of our salaries. All new development was in Python 3. But existing running code just had too high a risk and too low a reward for migrating.

1

u/HugeCannoli 5d ago

The result of this attitude is that you won't be able to hire anybody anymore, and people will leave because you are literally destroying their chance for re-employment in a different company.

1

u/iluvatar 5d ago

I'm employed to manage the IT of the company, not to enhance the future employment prospects of our employees. But your argument is flawed anyway because the majority of the code was in python 3. It's just that there wasn't the business case to justify porting the legacy application.

2

u/HugeCannoli 5d ago

I'm employed to manage the IT of the company, not to enhance the future employment prospects of our employees

And that's why they will leave you. Because you don't respect them. Let me guess, you are american?

1

u/iluvatar 5d ago

Because you don't respect them.

Incorrect.

Let me guess, you are american?

Also incorrect.

0

u/HugeCannoli 5d ago

well it certainly looks like both are correct.

0

u/GAZ082 4d ago

Software lives in a business. You have your free time to work in your pet projects that you can port from Python to rust and back if you want. If you don't like the company, just leave.

2

u/HugeCannoli 4d ago

we do, because again: if I have to spend years working with your crappy, obsolete code, my CV is compromised and I won't find employment when your business decides to "reassess the current resource allocation" and "curtail expenses by reducing the human budget".

Either keep up, or lose your employees (and good luck hiring new ones).