https://alwaldend.com/docs/infra/src/openspec/specs/python-import-validation/ Recent content in Python import validation on Alwaldend Hugo en https://alwaldend.com/docs/infra/src/openspec/specs/python-import-validation/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://alwaldend.com/docs/infra/src/openspec/specs/python-import-validation/spec/ <span id="python-import-validation-specification"></span><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Enforce module namespace imports in tracked first-party Python source through repository quality.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-validate-namespaced-python-imports">Requirement: Validate namespaced Python imports<a class="td-heading-self-link" href="#requirement-validate-namespaced-python-imports" aria-label="Heading self-link"></a></h3><p>The repository quality suite SHALL reject individual symbol imports in tracked first-party Python source using the existing pinned syntax linter, except direct public re-exports listed in explicit <code>__all__</code> in <code>__init__.py</code>. Wildcard imports SHALL remain forbidden. Module imports and qualified member access SHALL be accepted, including importing a verified module with <code>from package.path import module</code>. Long module paths SHALL use this form. Downloaded external source SHALL remain outside this first-party check. The Python skill SHALL describe the convention and its owning validation target.</p>