diff options
| author | Greg Becker <becker33@llnl.gov> | 2023-01-18 15:17:28 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-18 15:17:28 -0800 |
| commit | 08101639cd3af48d101410a03f4791ca13dde2ea (patch) | |
| tree | 7cd5a9f00ca2a38c1a5655349009c7d0df2bcb04 /var | |
| parent | fce95e2efb76da3c6ee549f2a9b4e257fb42ae50 (diff) | |
| download | spack-08101639cd3af48d101410a03f4791ca13dde2ea.tar.gz spack-08101639cd3af48d101410a03f4791ca13dde2ea.tar.bz2 spack-08101639cd3af48d101410a03f4791ca13dde2ea.tar.xz spack-08101639cd3af48d101410a03f4791ca13dde2ea.zip | |
Bugfix: External Python Extensions (#34202)
Normally when using external packages in concretization, Spack ignores
all dependencies of the external. #33777 updated this logic to attach
a Python Spec to external Python extensions (most py-* packages), but
as implemented there were a couple issues:
* this did not account for concretization groups and could generate
multiple different python specs for a single DAG
* in some cases this created a fake Python spec with insufficient
details to be usable (concretization/installation of the
extension would fail)
This PR addresses both of these issues:
* For environment specs that are concretized together, external python
extensions in those specs will all be assigned the same Python spec
* If Spack needs to "invent" a Python spec, then it will have all the
needed details (e.g. compiler/architecture)
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions