-
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-3325] [Tech Debt][Spike+] Test dbt-core
with Python 3.12
#9007
Comments
dbt-core
with Python 3.12dbt-core
with Python 3.12
Deprecation notices appear when you run
|
I get the warning when I run dbt debug - also using dbt-postgres and Python 3.12
|
FWIW those seem to come from dependencies rather than dbt-core itself. |
Hi folks - I identified a new problem with dbt-core and Python 3.12.1. 3.12 formally removed |
Hello - is there an update on this issue? It doesn't look to be a major reimplementation in the dbt-core logic - isolated to this file I believe: dbt-core/blob/main/core/dbt/task/test.py. I believe this logic would just have to be implemented directly instead of using strtobool: https://docs.python.org/3.9/distutils/apiref.html#distutils.util.strtobool We'd like to stay on the current version of Python within a reasonable timeframe to reduce exposure to vulnerabilities. Thanks so much!! |
dbt-core
with Python 3.12dbt-core
with Python 3.12
Hi all, Python 3.12 support will be included with upcoming Thanks! |
Housekeeping
Short description
Python 3.12 was released last month, let's test that
dbt-core
works with thishttps://www.python.org/downloads/release/python-3120/
Acceptance criteria
Bundles can be created with Python 3.12dbt-core
1.7.9 and 1.8.0b1Impact to Other Teams
Will backports be required?
No
Context
https://docs.getdbt.com/faqs/Core/install-python-compatibility
“New dbt minor versions will add support for new Python3 minor versions as soon as all dependencies can support it. In turn, dbt minor versions will drop support for old Python3 minor versions right before they reach end of life.”
The text was updated successfully, but these errors were encountered: