summaryrefslogtreecommitdiff
path: root/SECURITY.md
diff options
context:
space:
mode:
authorTodd Gamblin <gamblin2@llnl.gov>2022-05-23 23:33:43 -0400
committerGitHub <noreply@github.com>2022-05-24 03:33:43 +0000
commit306bed48d747c907cfbd60073cdf6d92c3bca14a (patch)
tree3e06e6dd1eb4c8b34a8ddbf47128683784e8d3e9 /SECURITY.md
parent63402c512b4d660e987dae6ad82f6ab7eac8a766 (diff)
downloadspack-306bed48d747c907cfbd60073cdf6d92c3bca14a.tar.gz
spack-306bed48d747c907cfbd60073cdf6d92c3bca14a.tar.bz2
spack-306bed48d747c907cfbd60073cdf6d92c3bca14a.tar.xz
spack-306bed48d747c907cfbd60073cdf6d92c3bca14a.zip
specs: emit better parsing errors for specs. (#24860)
Parse error information is kept for specs, but it doesn't seem like we propagate it to the user when we encounter an error. This fixes that. e.g., for this error in a package: ```python depends_on("python@:3.8", when="0.900:") ``` Before, with no context and no clue that it's even from a particular spec: ``` ==> Error: Unexpected token: ':' ``` With this PR: ``` ==> Error: Unexpected token: ':' Encountered when parsing spec: 0.900: ^ ```
Diffstat (limited to 'SECURITY.md')
0 files changed, 0 insertions, 0 deletions