From 3a0d137423d78a6cc57e3942587c10f547d7dde1 Mon Sep 17 00:00:00 2001 From: Jeremy Cohen Date: Tue, 12 Apr 2022 15:01:52 +0200 Subject: [PATCH 1/2] Note py310 support for v1.1+ --- website/docs/faqs/install-python-compatibility.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/website/docs/faqs/install-python-compatibility.md b/website/docs/faqs/install-python-compatibility.md index 276becc9f35..7f694e01586 100644 --- a/website/docs/faqs/install-python-compatibility.md +++ b/website/docs/faqs/install-python-compatibility.md @@ -1,9 +1,19 @@ --- title: What version of Python can I use? -description: "Python versions 3.7, 3.8, and 3.9 can be used with dbt Core" +description: "Python versions 3.7 and newer can be used with dbt Core" --- -As of v1.0.0, `dbt-core` is compatible with Python versions 3.7, 3.8, and 3.9. + + +The latest version of `dbt-core` is compatible with Python versions 3.7, 3.8, 3.9, and 3.10. + + + + + +As of v1.0, `dbt-core` is compatible with Python versions 3.7, 3.8, and 3.9. + + Adapter plugins and their dependencies are not always compatible with the latest version of Python. For example, dbt-snowflake v0.19 is not compatible with Python 3.9, but dbt-snowflake versions 0.20+ are. From 02b4376a3d603e4d6aefa9216d7086bdddbfc0fa Mon Sep 17 00:00:00 2001 From: Jeremy Cohen Date: Wed, 13 Apr 2022 16:53:36 +0200 Subject: [PATCH 2/2] Add note to v1.1 migration guide --- website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md b/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md index fa3f3320ef5..1f577af5609 100644 --- a/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md +++ b/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md @@ -36,6 +36,7 @@ _Note: If you're contributing docs for a new or updated feature in v1.1, please - [**Incremental models**](configuring-incremental-models) can now accept a list of multiple columns as their `unique_key`, for models that need a combination of columns to uniquely identify each row. This is supported by the most common data warehouses, for incremental strategies that make use of the `unique_key` config (`merge` and `delete+insert`). - [**Generic tests**](resource-properties/tests) can define custom names. This is useful to "prettify" the synthetic name that dbt applies automatically. It's needed to disambiguate the case when the same generic test is defined multiple times with different configurations. +- [Python compatibility](install-python-compatibility): dbt Core officially supports Python 3.10 ### For users of specific adapter plugins