Open cmelone opened 1 month ago
We define constants in code that are technically preferences of the authors, they should be decoupled to allow for customization.
example: https://github.com/spack/spack-gantry/blob/efd78caa73a8001a8af29cfcb71a694dd0640d3b/gantry/routes/prediction/prediction.py#L10-L22
Nothing fancy, maybe an optional config.py under gantry/.
config.py
gantry/
Problem/Opportunity Statement
We define constants in code that are technically preferences of the authors, they should be decoupled to allow for customization.
example: https://github.com/spack/spack-gantry/blob/efd78caa73a8001a8af29cfcb71a694dd0640d3b/gantry/routes/prediction/prediction.py#L10-L22
What would success / a fix look like?
Nothing fancy, maybe an optional
config.py
undergantry/
.