How adacore/e3-core works
Project type and purpose
• This is an open-source Python framework (“e3-core”) designed to ease the development of portable automated build systems.
• It’s a library (namespace package e3) exposing multiple subsystems (e.g. anod, archive, net, os, store, event, etc.) rather than a single monolithic application or microservices setup.
File structure
• Top-level:
• src/e3/… contains the core code, organized by feature subpackages
• docs/ holds Sphinx documentation
• tests/ holds pytest test suites mirroring each feature
• CI configs (.github/workflows/ci.yaml, tox.ini) and packaging files (pyproject.toml, setup.cfg)
• Major subpackages under src/e3—each is a component:
• anod (dependency resolution, packaging, .anod specs)
• archive (tar/zip I/O)
• collection (data structures, e.g. DAG)
• cve (calls NVD API)
• diff, decorator, fingerprint, fs, hash, log, yaml, etc.
• net (http downloads, smtp)
• os (cross-platform OS abstractions: fs, process, timezone, Windows native APIs)
• platform & platform_db (platform metadata knowledge base)
• store (resource download & local caching backends)
• event (pluggable event handlers: file, logging, s3, smtp)
• electrolyt (build-plan parsing and execution)
• main (CLI entrypoint, command-line parsing)
• Configuration files for build & test automation (.pre-commit, CI, ReadTheDocs).
README for additional insights
• Confirms the modular breakdown above
• Mentions how each subpackage contributes to the overall framework