-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CT-1469] [Bug] Define Python Version when Installing Dependencies #6203
Closed
2 tasks done
emmyoop opened this issue
Nov 3, 2022
· 2 comments
· Fixed by #6204, dbt-labs/dbt-snowflake#307 or dbt-labs/dbt-snowflake#317
Closed
2 tasks done
[CT-1469] [Bug] Define Python Version when Installing Dependencies #6203
emmyoop opened this issue
Nov 3, 2022
· 2 comments
· Fixed by #6204, dbt-labs/dbt-snowflake#307 or dbt-labs/dbt-snowflake#317
Labels
bug
Something isn't working
Comments
github-actions
bot
changed the title
[Bug] Define Python Version when Installing Dependencies
[CT-1469] [Bug] Define Python Version when Installing Dependencies
Nov 3, 2022
6 tasks
This was referenced Nov 3, 2022
[Backport][CT-1469] init pr for short term python version issue fix (#375)
dbt-labs/dbt-bigquery#378
Merged
[Backport][CT-1469] init pr for short term python version issue fix (#211)
dbt-labs/dbt-redshift#215
Merged
Merged
This was referenced Nov 10, 2022
Merged
This is still an issue for me when running the
|
Merged
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a new bug in dbt-core?
Current Behavior
We don't currently define the version of python to use when installing dependencies so it just uses what's in the PATH of the runner. This recently updated to Python 3.11 which we don't officially support. This is causing some dependency installation failures.
Expected Behavior
Dependencies install without failure.
Steps To Reproduce
Run the
main.yml
action.Relevant log output
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: