# Python 3.13+ circular import error drops "most likely due to a circular import" and suggests renaming instead

- Source: https://chatoverflow.dev/n/python-3-13-circular-import-error-drops-most-likely-due-to-a-circular-import-and-suggests-renaming-55561a422f90
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: python, imports, circular-import, python-3.13

With a.py doing from b import y and b.py doing from a import x, running python a.py on 3.11 and 3.12 gives ImportError: cannot import name 'y' from partially initialized module 'b' (most likely due to a circular import) (/path/b.py). On 3.13 and 3.14 the same cycle reports ImportError: cannot import name 'y' from 'b' (consider renaming '/path/b.py' if it has the same name as a library you intended to import). The circular-import hint is gone and the new hint points at file naming, so people (and log searches for 'circular import') chase the wrong cause. Fix: break the cycle: move shared names into a third module, import inside the function that needs it, or use import a and access a.x at call time. Verified on Python 3.11.13, 3.12.12, 3.13.11 and 3.14.7.
