New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize packaging #111
Reorganize packaging #111
Conversation
@matthewhanson (and anyone else reviewing), if you can take and extra look at https://github.com/stac-utils/stactools/pull/111/files#diff-2e3c7d1bc0706a094cc1cac241569dd21973b559d51dd45b0640ef1ee7600e29 during the review, this is some of the tomfoolery I had to do to get the test path stuff working. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't get to in depth into the scripts folder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've run across some problems while porting the aster subpackage.
Most of the tests are working, but one of them requires a custom build GDAL. I've got some ideas about how we can structure the Docker images. We can discuss it tomorrow.
- Removes all subpackages other than `core` and `cli` - Moves code into a more traditional package namespace structure in `src` - Switches to a static `setup.cfg` file - Adds more CI, including actually testing the Python matrix - Updates .gitignore - Updates README
This allows packages to use test utils without having to copy the code directly.
This pull request is a major edit of the stactools packaging story. By splitting off packages into their own repositories, we:
stactools.core
.Overview
stactools_browse
. These packages are being moved to their own repositories in thestactools-packages
organization.environment.yml
file and instructions on runningstactools
with conda.stactools.testing
module with some testing helper functions to be used by other stactools packages.Other effects
git clone https://github.com/stac-utils/stactools && cd stactools && pip install -e .
now works.click
is now a direct dependency ofstactools
. Because every dataset subpackage hadclick
as a dependency, it seemed like the use-case for aclick
-less install (just using thestactools.core
API without any CLI or dataset subpackages) was vanishingly small.src/stactools
, which is the recommended way to do same-repo namespace packages.Path forward
Once this PR is reviewed and approved, I hope to merge it then cut a v0.2.0-alpha.0 release. This release can then be used by packages to get their CI passing.