I'm stuck developing Python 2 code that needs to run under Jython due to system constraints. Unfortunately, I can't migrate to Python 3 as Jython only supports Python 2. I need some advice on Python 2 tooling to help with linting and formatting my code. I've installed Python 2 using pyenv and set up virtual environments with `virtualenv`, but I'm having trouble getting modern tools like Black, isort, and flake8 to work. I know that Python 3 tools have some backward compatibility for Python 2; can I use these tools effectively for my Python 2 code? Also, if you have experience with Python 2 in this day and age, how would you tackle these challenges? Any insights would be appreciated!
5 Answers
Seriously, have you considered looking for another job? It sounds like a real pain dealing with this outdated setup. You deserve better!
You could also try using Docker for the Python 2 environment. Pull the official Python 2 image and install the tools you need there. It simplifies the version management and keeps things isolated.
Why are you still using Python 2 in 2026? I get the struggle with legacy systems, but surely there's a way to transition. Why not push for a migration?
I feel you. Some industrial solutions stick with older tech for various reasons — it's a tough spot to be in.
Back in the days of Python 2, I used flake8 for linting and autopep8 for formatting. Older versions of these tools should still function proper, so consider looking for those. You might also check if you can find versions that still support Python 2 under Python 3's umbrella.
Yeah, it's a bit tricky finding those older versions. I suspect a lot of tools we currently use were compatible with Python 2 at some point, so if you look carefully, you might find what you need.
I suggest setting up separate virtual environments: one for Python 2.7 and another for your Python 3 tools. You can use a yaml file with pre-commit hooks for formatting and linting. This way, you specify targets for both versions and manage dependencies more effectively.
The short answer is Jython. Our ETL workflows rely on it, and we have no control to upgrade the system. If it were up to me, I'd have moved on years ago.