Lee-W opened a new pull request, #76736: URL: https://github.com/apache/airflow/pull/76736
* Simplify the Quick Start for first-time local installs First-time users land on a page that mixes a local standalone walkthrough with extras, stale version pins, and unsupported-tool discussion. Those details already live on the installation pages, and they make the most-visited getting-started guide hard to copy and easy to get wrong. * Fix Quick Start and PyPI tool-install commands that fail as written Every command on the Quick Start now runs as written against a released Airflow in a clean environment. `pipx run apache-airflow standalone` fails with "No such file or directory: 'airflow'": standalone starts each component by running `airflow` from PATH, and `pipx run` does not put it there. The pipx tab is dropped from the Quick Start. On the PyPI page, `pipx run` and `uv tool install` failed the same way; they now use `pipx install --include-deps` and `uv tool install --with-executables-from apache-airflow-core`. The uv tab creates the environment with `--python 3.13`, so uv supplies a supported interpreter, and the uvx shortcut pins the documented version and its constraints file. The pip tab covers the missing python3-venv module on Debian and Ubuntu and the 404 an unsupported Python produces. The page shows real standalone output, says where the password is on later runs, and replaces the `tasks test` check with unpausing an example Dag. The components-separately steps say to use one terminal per component. * Keep the Quick Start to the two constraint-based install paths The uvx shortcut skipped the constraints file the page relies on, so it is gone, leaving the uv and pip tabs. The uv tab no longer hard-codes a Python version; it explains `--python` instead. The page now shows the SimpleAuthManager production warning that every standalone run prints and says why it appears, reads the password file from `AIRFLOW_HOME`, and quotes the error each installer gives for an unsupported Python. The PyPI page goes back to its current content. Its `pipx run` and `uv tool install` commands fail because standalone starts components by running `airflow` from PATH, which is better fixed in standalone itself. * Use a placeholder for the generated password in the Quick Start --------- Co-authored-by: Sruthi <[email protected]> Co-authored-by: Kaxil Naik <[email protected]> <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: https://chris.beams.io/posts/git-commit/ 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. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- 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]
