cchepelov commented on pull request #10617:
URL: https://github.com/apache/airflow/pull/10617#issuecomment-696208338


   My apologies, I’ve been sidetracked and could not yet finish the patch 
against the 2.0 branch (playing whack-a-mole with additional ’sys.path leaks’), 
although I’d reckon I’m 95% there.
   
   I hope to publish it tomorrow. 
   
   Kamil is right you probably ought to take the patch as I originally sent it 
and attempt to integrate it into your system if that works for you. 
   
   
   
   
   > Le 21 sept. 2020 à 16:45, Kamil Breguła <[email protected]> a écrit 
:
   > 
   > 
   > if you can, please integrate this patch yourself. This PR target to 
Airflow 1.10 and we are focusing on Airflow 2,0 development. There is a long 
way to go before this change could be released in the 1.10 release,
   > 
   > First, we need to prepare an PR for Airflow 2.0. Once it gets merged we 
can work on a change for Airflow 1.10, but we have a lot of differences between 
releases, so we would have to prepare many other dependent changes. we have too 
much work on Airflow 2.0 to spend time on this bug. I would be happy to help if 
you would like to start working on a change for Airflow 2.0.
   > 
   > On other hand, we are getting closer to 2.0 and we also need to have some 
"nice feature" in 2.0 to get more people exited to migrate to it.
   > 
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub 
<https://github.com/apache/airflow/pull/10617#issuecomment-696162904>, or 
unsubscribe 
<https://github.com/notifications/unsubscribe-auth/AALR7ME4YIM4KS5ZQU4DSD3SG5RI7ANCNFSM4QNQIZPQ>.
   > 
   
   


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

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


Reply via email to