v4.13 Release #266
Merged
v4.13 Release #266
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-pymongo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
NoahStapp
suggested changes
May 14, 2025
source/reference/migration.txt
Outdated
|
|
||
| * - ``TestFindManyAndEmptyCursor`` | ||
| - 74.074 MB/s | ||
| - 112.490 MB/s |
There was a problem hiding this comment.
Suggested change
| - 112.490 MB/s | |
| - 112.490 MB/s |
| Performance Benchmarks | ||
| ~~~~~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| The following table shows the performance benchmarks for different tasks |
There was a problem hiding this comment.
A short blurb to explain that in almost every case, the new asynchronous API performs better seems helpful here.
There was a problem hiding this comment.
+1 I was just going to add a comment for the same thing
source/reference/migration.txt
Outdated
|
|
||
| .. warning:: | ||
|
|
||
| The {+driver-async+} driver does not support Tornado. | ||
| The {+driver-async+} API does not support Tornado. |
There was a problem hiding this comment.
My mistake on this earlier: the new API does support Tornado, as Tornado was made fully compatible in a release some time ago.
source/reference/migration.txt
Outdated
| - ``AsyncCursor.each()`` does not exist in the {+driver-async+} driver. | ||
| - ``MotorGridOut.stream_to_handler()`` does not exist in the {+driver-async+} driver. | ||
| - ``AsyncCursor.to_list(0)`` is not valid in the {+driver-async+} driver. Use | ||
| - ``AsyncCursor.each()`` does not exist in the {+driver-async+} api-root. |
There was a problem hiding this comment.
Suggested change
| - ``AsyncCursor.each()`` does not exist in the {+driver-async+} api-root. | |
| - ``AsyncCursor.each()`` does not exist in the {+driver-async+} API. |
NoahStapp
approved these changes
May 14, 2025
R-shubham
reviewed
May 14, 2025
| Performance Benchmarks | ||
| ~~~~~~~~~~~~~~~~~~~~~~ | ||
|
|
||
| The following table shows the performance benchmarks for different tasks |
There was a problem hiding this comment.
+1 I was just going to add a comment for the same thing
source/reference/migration.txt
Outdated
|
|
||
| The {+driver-async+} driver functions similarly to the Motor library, but allows | ||
| The {+driver-async+} API functions similarly to the Motor library, but allows | ||
| for improved latency and throughput due to directly using Python Asyncio instead |
R-shubham
approved these changes
May 14, 2025
rachel-mack
approved these changes
May 14, 2025
source/reference/migration.txt
Outdated
|
|
||
| The {+driver-async+} API is designed to be a replacement for the Motor | ||
| library. Motor was created to provide support for Tornado, with asyncio support | ||
| added later. Because of this, Motor provides full asyncio and Tornado support, |
There was a problem hiding this comment.
For all mentions:
Suggested change
| added later. Because of this, Motor provides full asyncio and Tornado support, | |
| added later. Because of this, Motor provides full ``asyncio`` and Tornado support, |
source/reference/migration.txt
Outdated
| but still relies on a thread pool to perform network operations. In some cases, | ||
| this might lead to performance degradation when using the Motor library. To | ||
| address this issue, the {+driver-async+} API implements asyncio support directly | ||
| into {+driver-short+}. |
There was a problem hiding this comment.
Re: the comments below. I would mention in this intro paragraph that PyMongo Async has better performance in most cases, then link to the performance section.
source/reference/migration.txt
Outdated
Comment on lines
190
to
191
| {+driver-async+} API. We strongly recommend that Motor users migrate to | ||
| the {+driver-async+} API while Motor is still supported. |
source/reference/release-notes.txt
Outdated
Comment on lines
49
to
50
| - The {+driver-async+} API is generally available. To learn how to migrate | ||
| to the {+driver-async+} API, see the :ref:`pymongo-async-migration` guide. |
There was a problem hiding this comment.
Suggested change
| - The {+driver-async+} API is generally available. To learn how to migrate | |
| to the {+driver-async+} API, see the :ref:`pymongo-async-migration` guide. | |
| - The {+driver-async+} API is generally available. To learn how to migrate | |
| to the {+driver-async+} API from the {+driver-short+} driver or the Motor library, see the :ref:`pymongo-async-migration` guide. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Info
PR Reviewing Guidelines
JIRA -
Staging Links
Self-Review Checklist