diff options
| author | Veselin Dobrev <v-dobrev@users.noreply.github.com> | 2018-02-28 14:25:29 -0800 |
|---|---|---|
| committer | Christoph Junghans <christoph.junghans@gmail.com> | 2018-02-28 15:25:29 -0700 |
| commit | d3ed46e9585f17c6eef3b3b38344d7492cc92f8e (patch) | |
| tree | b7c91723c8d39df815115c1ae5566d919801b2e5 /var | |
| parent | 98949bd79b18d1cd33e67314a893e46a2beb4958 (diff) | |
| download | spack-d3ed46e9585f17c6eef3b3b38344d7492cc92f8e.tar.gz spack-d3ed46e9585f17c6eef3b3b38344d7492cc92f8e.tar.bz2 spack-d3ed46e9585f17c6eef3b3b38344d7492cc92f8e.tar.xz spack-d3ed46e9585f17c6eef3b3b38344d7492cc92f8e.zip | |
[spack/spec.py] raise a query failure error if a property query returns None (#7277)
* [SPACK/spec.py] When a query through ForwardQueryToPackage returns
'None', treat that as query failure and raise RuntimeError with
suitable message. This overrides the current behavior to raise an
AttributeError which is now triggered only when no suitable query
property is found and there is no default handler.
* [spack/spec.py] Fix style.
* [SPACK/spec.py] In case of query failure, i.e. property returning
'None', raise AttributeError instead of RuntimeError in order to
pass the unit test. Also, small update in the logic distinguishing
query failure and lack of relevant property/attribute handling.
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions