dbt fails with ImportError: cannot import name Unpack or override from typing_extensions

TL;DR

For "ImportError: cannot import name 'Unpack' from 'typingextensions'": a community member worked out the exact matrix and the fix: pin typing\extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (0.4.1 for the dbt 1.7 line, which needed override). The reporter installed typing\_extensions==4.7.1, re-ran, and confirmed the error was gone.

ImportError: cannot import name 'Unpack' from 'typing_extensions'

Steps

1. Running dbt on Databricks failed at import time with ImportError: cannot import name 'Unpack' from 'typing_extensions', and on newer setups with cannot import name 'override'. The root cause was a version conflict: dbt-semantic-interfaces needed newer typing_extensions names than the installed version provided. A community member worked out the exact matrix and the fix: pin typing_extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (0.4.1 for the dbt 1.7 line, which needed override). The reporter installed typing_extensions==4.7.1, re-ran, and confirmed the error was gone. A maintainer also backported the 0.4.1 fix for the dbt 1.7 line.
2. Your installed typing_extensions is too old for what dbt-semantic-interfaces imports (Unpack on dbt 1.6, override on dbt 1.7). Fix: either pin typing_extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (use 0.4.1 if you're on the dbt 1.7 line). Re-run dbt after the change and the import error should be gone. The reporter did the pin and confirmed the error disappeared.

When to use

You are seeing this: Running dbt on Databricks failed at import time with ImportError: cannot import name 'Unpack' from 'typing\extensions', and on newer setups with cannot import name 'override'. Use this skill when you run into "dbt fails with ImportError: cannot import name Unpack or override from typingextensions".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: typing_extensions 4.7.1, 0.2.3, 0.4.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The root cause was a version conflict: dbt-semantic-interfaces needed newer typing\_extensions names than the installed version provided.

A user asked: Running dbt on Databricks failed at import time with ImportError: cannot import name 'Unpack' from 'typing_extensions', and on newer setups with cannot import name 'override'. The root cause was a version conflict: dbt-semantic-interfaces needed newer typing_extensions names than the installed version provided. A community member worked out the exact matrix and the fix: pin typing_extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (0.4.1 for the dbt 1.7 line, which needed override). The reporter installed typing_extensions==4.7.1, re-ran, and confirmed the error was gone. A maintainer also backported the 0.4.1 fix for the dbt 1.7 line. The verified answer: Your installed typing_extensions is too old for what dbt-semantic-interfaces imports (Unpack on dbt 1.6, override on dbt 1.7). Fix: either pin typing_extensions==4.7.1, or upgrade dbt-semantic-interfaces to 0.2.3 (use 0.4.1 if you're on the dbt 1.7 line). Re-run dbt after the change and the import error should be gone. The reporter did the pin and confirmed the error disappeared. Thread: https://vectle.com/threads/thr_08hL6MkceKV-IyMTuc7glw