Vendor dependencies

Ship Python libraries without dependency fear.

Run plugins and frameworks with their own dependencies — safely, inside one Python process.

framework/main.py

import pydantic
# → resolves vendor/pydantic [2.13.3]

print(pydantic.__version__)
# → '2.13.3' ✓ vendored

user/hook.py

import pydantic
# → resolves site-packages/pydantic [1.10.26]
 
print(pydantic.__version__)
# → '1.10.26' ✓ global

You’re building a plugin system

Your application loads third-party plugins in the process.

Each plugin is developed independently, with its own dependencies and versions. Any dependency conflicts between plugins can cause crashes and unexpected behavior.

Without isolation, one plugin’s dependencies can break another — or the host itself.

You run user code inside a framework

Your framework executes user-provided Python code.

Framework internals need strict dependency versions, but user code may require different versions. Any dependency mismatches break the entire application.

Mixing both leads to dependency conflicts and runtime errors.

Works the way you expect.

Everything you need for dependency isolation. Simple and powerful.

Package-Scoped Isolation

Dependencies are isolated only within your package, not across the entire Python process.

Native Import System

Built directly on Python’s import system. No source rewriting, no import renaming.

Multiple Versions, One Interpreter

Run different versions of the same dependency side by side.

Ready to end the dependency hell?

PyIsolate is open source and ready for production. Start isolating your dependencies in minutes.

Read the documentation