GitHub user potiuk added a comment to the discussion: Airflow 3 packaged for nixpgks
Maybe someone here has nix package interest. But to be honest I am surprised how complex your packaging is, especially after all the effort we've made to make our packages (except the workspace setup) fully compliant with modern python packaging. Basically what you need is to: 1) download constraints for specific version 2) checkout airflow, airflow-core, task-sdk for specific version (using version tag) and build it with hatch (and `custom` hook for airflow-core) 3) choose providers you want to install 4) for each provider checkout the right tag and build it with any pep compliant builder 5) install it all It all should be taken from "user" targetted information (constraint files) - you should not really need to read any of the airflow internal pypoject.toml or provider-dependencies etc. - especially that they are supposde to be purely internal and they are by no way guaranteed to be kept in the same format etc. which means your complex python code will break at any time. We are planning a number of changes (including starting uv.lock to keep our development dependencies) and in no way we will look at compatibilty of the internal metadata we keep in the repo. So my advice is: simplify. Use only what we tell our users to install airflow and nothing else. GitHub link: https://github.com/apache/airflow/discussions/54824#discussioncomment-14188696 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
