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/22 18:42:20 UTC

[GitHub] [airflow] potiuk commented on issue #13838: Setting up Airflow for local development is hard

potiuk commented on issue #13838:
URL: https://github.com/apache/airflow/issues/13838#issuecomment-765611601


   My thoughts: 
   
   All for it as well. 
   
   Breeze is not at all designed for end-users :). I love the idea of @kaxil to integrate running "airflow" in the airflow command line. However there is one caveat -  the tool should be  - much more than Breeze - supported on Windows. And it should not be needed at all to checkout Airflow code to use it. So Installing airflow via PyPI and running "start-local-airflow" (or something like that) is one of the ways to do it.
   
   Unfortunately Airflow as a package is notoriously difficult to even install on Windows (not mentioning running)  - the #10388 and #12874 mentioned by @mik-laj  but also discussion at slack today (setproctitle preventing from installing airflow for user who wanted to just install  virtualenv on windows for Intellij autocompletion): https://apache-airflow.slack.com/archives/CCQ7EGB1P/p1611316718050700 
   
   So either we should improve the installability of airflow package on windows (not runnability - that's much more complex :)), or we have a different tool (either go - similar  as astro-cli or python). Go would be nicer for portability (we could relase convenience static binaries for different platforms) where python is better for our community to maintain.
   
   


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