eladkal opened a new pull request, #61536:
URL: https://github.com/apache/airflow/pull/61536

   Running
   `breeze release-management constraints-version-check --python 3.13 --package 
async-timeout --explain-why
   `
   Resulted with
   ```
   × No solution found when resolving dependencies for split (markers:
     │ python_full_version >= '3.14' and sys_platform == 'win32'):
     ╰─▶ Because gremlinpython>=3.7.3 depends on async-timeout>=4.0.3,<5.0.0 and
         only the following versions of gremlinpython are available:
             gremlinpython<=3.7.3
             gremlinpython==3.7.4
             gremlinpython==3.7.5
             gremlinpython==3.8.0
         we can conclude that gremlinpython>=3.7.3 depends on
         async-timeout>=4.0.3,<5.0.0.
         And because apache-airflow-providers-apache-tinkerpop depends on
         gremlinpython>=3.7.3 and apache-airflow depends on 
async-timeout==5.0.1,
         we can conclude that apache-airflow-providers-apache-tinkerpop and
         apache-airflow are incompatible.
         And because your workspace requires apache-airflow and
         apache-airflow-providers-apache-tinkerpop, we can conclude that your
         workspace's requirements are unsatisfiable.
   
         hint: While the active Python version is 3.13, the resolution failed 
for
         other Python versions supported by your project. Consider limiting your
         project's supported Python versions using `requires-python`.
   
         hint: Pre-releases are available for `gremlinpython` in the requested
         range (e.g., 4.0.0b1), but pre-releases weren't enabled (try:
         `--prerelease=allow`)
         
   ```
   
   The hint means that the real error is hidden as when we find resolution for 
Python 3.13 other Python versions are not related. The fix is to specify 
python_version when we attempt to update dependencies.


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