Python: Why are circular imports bad?

Asked 2 years ago

I've heard that circular imports are generally considered bad in Python. Can someone explain why this is the case?

Python Adding dependencies Dependency conflicts Debugging

Roberto Ray

Wednesday, July 06, 2022

Circular imports are bad because they can lead to unexpected behavior and errors. When two modules are imported, the interpreter will execute the code in both modules. If the modules have variables or functions with the same name, the value of the variable or function in the second module will overwrite the value in the first module. This can lead to unexpected results.

Write an answer...﻿

Cancel

Please follow our Community Guidelines

Python: Why are circular imports bad?

Related Posts

Should I replace the broken /.pub-cache package with something else?

How to deal with transitive dependencies conflicts?

What are the differences between distribute, distutils, setuptools, and distutils2?

Trying to install with Anaconda package manager but it keeps telling me that it's not found. How do I make it 'find' the needed packages?

How do I get AWS SAM CLI to stop ignoring my Python dependencies during the deployment process?

How to avoid circular dependencies in python?

How do I add a module as a dependency in my POM file?

How can I enforce continuous integration checks to verify compatibility between Python and Node.js components in my project?

How do we bundle python dependencies so that it doesn't need to be downloaded when used by others?

How do I download a package from public repo to conda?

Can't find what you're looking for?