jens-scheffler-bosch opened a new issue, #31366:
URL: https://github.com/apache/airflow/issues/31366

   ### Apache Airflow version
   
   2.6.1
   
   ### What happened
   
   See also discussion in Slack: 
https://apache-airflow.slack.com/archives/CCQ7EGB1P/p1684331895556709
   
   We use Airflow based on docker image `apache/airflow:2.6.1-python3.8` and 
build custom PIP packages on-top. Of course following the setup guide we source 
the constraints 3.8.txt alongside to keep a consistent setup.
   
   With the upgrade to Airflow 2.6.1 we are trying to install `Sphinx` which is 
pinned to 5.3.0, this sources the dependency of `docutils`. Constraints pins 
this to 0.20. Install of `Sphinx` fails with a dependency error:
   ```
   ERROR: Cannot install sphinx==5.3.0 because these package versions have 
conflicting dependencies.
   
   The conflict is caused by:
       sphinx 5.3.0 depends on docutils<0.20 and >=0.14
       The user requested (constraint) docutils==0.20
   ```
   
   How 
   
   ### What you think should happen instead
   
   Pip install of `Sphinx` should be possible with the standard constraints.
   
   ### How to reproduce
   
   Run:
   * `docker run -it apache/airflow:2.6.1-python3.8 bash`
   * `pip install sphinx --constraint 
"https://raw.githubusercontent.com/apache/airflow/constraints-2.6.1/constraints-3.8.txt"`
   
   ### Operating System
   
   Ubuntu 20.04
   
   ### Versions of Apache Airflow Providers
   
   Default provider packages
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   n/a
   
   ### Anything else
   
   Workaround: Patch docutils down to 0.19 manually in downloaded 
constraints-3.8.txt
   This was the version used in Airflow 2.6.0
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to