Tableau provider not useable - Constraints points to YANKED tableauserverclient version

[DannyMeyer]

Apache Airflow version

3.1.7

If "Other Airflow 3 version" selected, which one?

No response

What happened?

The current airflow constraint points to tableauserverclient version 0.39 .. This version is YANKED and was replaced by 0.40 on the same day: https://pypi.org/project/tableauserverclient/#history

This results in an silent failed install of the tableau provider.

What you think should happen instead?

No response

How to reproduce

requirements.txt

--constraint https://raw.githubusercontent.com/apache/airflow/constraints-3.1.7/constraints-3.11.txt
apache-airflow[tableau]==3.1.7

pip install -r requirements.txt

tableauserverclient isn't installed! Also there is no notification about it.

Operating System

Debian

Versions of Apache Airflow Providers

No response

Deployment

Other

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[Jayantparashar10]

Hi @DannyMeyer, thanks for reporting this and for offering to submit a PR great catch!

I was able to reproduce the exact behavior you described with Airflow 3.1.7 + [tableau] extra using the official constraints:

--constraint https://raw.githubusercontent.com/apache/airflow/constraints-3.1.7/constraints-3.11.txt
apache-airflow[tableau]==3.1.7

→ pip install completes without errors, but tableauserverclient is not installed (confirmed via pip list | grep tableauserverclient returning nothing).
At runtime → ModuleNotFoundError: No module named 'tableauserverclient'.

Root cause
The constraints file still pins tableauserverclient==0.39 but 0.39 was yanked from PyPI on the same day it was released due to a broken wheel (missing top-level module directory → import fails even if "installed"). PyPI yanked it, and 0.40 was released as the fixed version the next day.

Pip silently skips yanked versions when they're strictly constrained (no loud error, just no install), which makes this particularly sneaky.

Existing fix reference
The apache-airflow-providers-tableau package already addressed this in later releases by adding an exclusion:
tableauserverclient >=0.27,!=0.39 (or similar pinning to >=0.40 in even newer versions see changelog entry in #61387 or around provider version ~5.3.x timeframe: "limit 0.39 version due to missing package").

For users stuck on Airflow 3.1.7 constraints, the provider package gets installed but is broken because of the frozen dep.

Suggested fixes (pick one or combine):

1. Quick user workaround :
   Install without strict constraints or override just this dep:

   pip install apache-airflow[tableau]==3.1.7 \
       --constraint https://raw.githubusercontent.com/apache/airflow/constraints-3.1.7/constraints-3.11.txt \
       tableauserverclient>=0.40
   

   (The extra pin overrides the yanked one.)

2. Project-side Update the constraints-3.1.7 files retroactively:

   • Replace tableauserverclient==0.39 with tableauserverclient==0.40 (or >=0.40,<0.41 if semver-safe)
   • Or at minimum add !=0.39 if keeping a range.
     This would prevent new users from hitting the silent failure.

Since the constraints repo/branch for 3.1.7 is still using the bad pin , updating the constraints files seems like the cleanest long-term fix.

[eladkal]

@Jayantparashar10 please do not copy paste AI generated answers. We do not need humans to post AI answer.

The AI answer is also completely wrong in the context of how we do things in Airflow and clearly the model you used did not considered our constraints policy.

@DannyMeyer The airflow constraints are just something the project offer to make things easier for users. We rarely if never update them (as policy explained in the docs). You are welcome to generate and use your own constraints - it's very easy to do.

[Jayantparashar10]

@eladkal, I see now constraints don't get updated once released. My bad for suggesting that.

Thanks for the feedback