Compatibility Policy

Semantic Versioning

PyMongo’s version numbers follow semantic versioning: each version number is structured “major.minor.patch”. Patch releases fix bugs, minor releases add features (and may fix bugs), and major releases include API changes that break backwards compatibility (and may add features and fix bugs).


Before we remove a feature in a major release, PyMongo’s maintainers make an effort to release at least one minor version that deprecates it. We add “DEPRECATED” to the feature’s documentation, and update the code to raise a DeprecationWarning. You can ensure your code is future-proof by running your code with the latest PyMongo release and looking for DeprecationWarnings.

Starting with Python 2.7, the interpreter silences DeprecationWarnings by default. For example, the following code uses the deprecated slave_okay option but does not raise any warning:

# ""
from pymongo import MongoClient

client = MongoClient(slave_okay=True)

To print deprecation warnings to stderr, run python with “-Wd”:

$ python -Wd DeprecationWarning: slave_okay is deprecated. Please use read_preference instead.
  client = MongoClient(slave_okay=True)

You can turn warnings into exceptions with “python -We”:

$ python -We
Traceback (most recent call last):
  File "", line 4, in <module>
    client = MongoClient(slave_okay=True)
  File "/Users/emptysquare/.virtualenvs/official/mongo-python-driver/pymongo/", line 373, in __init__
DeprecationWarning: slave_okay is deprecated. Please use read_preference instead.

If your own code’s test suite passes with “python -We” then it uses no deprecated PyMongo features.

See also

The Python documentation on the warnings module, and the -W command line option.

Table Of Contents

Previous topic

Frequently Asked Questions

Next topic

API Documentation

This Page