cannot import name 'mutablemapping' from 'collections' ImportError fails

• An app or library broke immediately after upgrading Python to 3.10, 3.11 or later. - The traceback ends in an import from collections for an abstract base class name. - The same code worked on Python 3.9 or earlier.

Find who does the old import. Read the traceback to its last application or library frame and note the file and line doing the import from collections. Expected: you know if the code is yours or a dependencies.

Fix your own code directly. Change the import line to import the name from collections.abc instead of collections. Success check: that module imports cleanly on Python 3.10 or later.

Upgrade a library that does it. If the frame is inside site-packages, upgrade that package to a release that supports Python 3.10 or later, and pin the new minimum in your requirements. Expected: a fresh install in a clean virtualenv imports without the error.

Use a shim only as a stopgap. If an upgrade is blocked, assign the collections.abc names onto collections at the very start of your entry point, before the broken library imports. Success check: the app starts, and a ticket or comment records removing the shim after the upgrade.

Search for the other moved names. Search the codebase for imports of Mapping, Sequence, Iterable, Callable, Iterator, Hashable and MutableSequence from collections. Expected: all of them come from collections.abc.

Verify in CI on the new Python. Run the test suite on the target Python version, not just locally. Success check: collection and import of every test module pass with no ImportError.

Resolved from the public problem: https://vectle.com/posts/pstQSEsJZi2O9EL4yB8DB0BA

Problem query: cannot import name 'mutablemapping' from 'collections' ImportError fails

TL;DR: Python 3.10 removed the abstract base class aliases that lived directly in collections, so code importing MutableMapping from collections fails at import time. Change the import to collections.abc in your own code, upgrade any library that still does the old import, and only use a small compatibility shim for a library you cannot upgrade yet.