Hi,
I've been actively using Satclip and recently refactored it into a modern Python package here: Haight3/satclip. I wanted to ask whether you'd be interested in adopting this structure upstream or as an optional branch.
Here’s what was changed:
Key Modernization Features:
-
PEP 621-compliant pyproject.toml (removes the need for setup.py/setup.cfg)
-
src/ layout to improve import hygiene and avoid namespace clashes
-
Explicit versioning support baked into the build process
-
All imports cleaned and made absolute for clarity
-
Add Documentation to most of the functions and modules.
Benefits:
-
Easier integration with tools like pipx, build, tox, pytest, and ruff
-
Simplifies distribution via PyPI or internal registries
-
Much easier for downstream users to consume and extend
-
Plays well with IDEs and type checkers (VSCode, PyCharm, mypy)
-
Helps modularize and test parts like location_encoder, wrap, etc.
Happy to open a PR or break this into smaller parts if you think it’s of interest!
Hi,
I've been actively using Satclip and recently refactored it into a modern Python package here: Haight3/satclip. I wanted to ask whether you'd be interested in adopting this structure upstream or as an optional branch.
Here’s what was changed:
Key Modernization Features:
PEP 621-compliant pyproject.toml (removes the need for setup.py/setup.cfg)
src/ layout to improve import hygiene and avoid namespace clashes
Explicit versioning support baked into the build process
All imports cleaned and made absolute for clarity
Add Documentation to most of the functions and modules.
Benefits:
Easier integration with tools like pipx, build, tox, pytest, and ruff
Simplifies distribution via PyPI or internal registries
Much easier for downstream users to consume and extend
Plays well with IDEs and type checkers (VSCode, PyCharm, mypy)
Helps modularize and test parts like location_encoder, wrap, etc.
Happy to open a PR or break this into smaller parts if you think it’s of interest!