spack: Package cannot depend on python@2.7
A lot of Python packages depend on Python 2.7 and/or Python 3.4. If you explicitly say depends_on('python@2.7'), it tries to build exactly 2.7 and fails. We should prob make this work.
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 19 (19 by maintainers)
Commits related to this issue
- Added examples of getting the right behavior from depends_on(). See #1035 — committed to citibeth/spack by deleted user 10 years ago
- Documentation Improvements for SC16 (#1676) * Transferred pending changes from efischer/develop * 1. Rewrite of "Getting Started": everything you need to set up Spack, even on old/ornery systems. ... — committed to spack/spack by deleted user 10 years ago
- Add morph-validator to morphology workflow dependencies (#1035) — committed to olupton/spack by deleted user 6 years ago
The use of the Python version
2.8is confusing. I believe the lines above are only correct since we know that there will not be a Python 2.8. I suggest using2.999and2.7.999instead, respectively, so that readers who are unaware of Python versions will “naively” understand how to carve out version number intervals for their own packages.