Full-on switching Breeze development to use uv#43628
Merged
potiuk merged 2 commits intoapache:mainfrom Nov 4, 2024
Merged
Conversation
potiuk
requested review from
Lee-W,
amoghrajesh,
dstandish,
eladkal,
ephraimbuddy,
gopidesupavan,
hussein-awala,
jscheffl,
kaxil,
mobuchowski,
o-nikolas,
pankajastro,
pankajkoti,
phanikumv,
pierrejeambrun,
rawwar,
romsharon98,
tirkarthi,
uranusjr,
utkarsharma2,
vikramkoka and
vincbeck
kaxil
reviewed
Nov 4, 2024
kaxil
approved these changes
Nov 4, 2024
amoghrajesh
reviewed
Nov 4, 2024
potiuk
force-pushed
the
full-on-uv-with-breeze-development
branch
from
976c371 to
21f59a0
Compare
Since we are switching to uv, breeze dev environment can now also be managed with uv and if you fully switch to it, the workflow of managing breeze, setting the dev environment and upgrading dependencies is far simpler than airflow's so we should be able to follow the regular uv workflow for it - i.e. use uv to manage dependencies, sync, upgrade them etc. This will be really nice way for some of the maintainers to get to learn uv more and prepare for more standardisation in the future Airflow development (maybe) - when we will link uv.lock and constraints management. Documentation has been updated in Breeze's README to explain some basic way of using uv for breeze development.
potiuk
force-pushed
the
full-on-uv-with-breeze-development
branch
from
21f59a0 to
222196f
Compare
amoghrajesh
approved these changes
Nov 4, 2024
gopidesupavan
approved these changes
Nov 4, 2024
Lee-W
approved these changes
Nov 4, 2024
phanikumv
approved these changes
Nov 4, 2024
Co-authored-by: Wei Lee <weilee.rx@gmail.com>
vincbeck
approved these changes
Nov 4, 2024
pierrejeambrun
approved these changes
Nov 4, 2024
ellisms
pushed a commit
to ellisms/airflow
that referenced
this pull request
Nov 13, 2024
* Full-on switching Breeze development to use uv Since we are switching to uv, breeze dev environment can now also be managed with uv and if you fully switch to it, the workflow of managing breeze, setting the dev environment and upgrading dependencies is far simpler than airflow's so we should be able to follow the regular uv workflow for it - i.e. use uv to manage dependencies, sync, upgrade them etc. This will be really nice way for some of the maintainers to get to learn uv more and prepare for more standardisation in the future Airflow development (maybe) - when we will link uv.lock and constraints management. Documentation has been updated in Breeze's README to explain some basic way of using uv for breeze development.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since we are switching to uv, breeze dev environment can now also be managed with uv and if you fully switch to it, the workflow of managing breeze, setting the dev environment and upgrading dependencies is far simpler than airflow's so we should be able to follow the regular uv workflow for it - i.e. use uv to manage dependencies, sync, upgrade them etc. This will be really nice way for some of the maintainers to get to learn uv more and prepare for more standardisation in the future Airflow development (maybe) - when we will link uv.lock and constraints management.
Documentation has been updated in Breeze's README to explain some basic way of using uv for breeze development.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.