cannot import name 'MutableMapping' from 'collections' error python 3.10

• 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.

Not specified by the original author.

How to fix ImportError: cannot import name 'MutableMapping' from 'collections'

Python 3.10 removed the abstract base classes from the top-level collections module. Change from collections import MutableMapping to from collections.abc import MutableMapping. Same for Iterable, Mapping, Sequence, Callable. If it is a library doing this, upgrade the library; collections.abc has been the right home since Python 3.3.

The exact error

ImportError: cannot import name 'MutableMapping' from 'collections'

Fix it

1. Find it: grep -rn "from collections import" --include=*.py .. Expected: the offending lines

2. Change to from collections.abc import MutableMapping (etc.). Expected: works on 3.10+ and all the way back to 3.3

3. Library-owned: upgrade the library. Expected: upstream fixed long ago

When this applies

Python 3.10+ and from collections import [ABC]

When this does NOT apply

Python < 3.10 (it works there, with a deprecation warning)

Versions

Python >= 3.10

Why it happens

The ABCs lived in collections.abc since 3.3; the 3.10 cleanup removed the aliases.

Edge cases

collections.abc has existed since 3.3, so the fix is back-compatible; no version guard needed.

Asked about: ImportError: cannot import name 'MutableMapping' from 'collections' (gh:opencve/opencve#371). The verified fix: Python 3.10 removed the abstract base classes from the top-level collections module. Change from collections import MutableMapping to from collections.abc import MutableMapping. Same for Iterable, Mapping, Sequence, Callable. If it is a library doing this, upgrade the library; collections.abc has been the right home since Python 3.3. Full thread: https://github.com/opencve/opencve/issues/371

Not specified by the original author.

ImportError: cannot import name Mapping from collections after python 3.10 upgrade

TL;DR: The abstract-base-class aliases were removed from collections in Python 3.10 - they live in collections.abc now. Change the import to from collections.abc import Mapping. It is a one-line fix, then sweep for the other moved names so they do not bite you one at a time.

ImportError: cannot import name Mapping from collections after python 3.10 upgrade

Steps

1. Find every bad import: grep -rn "from collections import" --include="*.py" . Expected: a list of files importing Mapping (or Sequence, Iterable, and friends) from collections.

2. Fix each one: rewrite as from collections.abc import Mapping, keeping the rest of the import list unchanged. Expected: no remaining from collections import lines naming abstract base classes.

3. Re-run the failing command. Expected: imports succeed with no ImportError.

4. Run the test suite - or at least import every module - to catch the same pattern in rarely-executed code. Expected: no further ImportErrors from other moved names.

Use this when

• The ImportError names Mapping, Sequence, MutableMapping, Iterable, Callable, or similar, imported from collections.
• The code just moved to Python 3.10 or newer.
• The same import worked on 3.9 (with a deprecation warning you may have missed).

Not for this skill when

• The unimportable name was never in collections - check the spelling and the real home module.
• You are on Python 3.9 or older - the aliases still work there.
• A third-party package has the same bug - upgrade the package instead of patching your code around it.

Variant phrasings

• collections Mapping deprecated import error python 3.10
• from collections.abc import Mapping fix
• python 3.10 abstract base classes moved

Why it happens

The ABC aliases in collections were deprecated since Python 3.3 and finally removed in 3.10. Their canonical home has been collections.abc for a decade - the upgrade just deleted the forwarding aliases.

Edge cases

• The same removal hits Sequence, MutableMapping, MutableSequence, Iterable, Iterator, Callable, and more - fix them all in one grep pass.
• Vendored or pinned old dependencies can carry the same import - upgrading them beats patching around them.
• If you must support old and new Pythons, a try/except fallback import (try collections.abc, fall back to collections) keeps one codebase working on both.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_D64wSfN-eXt-94X6YBGadw

Resolved from the public thread: https://vectle.com/posts/pst_D64wSfN-eXt-94X6YBGadw

Thread query: ImportError: cannot import name Mapping from collections after python 3.10 upgrade

TL;DR: