potiuk commented on issue #57471: URL: https://github.com/apache/airflow/issues/57471#issuecomment-3481575690
> [@potiuk](https://github.com/potiuk) that's probably matter of interpretation, but I am referring to doc https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#installation-tools, where installation method, that I pointed can be read as recommended approach. Yes. It's still is. But nowhere there is specified that presence in constraint file means that it wil be installed. That's not how constraints work. On the other hand - in FAB https://pypi.org/project/apache-airflow-providers-fab/ you can clerly see no Pyton 3.13 <img width="624" height="228" alt="Image" src="https://github.com/user-attachments/assets/645ba452-c1f7-4b3a-9fb0-349053af1576"; /> As well as the package metadata !=3.13 is specified: ``` Metadata-Version: 2.4 Name: apache-airflow-providers-fab Version: 3.0.1 Summary: Provider package apache-airflow-providers-fab for Apache Airflow Keywords: airflow-provider,fab,airflow,integration Author-email: Apache Software Foundation <[email protected]> Maintainer-email: Apache Software Foundation <[email protected]> Requires-Python: >=3.10,!=3.13 ``` I'd think that those are much stronger signals (and totally standard and exactly the same as for any other python packages) to indicate that Fab provider is not meant to be installed with Python 3.13. Don't you think so ? Why do you think presence of the package in totally airlfow specific constraint files (which are really a hacky workaround until https://peps.python.org/pep-0751/ becomes implemented and supported for installation) is more "obvious" than those two? -- 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]
