Of course this is not the only example. It bites me at least once a month: I try to use some random python project from the internet only to find out that I'm using too new python. If I really badly need it, then it is time to set up a VM with an ancient python version. But usually I just give up, and look for a non-python solution. If it has never ever happened to anyone, then I guess I might be the only person using python in this world regularly.
But this is pretty much my point. Python3 scripts die if you try to use them with Python3 - today's python3 doesn't give a damn about yesterday's python3. Python3 scripts rot faster than milk on the sun.
Maybe just use virtual environment?
> Tell me you don't know what's a python virtual environment without telling me you don't know what's a python virtual environment
Of course you know that also that Python virtual environments are used to handle/isolate different python packages and their versions on top of the system-wide python installation, and not different versions of python runtime, so I won't even mention it. Of course in theory you can have as many different python version installed as you want on the same system, but whoever suggests that has never tried having more than 1 intentionally. I'm sure you were only joking with that post. Haha. I get it.When you say datamining, what exactly do you mean? I've never had to datamine a codebase. It's not a database.
Using the wrong terms for stuff generally flags someone for me as having no idea what they're doing. Definitely not a reliable narator so to speak. I can equally hear you say 'I haven't used this car in 6 years and it wont drive now'.
It's also pretty redflagish that you're not actually giving any specifics. Like was a module in the standard library removed, or was this a third party thing. I wonder because you said it was related to bluetooth.
That's not to say early python 3 wasn't a mess. It was, but that's certainly resolved now.