From c27940dfdbff4ac23d179554f238ad8fce79e0e7 Mon Sep 17 00:00:00 2001 From: Pranav <85227306+Pranavchiku@users.noreply.github.com> Date: Thu, 29 Jun 2023 23:59:41 +0530 Subject: [PATCH] Replace `datatime.timedelta()` with `datetime.timedelta()` in codebase (#207) ## Fixes Fixes #206. ## Changes With this PR, I am replacing `datatime.timedelta()` with `datetime.timedelta()` in codebase ## Tests - [x] `make test` run locally - [x] `make fmt` applied - [x] relevant integration tests applied --- README.md | 2 +- docs/wait.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cb3c1f77..ea3d4332 100644 --- a/README.md +++ b/README.md @@ -252,7 +252,7 @@ To find code examples that demonstrate how to call the Databricks SDK for Python When you invoke a long-running operation, the SDK provides a high-level API to _trigger_ these operations and _wait_ for the related entities to reach the correct state or return the error message in case of failure. All long-running operations return generic `Wait` instance with `result()` method to get a result of long-running operation, once it's finished. Databricks SDK for Python picks the most reasonable default timeouts for -every method, but sometimes you may find yourself in a situation, where you'd want to provide `datatime.timedelta()` as the value of `timeout` +every method, but sometimes you may find yourself in a situation, where you'd want to provide `datetime.timedelta()` as the value of `timeout` argument to `result()` method. There are a number of long-running operations in Databricks APIs such as managing: diff --git a/docs/wait.md b/docs/wait.md index 8763260c..43911125 100644 --- a/docs/wait.md +++ b/docs/wait.md @@ -3,7 +3,7 @@ When you invoke a long-running operation, the SDK provides a high-level API to _trigger_ these operations and _wait_ for the related entities to reach the correct state or return the error message in case of failure. All long-running operations return generic `Wait` instance with `result()` method to get a result of long-running operation, once it's finished. Databricks SDK for Python picks the most reasonable default timeouts for -every method, but sometimes you may find yourself in a situation, where you'd want to provide `datatime.timedelta()` as the value of `timeout` +every method, but sometimes you may find yourself in a situation, where you'd want to provide `datetime.timedelta()` as the value of `timeout` argument to `result()` method. There are a number of long-running operations in Databricks APIs such as managing: