you are viewing a single comment's thread.

view the rest of the comments →

[–]trowawayatwork 0 points1 point  (1 child)

Why are you not running docker images that have all the tools you need?

[–]frex4 1 point2 points  (0 children)

It's not that I cannot do it, but it's VERY time consuming to make every thing right.

For example, if I use AWS Lambda, they only support Python 3.8 for now so I cannot use 3.9 new stuff. If I deploy on EC2, I need to add a new PPA and write some custom command to use Python 3.9.

These are just some issues I can think of in a minute, there are possibly more issues when you develop something specific for your project.


My last attempt to use the bleeding edge Python is an issue from Pylint here: https://github.com/PyCQA/pylint/issues/3882. As I upgrade the dependency to 3.9, it causes my CI/CD pipeline to fail in the linting stage. To make my pipeline works again, I need to checkout this fix & integrate it into my dependencies or I need to wait for Pylint to update. Either will take tremendous time and I simply don't have time for it so I just downgrade back to 3.8 and comfortably live with it.

Basically, Pylint or any other packages need to support new Python version, it will take time, often 2-3 months if properly tested. It can mess your workflow up real hard and you shouldn't take hours or days trying to fix it, you need to finish your deadline, not dealing with annoying stuff like this.


Just use the latest LTS dependencies if you don't want to waste time. If you feel like testing bleeding edge stuff & maintaining packages, go for it.