potiuk commented on PR #58439:
URL: https://github.com/apache/airflow/pull/58439#issuecomment-3548836111

   > > Can we go for py 3.13 instead for all these?
   > 
   > No. Because our Python code base supports 3.10 so we have to go for lowest 
common denominator.
   
   For example the whole reason why things started to fail for the user in 
https://github.com/apache/airflow/issues/56048 (look closely) - is that the 
code we were using in regular Airflow was using some things that were removed 
in 3.14. 
   
   Now - if we allow people to run their check on 3.13 - and we have some code 
that does not work on 3.10 - it will work for **them** but it will not be 
python 3.10 compliant.
   
   So absolutely safest choice is to have everyone use the same as the lowest 
denominator for Airflow code - Python 3.10.
   
   Even if Python 3.13 works a **bit** faster and has **better UX** for 
developers (it does)  - the "works for me" problem is far bigger than any of 
the gains. 
   
   In this case - optimisation goal is not for this to be "better" - but to be 
"the same for everyone".  


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to