importscan: recursively import Python packages
importscan provides a scan function that lets you recursively import a package and its sub-modules and sub-packages.
CHANGES
1.0.0 (2026-10-10)
Skip importing packages in scan() since they’re already imported in walk_packages().
Add type annotations and integrate mypy and pyright.
Switch to pyproject.toml based project setup.
Add support for Python 3.11 - 3.15.
Drop support for Python 3.10 and below.
Support Pypy 3.12.
Fix linting errors.
Use GitHub Actions for CI.
Add tests for 100% coverage.
Update docs and adjust sphinx config.
Make an overall cleanup.
Fix readthedocs integration.
Replace flake8, black, isort, pyupgrade and pre-commit with Ruff.
Add a tracked Git pre-commit hook for Ruff checks on staged Python files.
Remove coveralls integration.
Adjust the deployment strategy:
Move the Pypi upload from zest.release to gh-actions.
Use v + version as release tags like v1.0.0.
So we still use zest.release but without publishing to Pypi. The Pypi upload is triggered by pushing the new release tag to GitHub. This happens in the Release workflow in .github/workflows/release.yml. With this workflow we get Trusted Publishing with short-lived OIDC tokens that PyPI issues to one specific repository, workflow file and environment (pypi). We also get PEP 740 provenance and can set required reviewers for the environment and a ruleset who can create release tags and trigger releases.
0.2 (2020-01-29)
Removed: Removed support for Python 2.
You have to upgrade to Python 3 if you want to use this version.
Dropped support for Python 3.3
Added support for Python 3.5, 3.6, 3.7, 3.8 and PyPy 3.6.
Make Python 3.7 the default testing environment.
Fix deprecated and legacy code.
Use virtualenv and pip instead of buildout to set up the development environment.
Add development documentation and reorganize documentation.
Upload universal wheels to pypi during release.
Clean up the development and release workflow.
Add integration for the Black code formatter.
0.1 (2016-03-15)
Initial public release.
Release files for importscan 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| importscan-1.0.0.tar.gz | 24.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| importscan-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.2 kB
Release files / importscan-1.0.0.tar.gz
| Download URL | importscan-1.0.0.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb346742fd225bce326f2d1c0dc97d7ed0a9904175c8958b32f7ef48dd774252
|
|
BLAKE2b-256 checksum How to use checksums |
dd69483d465d9b02c7d49015b4fe20fa5f5e7f36fd1ba935aa396e689aa5982a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / importscan-1.0.0-py3-none-any.whl
| Download URL | importscan-1.0.0-py3-none-any.whl |
|---|---|
| Size | 29.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1261751fb6afecae32d7ed2bb6a47cad31928230b0efef9e0a3f72b6fdab6fa
|
|
BLAKE2b-256 checksum How to use checksums |
110a738f1757f9f5161f80e8cede8ea0fc604f59dd28754d38df1aa9b2c5336a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log
