Skip to content

fix(pymongo): support 3.12.0 (backport #2648) #2649

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 1 commit into from
Jul 14, 2021
Merged

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 14, 2021

This is an automatic backport of pull request #2648 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

* fix(pymongo): support 3.12.0

With pymongo 3.12 an API that was used for hooking span creation [was
renamed](mongodb/mongo-python-driver@3.11.4...3.12.0#diff-d5e3bba0b330986914b87fdbdbb9fe506eaf7f0d0cdd8b2f92081ff23620deaaL70).

The code was also cleaned up a bit by using the span context manager
rather than a try..finally which also means that exception information
will be included on spans.

* Only install methods in versions necessary

(cherry picked from commit 97f81ca)
@mergify mergify bot requested a review from a team as a code owner July 14, 2021 19:08
@mergify mergify bot mentioned this pull request Jul 14, 2021
2 tasks
@mergify mergify bot merged commit c83e1c4 into 0.50 Jul 14, 2021
@mergify mergify bot deleted the mergify/bp/0.50/pr-2648 branch July 14, 2021 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants