"More things happened in the past than the present" is an excellent quote and I'm probably going to steal it.
Sucks for Python. They should never have broken compatibility, womp womp.
EDIT: Just to be clear, I have zero pity because the documentation and old code doesn't just disappear when the compatibility breaks. Same for old libraries that may not have been updated to 3.0 for any number of reasons. The exact same thing will happen if you're looking up Python resources the normal way. This is not an AI problem, this is a "don't break compatibility" problem.
I'm doing Python at *important job* atm and on our platform, the industry standard RHEL 8, the Python version used is 3.6.8.
So not just answering with stuff obsoleted by 3.10 is fine I think ...
@Ash_Crow @rastilin @esther_alter If anything, the incompatible changes are probably easier for the model to handle.
If you're using the compiler as a source of feedback while training a model, incompatible changes could be flagged immediately. Catching obsolete syntax that is still valid is a more difficult problem.