potiuk opened a new issue, #23848:
URL: https://github.com/apache/beam/issues/23848

   ### What would you like to happen?
   
   I know it is eaarly (Python 3.11 has just been released yesterday) but we 
are hoping in Apache Airflow to a much faster cycle of adding new Python 
releases - especially that Pyhon 3.11 introduces huge performance improvements 
(25% is the average number claimed)  due to a very focused effort to increase 
single-threaded Python performance (Specialized interpreter being the core of 
it but also many other improvements) without actually changing any of the 
Python code. 
   
   Apache Beam was triaditionally one of the latest dependencies of Airflow to 
support newer Python version so this issue is here to make you aware that we 
are eaager (also to help if needed) to make it faster, possibly by talking to 
dependencies of Beam as well (who are oftten also direct dependencies of 
Airflow) and help them as well. I perfectly understand we need to bubble up 
support so that your dependencies support them first.
   
   Nice summary of Py3.11 support is here: https://pyreadiness.org/3.11/  - 
it's not very green obviously, but I hope it gets greener soon.
   
   I'd appreciate if someone in the Beam team attempted to migrate and have a 
PR running (and failing possibly until all prerequisite are met so that we can 
also track the progress and possibly help each other to solve any problems.
   
   I just opened such PR in Apache Airflow yesterday and plan to keep it open 
until it gets green :)
   
   https://github.com/apache/airflow/pull/27264
   
   I think it would be fantastic if we could as the open source community 
migrate to the new Python much faster.
   
   Looking forward to cooperation on that one :)
   
   ### Issue Priority
   
   Priority: 3
   
   ### Issue Component
   
   Component: sdk-py-core


-- 
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