How guille-ux/conduitpkg works
Project type and purpose
• This is an open-source Python packaging toolkit (“conduitpkg”) that exposes a CLI, a GUI, and a programmatic API for scaffolding (“builder”), compressing/extracting packages (“packaging”), and installing/searching packages (“install”). It bundles itself into wheel/tar.gz and publishes to PyPI.
File structure
• Top-level: LICENSE, README, docs.
• python-package/: all source, tests, build scripts, distribution artifacts.
• src/conduitpkg/api → core library methods (advanced operations)
• src/conduitpkg/cli → CLI entry-point and parser (cpkg_cli.py, parsertoapi.py)
• src/conduitpkg/gui → GUI frontend
• src/conduitpkg/builder → project scaffolding (new_packet)
• src/conduitpkg/install → package installation/search/dependencies
• src/conduitpkg/packaging → compress/extract modules
• src/conduitpkg/templates → code/license/package templates
• build.sh & dist/ → packaging & distribution artifacts
• tests/ → unit tests
README insights
• Usage: pip install conduitpkg
• Licensing: GPLv3+
Main components & their interactions
a. Interfaces
• CLI (cpkg_cli.py + parsertoapi)
• GUI module
• Programmatic API
b. Core Services
• Builder Service (scaffolding new packages with templates)
• Packaging Service (compress_packet, extract_packet)
• Installation Service (install_pkg, search_packet, dependencies resolution)
c. Templates Repository
• builder_template, gpl_template, package_template
d. Distribution & Publishing
• build.sh → invokes packaging services → produces .whl/.tar.gz in dist/
• External Service: PyPI
e. Tests
• Validate each service independently
Architectural patterns & design principles
• Layered architecture: Interfaces → API orchestration → Core services → Templates → Distribution
• Separation of concerns: CLI/GUI vs. core logic vs. templates vs. packaging vs. install
• Modular, extensible design: each “service” is a self-contained module