How to Fix ‘cannot import name multihostdsn from pydantic.networks’

When working with Python applications using the Pydantic library, you may encounter the following import error:

cannot import name 'multihostdsn' from 'pydantic.networks' 

This occurs when there is a version mismatch between Pydantic and one of its dependencies.

In this comprehensive guide, I’ll explain the cause of this import error and guide you through multiple solutions to fix it in Pydantic.

Let’s start by getting an overview of Pydantic and why this error occurs.

What is Pydantic?

Pydantic is a popular Python library for data validation and settings management using Python type hints.

Some of its key features include:

  • Data parsing and validation using pydantic.BaseModel
  • Type-based config management with pydantic.BaseSettings
  • ORM-like data modeling capabilities
  • Integration with other frameworks like FastAPI

Internally, Pydantic depends on several other packages like:

Version conflicts between Pydantic and its dependencies can cause certain modules to become unavailable, resulting in errors like the multihostdsn ImportError.

Origins of the ImportError

The cannot import name 'multihostdsn' from 'pydantic.networks' error indicates that the pydantic.networks module is not available.

This module was introduced in Pydantic version 1.9. It provides functions for validating network addresses, hostnames, and DSN formats.

The multihostdsn() function specifically validates multi-host database DSN strings.

When this module is missing entirely, it typically means:

  1. You have an outdated version of Pydantic that does not include pydantic.networks at all. Upgrading Pydantic should resolve it.
  2. There is a dependency conflict between Pydantic and one of its dependencies, which breaks certain submodules. Resolving this conflict is needed.

Let’s go over some commands to check the installed versions and narrow down the cause.

Checking Installed Versions

First, check your currently installed versions of Pydantic and related packages:

# Check Pydantic version
python -m pydantic --version

# List installed packages
pip freeze | grep -e pydantic -e typer -e validator

This will display the exact versions that are installed for:

  • Pydantic
  • Typer
  • EmailValidator
  • validators

Based on the versions reported, you can determine if a Pydantic upgrade is needed or if a mismatch between packages exists.

Now let’s go through different solutions to address the multihostdsn error based on the installed versions.


There are a few potential solutions depending on the installed Pydantic version:

Upgrade Pydantic

If you have Pydantic 1.8.2 or earlier installed, the pydantic.networks module does not exist at all.

Upgrading to the latest Pydantic version will provide the missing module:

pip install -U pydantic

This will install Pydantic 1.9.0 or later, resolving the ImportError.

Downgrade Typer

If you have the latest Pydantic but a mismatch with Typer, downgrading Typer may help:

pip install typer==0.4.0

Typer 0.5.0 introduced breaking changes causing submodule conflicts. Downgrading provides compatibility with the Pydantic version.

Reinstall Packages

Sometimes dependency conflicts can be fixed by reinstalling packages:

# Uninstall Pydantic and Typer
pip uninstall pydantic typer

# Reinstall packages
pip install pydantic typer

This refreshes the installations to play well together.

Use Virtual Environments

Isolating Pydantic and its dependencies in a virtual environment can prevent conflicts:

# Create virtual environment 
python -m venv env

# Activate environment
source env/bin/activate

# Install packages in environment
pip install pydantic typer

The virtual environment contains compatible versions so import multihostdsn will work.

In most cases, either upgrading Pydantic or downgrading Typer should resolve the issue. But let’s look at some other solutions as well.

Importing from pydantic.dataclasses

Recent versions of Pydantic introduced a new pydantic.dataclasses module with alternatives to certain networks functions.

As a workaround, you may be able to import the required validation functions from dataclasses instead.

For example:

from pydantic.dataclasses import dataclass_url

Unfortunately this does not provide an alternative to multihostdsn(). But for other attributes like URLs and emails, the dataclasses module can help avoid version conflicts.

Managing Requirements Files

Requirements files like requirements.txt pin specific package versions for reproducibility.

Best practices recommend managing dependencies in requirements files and virtual environments.

For example, a requirements.txt file might contain:

# etc

This prevents unexpected version changes leading to issues like missing submodules.

After troubleshooting the multihostdsn error, be sure to update the requirements file accordingly.

Pinning Versions

In general when using Pydantic it is best practice to install a specific version like:


Pinning the major AND minor version prevents unintended upgrades that could break dependencies.

Apply this principle to all packages in requirements files.

Pydantic Changelog

When managing Pydantic dependencies, consult the Pydantic changelog to view dependency changes in each release.

For example, the 1.9 changelog highlights:

  • Added new pydantic.networks module
  • Typer upgrade compatibility issues

This helps anticipate and prevent version conflicts as new releases occur.

Additional Troubleshooting

Some additional tips for troubleshooting the multihostdsn error:

  • Try commenting out the line causing the ImportError to isolate the problem
  • Search Pydantic issues on Github/StackOverflow to see if others have reported similar problems
  • Try replicating the error in a fresh virtual environment with only pydantic and typer installed
  • If upgrading/downgrading doesn’t work, try reinstalling the packages
  • As a last resort, uninstall all packages and reinstall from scratch

Thoroughly investigating dependency versions and replicating the bare minimum environment is key to resolving module import issues.

Preventing Dependency Issues

Here are some best practices for preventing dependency conflicts:

  • Always pin full version numbers like 1.9.1 in requirements files
  • Isolate dependencies in virtual environments
  • Only upgrade one package at a time, checking for breakages
  • Periodically run pip list --outdated to review packages needing upgrade
  • When upgrading, consult changelog notes for dependency changes

Carefully managing dependencies avoids tricky version conflicts and import errors down the road.


This guide covered a variety of solutions to fix the “cannot import name ‘multihostdsn’ from ‘pydantic.networks'” error, including:

  • Upgrading Pydantic to the latest version
  • Downgrading Typer to 0.4.0
  • Reinstalling packages to refresh installations
  • Using virtual environments for isolation
  • Modifying code to import from pydantic.dataclasses
  • Enforcing pinned versions in requirements files

While the exact cause can vary, the ultimate fix involves resolving the dependency mismatch between Pydantic and associated packages like Typer.

Carefully managing virtual environments, requirements files, and incremental upgrades is the best way to prevent Pydantic dependency issues.

Hopefully this provides a thorough guide to debugging and fixing the confusing multihostdsn ImportError in Pydantic. Let me know if you have any other suggestions to cover!

Leave a Comment