summaryrefslogtreecommitdiff
path: root/.github
diff options
context:
space:
mode:
authorTom Scogland <scogland1@llnl.gov>2022-11-07 15:00:22 -0800
committerGitHub <noreply@github.com>2022-11-07 15:00:22 -0800
commit6241cdb27be0ed81a517f1601feac1b7e327170c (patch)
tree68caab8eb5992a218f0e276619ae3b70c153e086 /.github
parent28d669cb39b155e73fea532ea4d8100a921041b0 (diff)
downloadspack-6241cdb27be0ed81a517f1601feac1b7e327170c.tar.gz
spack-6241cdb27be0ed81a517f1601feac1b7e327170c.tar.bz2
spack-6241cdb27be0ed81a517f1601feac1b7e327170c.tar.xz
spack-6241cdb27be0ed81a517f1601feac1b7e327170c.zip
encode development requirements in pyproject.toml (#32616)
Add a `project` block to the toml config along with development and CI dependencies and a minimal `build-system` block, doing basically nothing, so that spack can be bootstrapped to a full development environment with: ```shell $ hatch -e dev shell ``` or for a minimal environment without hatch: ```shell $ python3 -m venv venv $ source venv/bin/activate $ python3 -m pip install --upgrade pip $ python3 -m pip install -e '.[dev]' ``` This means we can re-use the requirements list throughout the workflow yaml files and otherwise maintain this list in *one place* rather than several disparate ones. We may be stuck with a couple more temporarily to continue supporting python2.7, but aside from that it's less places to get out of sync and a couple new bootstrap options. Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions