Reco wrote: ... > Because python. Be it python 2 or python 3 - it's (in)famous for one > thing - lack of backwards compatibility. Sooner or later they replace > python 3.8 (current sid) with, say, python 3.9 - and the things will > break again. > Because they did on 3.7->3.8 transition, did before that on 3.6->3.7 > transition and this list goes long way back.
i've not had any problems with python3 here, but i don't do strange things with python3. oh, let me rephrase that, during a recent round i had a problem with a program, but that wasn't anything i did so it was somewhere in the stack of modules that program used. does that mean it was incompatible? no, it just meant there was a bug introduced which eventually got fixed. songbird
