แก้ไข

แชร์ผ่าน


Azure Cosmos DB Python SDK for API for NoSQL: Release notes and resources

APPLIES TO: NoSQL

Page Link
Download SDK PyPI
API documentation Python API reference documentation
SDK installation instructions Python SDK installation instructions
Get started Get started with the Python SDK
Samples Python SDK samples
Current supported platform Python 3.6+

Important

  • Versions 4.3.0b2 and higher support Async IO operations and version 4.5.2b4 and higher only support Python 3.8+. Python 2 is not supported.

Release history

Release history is maintained in the azure-sdk-for-python repo, for detailed list of releases, see the changelog file.

Release & retirement dates

Microsoft provides notification at least 12 months in advance of retiring an SDK in order to smooth the transition to a newer/supported version. New features and functionality and optimizations are only added to the current SDK, as such it is recommended that you always upgrade to the latest SDK version as early as possible.

Warning

After 31 August 2022, Azure Cosmos DB will no longer make bug fixes or provide support to versions 1.x and 2.x of the Azure Cosmos DB Python SDK for API for NoSQL. If you prefer not to upgrade, requests sent from version 1.x and 2.x of the SDK will continue to be served by the Azure Cosmos DB service.

Version Release Date Retirement Date
4.6.0 Mar 15, 2023 ---
4.5.1 Sep 14, 2023 ---
4.5.0 Aug 10, 2023 ---
4.4.0 Jun 10, 2023 ---
4.3.1 Feb 24, 2023 ---
4.3.0 May 23, 2022 ---
4.2.0 Oct 09, 2020 ---
4.1.0 Aug 10, 2020 ---
4.0.0 May 20, 2020 ---
3.0.2 Nov 15, 2018 ---
3.0.1 Oct 04, 2018 ---
2.3.3 Sept 08, 2018 August 31, 2022
2.3.2 May 08, 2018 August 31, 2022
2.3.1 December 21, 2017 August 31, 2022
2.3.0 November 10, 2017 August 31, 2022
2.2.1 Sep 29, 2017 August 31, 2022
2.2.0 May 10, 2017 August 31, 2022
2.1.0 May 01, 2017 August 31, 2022
2.0.1 October 30, 2016 August 31, 2022
2.0.0 September 29, 2016 August 31, 2022
1.9.0 July 07, 2016 August 31, 2022
1.8.0 June 14, 2016 August 31, 2022
1.7.0 April 26, 2016 August 31, 2022
1.6.1 April 08, 2016 August 31, 2022
1.6.0 March 29, 2016 August 31, 2022
1.5.0 January 03, 2016 August 31, 2022
1.4.2 October 06, 2015 August 31, 2022
1.4.1 October 06, 2015 August 31, 2022
1.2.0 August 06, 2015 August 31, 2022
1.1.0 July 09, 2015 August 31, 2022
1.0.1 May 25, 2015 August 31, 2022
1.0.0 April 07, 2015 August 31, 2022
0.9.4-prelease January 14, 2015 February 29, 2016
0.9.3-prelease December 09, 2014 February 29, 2016
0.9.2-prelease November 25, 2014 February 29, 2016
0.9.1-prelease September 23, 2014 February 29, 2016
0.9.0-prelease August 21, 2014 February 29, 2016

FAQ

How will I be notified of the retiring SDK?

Microsoft will provide 12 month's advance notice before the end of support of the retiring SDK to facilitate a smooth transition to a supported SDK. We'll notify you through various communication channels: the Azure portal, Azure updates, and direct communication to assigned service administrators.

Can I author applications by using a to-be-retired Azure Cosmos DB SDK during the 12-month period?

Yes, you'll be able to author, deploy, and modify applications by using the to-be-retired Azure Cosmos DB SDK during the 12-month notice period. We recommend that you migrate to a newer supported version of the Azure Cosmos DB SDK during the 12-month notice period, as appropriate.

After the retirement date, what happens to applications that use the unsupported Azure Cosmos DB SDK?

After the retirement date, Azure Cosmos DB will no longer make bug fixes, add new features, or provide support to the retired SDK versions. If you prefer not to upgrade, requests sent from the retired versions of the SDK will continue to be served by the Azure Cosmos DB service.

Which SDK versions will have the latest features and updates?

New features and updates will be added only to the latest minor version of the latest supported major SDK version. We recommend that you always use the latest version to take advantage of new features, performance improvements, and bug fixes. If you're using an old, non-retired version of the SDK, your requests to Azure Cosmos DB will still function, but you won't have access to any new capabilities.

What should I do if I can't update my application before a cutoff date?

We recommend that you upgrade to the latest SDK as early as possible. After an SDK is tagged for retirement, you'll have 12 months to update your application. If you're not able to update by the retirement date, requests sent from the retired versions of the SDK will continue to be served by Azure Cosmos DB, so your running applications will continue to function. But Azure Cosmos DB will no longer make bug fixes, add new features, or provide support to the retired SDK versions.

If you have a support plan and require technical support, contact us by filing a support ticket.

How can I request features be added to an SDK or connector?

New features are not always added to every SDK or connector immediately. If there is a feature not supported that you would like added, please add feedback to our community forum.

Next steps

To learn more about Azure Cosmos DB, see Microsoft Azure Cosmos DB service page.