You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "raphaelauv (via GitHub)" <gi...@apache.org> on 2025/04/24 19:34:29 UTC

[PR] docs: README uv [airflow]

raphaelauv opened a new pull request, #49748:
URL: https://github.com/apache/airflow/pull/49748

   (no comment)


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "raphaelauv (via GitHub)" <gi...@apache.org>.
raphaelauv closed pull request #49748: docs: README uv
URL: https://github.com/apache/airflow/pull/49748


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2832684095

   This is a standalone installation docs. Which indeed can be installed with `uv`. And yes we could potentially add `uv` and installation method - but that woudl require a new link on https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html -> which currently explains only `pip` - possibly we could add `uv` as optional there - but that woudl require some variant docs describing it.
   
   Do you think you can provide such options (I have no problems with having it as optional to `pip` - just we need to describe it  - if we say we can install airflow with `uv`, we should describe how and make sure it works.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "raphaelauv (via GitHub)" <gi...@apache.org>.
raphaelauv commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2833243888

   Okay , thanks @potiuk for the detailed answer


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2832685208

   I  just see completely no point in adding `uv` if we do not have instructions and commit to our users on how to do it


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "raphaelauv (via GitHub)" <gi...@apache.org>.
raphaelauv commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2832650666

   Since uv is present on this docs and also in the official docker image 
   
   https://airflow.apache.org/docs/apache-airflow/stable/start.html
   
   I thought it was official 


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2832686162

   What's the point of adding it to readme otherwise @raphaelauv ? 


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2832648660

   the `uv` is not yet officially standardized for user installlation. We use it for development, yes, but user installation documentation is not really updated for `uv` purposes. If we were supporting both `uv` and `pip` as `user` facing installation we would have to update installation docs for users in `airflow-core/docs` - I do not think we are ready for that, without a discussion and agreement on devlist.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [PR] docs: README uv [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #49748:
URL: https://github.com/apache/airflow/pull/49748#issuecomment-2832716328

   And - just to be very clear about my reservations here - what happens if someone reads the the README tomorrow and says `I used uv to install airflow in production and it does not work` - what do we respond? Do we have a page that we can direct the user to when we explain how to use `uv` ? Are we sure (and checking as we do with `pip` ) that any future version of uv can be used to install airflow?
   
   I have completely nothing against `uv` - I was one of the first to proposed it to be used for our development pipelines and CI especially to speed it up. 
   
   But making it official for producion-ready installation of airflow requires way more than few words of change in README.md  for users (not for contributors/developers)- it requires documentation and commitment (and CI tests that verify that installation works - something that we do now for `pip` by running PROD imaage installation with `pip` rather than `uv` now.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org