Skip to content

Make backwards compatible with urllib3~=1.0 #197

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

Merged
merged 2 commits into from
Aug 16, 2023
Merged

Conversation

susodapop
Copy link
Contributor

This is required to support dbt-databricks because dbt-core is pinned to urllib3~=1.0

Signed-off-by: Jesse Whitehouse <[email protected]>
@susodapop susodapop changed the title Make backwards compatible with urllib3 Make backwards compatible with urllib3==1.0 Aug 15, 2023
Signed-off-by: Jesse Whitehouse <[email protected]>
@susodapop susodapop changed the title Make backwards compatible with urllib3==1.0 Make backwards compatible with urllib3~=1.0 Aug 15, 2023
@susodapop
Copy link
Contributor Author

I tested this manually in an environment with urllib==1.26.16 installed. All e2e and unit tests pass. I am also pushing 2.9.2dev1 to pypi so we can make sure this will work with dbt-databricks as well.

@susodapop
Copy link
Contributor Author

I've manually run the integration tests for dbt-databricks using the dev version I deployed yesterday. Everything works. This PR should be good to merge. Then we'll release version 2.9.2 of pysql and cut a new release of dbt-databricks that bumps the pysql dependency to 2.9.2.

@susodapop susodapop merged commit d28a692 into main Aug 16, 2023
@susodapop susodapop deleted the change-urllib-spec branch August 16, 2023 19:02
susodapop pushed a commit that referenced this pull request Aug 24, 2023
* Make retry policy backwards compatible with urllib3~=1.0.0

We already implement the equivalent of backoff_max so the behaviour will
be the same for urllib3==1.x and urllib3==2.x

We do not implement backoff jitter so the behaviour for urllib3==1.x will
NOT include backoff jitter whereas urllib3==2.x WILL include jitter.

---------

Signed-off-by: Jesse Whitehouse <[email protected]>
susodapop pushed a commit to unj1m/databricks-sql-python that referenced this pull request Sep 19, 2023
susodapop pushed a commit to unj1m/databricks-sql-python that referenced this pull request Sep 19, 2023
databricks#206)

* Make retry policy backwards compatible with urllib3~=1.0.0

We already implement the equivalent of backoff_max so the behaviour will
be the same for urllib3==1.x and urllib3==2.x

We do not implement backoff jitter so the behaviour for urllib3==1.x will
NOT include backoff jitter whereas urllib3==2.x WILL include jitter.

---------

Signed-off-by: Jesse Whitehouse <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants