Skip to content

Python as a virtual dependency #7966

@mkuron

Description

@mkuron

I'm creating a separate issue for this request that was previously discussed at #2215 (comment) with @alalazo.

There are multiple Python packages available in Spack (python, miniconda2, miniconda3); an Anaconda package has been requested (#2738, #2741), and some of the alternative interpreters (e.g. Jython, PyPy) might also be packaged at some point (even though they only support a subset of Python libraries). Since all these packages provide a Python interpreter and libraries, there should logically be a Python virtual package and the existing Python package should be renamed to CPython.

This has two advantages:

@citibeth voiced her concerns about making such a change as the Python package is a bit special and the change might break other things. However, with #7955 this might become easier to implement.

I already tried to implement this change, but ran into some issues (#2215 (comment)). @alalazo also wanted to give it a try.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions