You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/01/04 17:55:11 UTC

[GitHub] [airflow] potiuk edited a comment on issue #13149: Failure during "airflow db init" on fresh airflow 2.0 installation

potiuk edited a comment on issue #13149:
URL: https://github.com/apache/airflow/issues/13149#issuecomment-754121480


   > Not to ignore the above discussion, but for the benefit of anyone else using poetry on top of airflow in a workflow similar to the following who is experiencing issues with flask-openid:
   
   Just wondering (I would love to understand it) - what benefit does poetry brings in this particular case?
   Is there any reason why one simply could not use `pip` alone rather than    poetry in this case? Is there a reason this cannot be done?
   
   I was thinking about switching to poetry once for Airflow (that was a long time ago: my mail from October 2018: https://lists.apache.org/thread.html/23a598f54eda27311544fbdb9503305cd214b27b211699bd37689f46%40%3Cdev.airflow.apache.org%3E) but after trying it out, I noticed that it misses a lot of the things vs. what we wanted (also checked pip-tools then but they weren't good enough either). So I really wonder what benefits people have with using poetry vs. other tools and how it fits in in the workflow you already have.
   


----------------------------------------------------------------
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:
users@infra.apache.org