o-nikolas opened a new pull request #19178: URL: https://github.com/apache/airflow/pull/19178
In [this Slack thread](https://apache-airflow.slack.com/archives/CQ9QHSFQX/p1634668910074400), a user was attempting to setup a virtual env to do some testing of code changes. The user reported: > I got the breeze initialize-local-virtualenv command to complete successfully but I still am missing packages in my venv. This is because it is not possible to specify to breeze which extras you'd like to install in the venv (this user needed azure). To get specific extras, users have to fall back to manually run commands from our docs which can be error prone. This change allows users to export the extras they'd like breeze to install for them. ## Testing Manually tested both the default case (no user export, use `devel`) and overridden case (user exports `VIRTUALENV_EXTRAS`), both cases functioned correctly and installed the expected extras. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
