Add naive list of package dependencies to pyproject.toml#123
Add naive list of package dependencies to pyproject.toml#123kemccusker merged 7 commits intomainfrom
Conversation
|
Feel free to merge this if it reviews good. I'm not sure if we know enough to move some of these to an optional dependency section. Happy to do that here if reviewers think we can do that and can give me some direction. |
Codecov Report
@@ Coverage Diff @@
## main #123 +/- ##
=======================================
Coverage 65.27% 65.27%
=======================================
Files 17 17
Lines 1846 1846
=======================================
Hits 1205 1205
Misses 641 641 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
brews
left a comment
There was a problem hiding this comment.
Collapse dask requirements
kemccusker
left a comment
There was a problem hiding this comment.
This makes sense and looks good to me. There might be the opportunity for optional deps, especially if dscim is only used for running from damage function coefs, rather than from the spatial damage inputs. This should be a later PR.
This PR adds a list of package dependencies so people have an idea of what's required to run things.
Basically, this takes the packages in requirement.txt and puts them into pyproject.toml, without version pins.
I have a feeling that some of these are not really hard required dependencies. Some might be optional, so we might want to tweak these a bit and make some optional dependencies or "features". Like a "viz" section that installs stuff required to do graphics and plots -- then we can make those packages optional. "io" might be another good one because it looks like there are a couple heavy packages for reading and writing different file formats and I'm not sure if these are always required. Anyways, that might be a task for another PR.
Close #102