Taragolis commented on issue #33688: URL: https://github.com/apache/airflow/issues/33688#issuecomment-1695586927
> **NEVER EVER UNDER ANY CIRCUMSTANCES** you should use this option in anything close to production ... test, development. **IMHO**, this variable should only use if life or carrier depends on it 😥 I hope one day we will remove this env variable completely (Airflow 3?). According to my past experience with companies who already use Airflow chance that also `_PIP_ADDITIONAL_REQUIREMENTS` uses everywhere close to 100% (or only I so unlucky), with additional side effects: broken dependencies, health checks disabled or use 10 minutes timeout and etc. And I can't see any better solution rather than disable (neutral) or terminate container (chaotic evil 👿 ) if found this variable, [on the Internet](https://www.google.com/search?q=_PIP_ADDITIONAL_REQUIREMENTS) a lot of suggestion to use it 😞 😢 > pyiso8583 plyvel schema jsonschema redis==4.3.4 I've bet that Airflow 2.7 use [`redis >=5.2.3,<6`](https://airflow.apache.org/docs/apache-airflow-providers-celery/3.3.0/index.html) -- 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]
