potiuk edited a comment on issue #14231: URL: https://github.com/apache/airflow/issues/14231#issuecomment-779325403
Oh yeah `./breeze initialize-local-virtualenv --python 3.6` is just a convenience setup to do *just* this - setup the virtualenv for either Linux and MacOS automatically. No more, no less. It's just a convenience way of running iinitialization, creating the empty sqlite database and initializing configuration for airflow. With `breeze` being entrypoint for everything else it seems reasonable to add it there. And it worked just fine until 7 days ago. * `cryptography` - is a new problem introduced 7 days ago: https://github.com/pyca/cryptography/issues/5771 * `openssl` was mentioned in the instructions provided by 'initialize local virtualenv` * `brew install mysql` was also suggested when the "initialize" command failed This is the message printed when the `initialize` command fails: ``` ####################################################################### You had some troubles installing the venv !!!!! Try running the command below and rerun virtualenv installation brew install sqlite mysql postgresql openssl export LDFLAGS=\"-L/usr/local/opt/openssl/lib\ export CPPFLAGS=\"-I/usr/local/opt/openssl/include\ #######################################################################" ``` Similar message is printed when you run `breeze initialize-local-virtualenv` on Linux. It tells you the `apt` command that you most likely need to run to have it succeed. So what @mik-laj is proposing here has already been working and implemented as `breeze initialize-local-virtualenv` command interactive instructions. My proposal is then @sdanbury - maybe you can make your first PR and: * fix the `cryptography` issue (I believe it is a single env variable to add) * display all the instructions not after but also before initialization (and ask the user to confirm it) * make the message displayed in YELLOW to grab user attention (we recently started to use coloring of terminal output). * review the docs to see if we have those prerequisites nicely descrbed I think the "interactive" single command that tells you what to do is better than list of prerequisites in docs (although we have both already I believe). Simply fixing what was already there and working seems better than reinventing stuff. @mik-laj - what do you think? Do you have anything agains interactive setup in this case? ---------------------------------------------------------------- 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]
