Prab-27 commented on issue #60888: URL: https://github.com/apache/airflow/issues/60888#issuecomment-4103230259
I tried, but first solution (`if possible in uv - exclude other providers from workspace during the uv-sync.` ) not possible since the uv sync internally handle this using` uv lock` I’m working on the second - `if not possible to do - manually update the workspace to remove those providers from the workspace definition so that they are installed from PyPI` I followed this approach - removed` common-compact` from the `workspace member` or also `dev` if mentioned - that way we can remove it from installing from sources during uv-sync. But I don’t understand what type of group we can add this dependency to so it can be used and also installed from PyPI, or does it get worse? I think it might be better if we handle this type of dependency from the uv side - for example, by implementing a flag`(# use next version`) like #pypi, or a mechanism like an `Index flag for only PYPI`. In that case, we’d need to implement this as a workspace member that can only be installed from PyPI (e.g., index = PyPI). If yes I'd happy to raise a PR there @potiuk Would you please share your thoughts on this ? -- 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]
