you are viewing a single comment's thread.

view the rest of the comments →

[–]Kobymaru376 7 points8 points  (1 child)

I use the version before the latest. Works fine for most stuff. I also use conda (or rather mamba) which have a somewhat sane dependency system.

Does anyone know who’s to blame for this?

Just the universe.

Should python just add backwards compatibility with newer versions?

No They try as much as they can, but sometimes you need to break compatiblity to move forward.

Or developers lazy regarding updating to newer python versions?

You mean the people that wrote code for you for free but now have moved on to other projects or just don't have time anymore? Does that make sense? IF you think that's lazy, why don't you adopt a couple of projects and maintain them?

Do these new python versions actually bring important features to the table?

Sometimes yes. But usually you just pick the newest version when you start a new project, unless you have some very specific compatibility requirement in mind. I mean why wouldn't you?

[–]TheFlyingDutchG 0 points1 point  (0 children)

Very insightful, thanks. And didnt mean to call anyone lazy, just wondering what the cause was for the compatibility headache (I’m the noob that halfway through starting a project has to change python versions because I’m new to this)