Changes in Version 4.2¶Warning Show
PyMongo 4.2 drops support for Python 3.6: Python 3.7+ is now required. PyMongo 4.2 brings a number of improvements including:
Bug fixes¶
Unavoidable breaking changes¶
Changes in Version 4.1.1¶Version 4.1.1 fixes a number of bugs:
Changes in Version 4.1¶Warning PyMongo 4.1 drops support for Python 3.6.0 and 3.6.1, Python 3.6.2+ is now required. PyMongo 4.1 brings a number of improvements including:
Bug fixes¶
Changes in Version 4.0¶Warning PyMongo 4.0 drops support for Python 2.7, 3.4, and 3.5. Warning PyMongo 4.0 drops support for MongoDB 2.6, 3.0, 3.2, and 3.4. Warning PyMongo 4.0 changes the default value of the PyMongo 4.0 brings a number of improvements as well as some backward breaking changes. For example, all APIs deprecated in PyMongo 3.X have been removed. Be sure to read the changes listed below and the PyMongo 4 Migration Guide before upgrading from PyMongo 3.x. Breaking Changes in 4.0¶
Notable improvements¶
Changes in Version 3.12.0¶Warning PyMongo 3.12.0 deprecates support for Python 2.7, 3.4 and 3.5. These Python versions will not be supported by PyMongo 4. Warning PyMongo now allows insertion of documents with keys that include dots (‘.’) or start with dollar signs (‘$’).
Notable improvements¶
Bug fixes¶
Deprecations¶
Changes in Version 3.11.3¶Changes in Version 3.11.2¶Changes in Version 3.11.1¶Version 3.11.1 adds support for Python 3.9 and includes a number of bugfixes. Highlights include:
Changes in Version 3.11.0¶Version 3.11 adds support for MongoDB 4.4 and includes a number of bug fixes. Highlights include:
Deprecations:
Unavoidable breaking changes:
Changes in Version 3.10.0¶Version 3.10 includes a number of improvements and bug fixes. Highlights include:
Changes in Version 3.9.0¶Version 3.9 adds support for MongoDB 4.2. Highlights include:
Unavoidable breaking changes:
Changes in Version 3.8.0¶Warning PyMongo no longer supports Python 2.6. RHEL 6 users should install Python 2.7 or newer from Red Hat Software Collections. CentOS 6 users should install Python 2.7 or newer from SCL Warning PyMongo no longer supports PyPy3 versions older than 3.5. Users must upgrade to PyPy3.5+.
Unavoidable breaking changes:
Changes in Version 3.7.2¶Version 3.7.2 fixes a few issues discovered since the release of 3.7.1.
Changes in Version 3.7.1¶Version 3.7.1 fixes a few issues discovered since the release of 3.7.0.
Changes in Version 3.7.0¶Version 3.7 adds support for MongoDB 4.0. Highlights include:
Deprecations:
Unavoidable breaking changes:
Changes in Version 3.6.1¶Version 3.6.1 fixes bugs reported since the release of 3.6.0:
Changes in Version 3.6.0¶Version 3.6 adds support for MongoDB 3.6, drops support for CPython 3.3 (PyPy3 is still supported), and drops support for MongoDB versions older than 2.6. If connecting to a MongoDB 2.4
server or older, PyMongo now throws a Highlights include:
Deprecations:
Unavoidable breaking changes:
Changes in Version 3.5.1¶Version 3.5.1 fixes bugs reported since the release of 3.5.0:
Changes in Version 3.5¶Version 3.5 implements a number of improvements and bug fixes: Highlights include:
Changes and Deprecations:
Changes in Version 3.4¶Version 3.4 implements the new server features introduced in MongoDB 3.4 and a whole lot more: Highlights include:
Warning Starting in PyMongo 3.4, Note PyMongo 3.4+ attempts to create sockets non-inheritable when possible (i.e. it sets the close-on-exec flag on socket file descriptors). Support is limited to a subset of POSIX operating systems (not including Windows) and the flag usually cannot be set in a single atomic operation. CPython 3.4+ implements PEP 446, creating all file descriptors non-inheritable by default. Users that require this behavior are encouraged to upgrade to CPython 3.4+. Since 3.4rc0, the max staleness option has been renamed from Changes in Version 3.3.1¶Version 3.3.1 fixes a memory leak when decoding elements inside of a
Changes in Version 3.3¶Version 3.3 adds the following major new features:
Warning PyMongo 3.3 drops support for MongoDB versions older than 2.4. It also drops support for python 3.2 (pypy3 continues to be supported). Changes in Version 3.2.2¶Version 3.2.2 fixes a few issues reported since the release of 3.2.1, including a fix for using the connect option in the MongoDB URI and support for setting the batch size for a query to 1 when using MongoDB 3.2+. Changes in Version 3.2.1¶Version 3.2.1 fixes a few issues reported since the release of 3.2, including running the mapreduce command twice when calling the Changes in Version 3.2¶Version 3.2 implements the new server features introduced in MongoDB 3.2. Highlights include:
Changes in Version 3.1.1¶Version 3.1.1 fixes a few issues reported since the release of 3.1, including a regression in error handling for oversize command documents and interrupt handling issues in the C extensions. Changes in Version 3.1¶Version 3.1 implements a few new features and fixes bugs reported since the release of 3.0.3. Highlights include:
Changes in internal classes¶The private Changes in Version 3.0.3¶Version 3.0.3 fixes issues reported since the release of 3.0.2, including a feature breaking bug in the GSSAPI implementation. Changes in Version 3.0.2¶Version 3.0.2 fixes issues reported since the release of 3.0.1, most importantly a bug that could route operations to replica set members that are not in primary or secondary state when using
Changes in Version 3.0.1¶Version 3.0.1 fixes issues reported since the release of 3.0, most importantly a bug in GridFS.delete that could prevent file chunks from actually being deleted. Changes in Version 3.0¶PyMongo 3.0 is a partial rewrite of PyMongo bringing a large number of improvements:
PyMongo 3.0 brings a large number of API changes. Be sure to read the changes listed below before upgrading from PyMongo 2.x. Warning PyMongo no longer supports Python 2.4, 2.5, or 3.1. If you must use PyMongo with these versions of Python the 2.x branch of PyMongo will be minimally supported for some time. SONManipulator changes¶The Thus the SSL/TLS changes¶When ssl is Gevent Support¶In previous versions, PyMongo supported Gevent in two modes: you could call In PyMongo 3.0, the For more information, see PyMongo’s Gevent documentation. MongoClient changes¶
The obsolete classes The
Therefore the In PyMongo 2.x, MongoClient(['host1.com:27017', 'host2.com:27017']) A list of multiple standalones is no longer supported; if multiple servers are listed they must be members of the same replica set, or mongoses in the same sharded cluster. The behavior for a list of mongoses is changed from “high availability” to “load balancing”. Before, the client connected to the lowest-latency mongos in the list, and used it until a network error prompted it to re-evaluate all mongoses’ latencies and reconnect to one of them. In PyMongo 3, the client monitors its network latency to all the mongoses continuously, and distributes operations evenly among those with the lowest latency. See mongos Load Balancing for more information. The client methods Support for the The
The The The The The
The following read-only attributes have been added:
The following attributes are now read-only:
The following attributes have been removed:
The following attributes have been renamed:
Cursor management changes¶
The second parameter to Database changes¶The The following read-only attributes have been added:
The following attributes are now read-only:
Use
The following attributes have been removed:
The following methods have been added:
The following methods have been changed:
The following methods have been deprecated:
The following methods have been removed: The Collection changes¶The following read-only attributes have been added:
The following attributes are now read-only:
Use The following attributes have been removed:
The following methods have been added:
The following methods have changed:
The following methods are deprecated:
The following methods have been removed: The Changes to |