question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bump google-api-core package version to make apache-airflow-providers-google compatible with python3.6

See original GitHub issue

Apache Airflow version: 1.10.14 and 1.10.15

Environment Official Docker image python 3.6

What happened:

The backport package apache-airflow-backport-providers-google has a dependency on google-api-core:

Those two do not overlap in any version. Setting google-api-core==1.26.3 will make it solve the dependencies again

What you expected to happen:

Should be posible to install airflow with the current constraints.

pip install apache-airflow-backport-providers-google -c https://raw.githubusercontent.com/apache/airflow/constraints-1.10.14/constraints-3.6.txt 

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
potiukcommented, Apr 2, 2021

@dinigo. Everything is as expected.

Constraints are frozen at the time of creating the apache-airflow package. And they are there to be able to install the given version of apache-airflow in a consistent way. No more, no less. They have nothing to do with the version of provider that you can install afterwards. Constraints finish their role when you have apache-airflow installed, and then you should manage your additional packages (including backport providers) on your own.

There is (and cannot be) absolutely no relation of the constraints with version 1.10.14 to the providers/backport providers (which are released on a completely dfferent schedule).

You should not use constraints to install providers/backports, this is neither endorsed not supported. You should install providers (or backport providers) separately, without constraints.

1reaction
uranusjrcommented, Apr 1, 2021

The constraint files are automatically generated from CI, and you shouldn’t be modifying them directly.

I believe the way to do it is to change the minimal version in setup.py; CI will pick them up automatically and update the constraints files accordingly.

Read more comments on GitHub >

github_iconTop Results From Across the Web

apache-airflow-providers-google Documentation
This is a provider package for google provider. All classes for this provider package are in airflow.providers.google python package. Installation¶. You can ...
Read more >
google-api-core - PyPI
The last version of this library compatible with Python 2.7 and 3.5 is google-api-core==1.31.1 . The last version of this library compatible with...
Read more >
googleapis/python-api-core - GitHub
The last version of this library compatible with Python 2.7 and 3.5 is google-api-core==1.31.1. The last version of this library compatible with Python...
Read more >
Cloud Composer version list
Version Airflow version Python versions Release date Full su... composer‑2.1.2‑airflow‑2.3.4 2.3.4 3.8.12 December 13, 2022 Decem... composer‑2.1.2‑airflow‑2.2.5 2.2.5 3.8.12 December 13, 2022 Decem... composer‑1.20.2‑airflow‑2.3.4 2.3.4 3.8.12...
Read more >
Changelog — google-api-core documentation
As of January 1, 2020 this library no longer supports Python 2 on the latest released version. Library versions released prior to that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found