project-import-conventions

To fix circular imports and module-resolution errors, enforce standardized root-to-submodule import paths and consistent test-mocking conventions. This prevents ambiguity between namespace prefixes and ensures reliable module discovery across the codebase.

The best way to structure pytest mocks is applying standardized import patterns for tests and scripts. This avoids ambiguity between namespace prefixes and provides clear rules for test structure to improve reliability and discovery.

To configure relative imports within src/app without triggering circular dependencies, apply clear rules for within-module references and use explicit root-to-submodule import paths. This standardizes cross-module references and prevents resolution failures.

Yes, the convention supports project expansion by enumerating recommended locations for scripts, references, and assets. It requires explicit frontmatter name and description to maintain consistent import paths as new modules are added.

Python tests fail with namespace prefix ambiguity when import paths lack standardization across the codebase. Enforcing root-to-submodule import conventions and clear test-mocking guidelines resolves this ambiguity and prevents module-resolution errors.