On Tue, Feb 9, 2016 at 11:47 AM, Todd Gamblin <[email protected]> wrote:
> FWIW, the Spack Python builds (for 3.5 and 2.7 at least) work on El > Capitan, thanks to a number of recent contributions. They don't use any > patches. > With GCC? > > Spack bridges the everything-in-its-own-prefix gap by allowing you to > activate/deactivate python packages on the fly. You install the module in > its own prefix then `spack activate <module>`, and it is symlinked into > place within the python prefix (with special handling for eggs, .pth files, > etc.) > > Think of it as though each python installation is its own virtualenv. > Modules are installed in their own prefix but can be symlinked into the > python prefix on demand: > http://software.llnl.gov/spack/basic_usage.html#extensions-python-support > http://software.llnl.gov/spack/packaging_guide.html#extensions > > We use this to manage Python installs at LLNL. The same support can be > implemented for other languages that have their own module systems via > Spack extensions (e.g., we're thinking about lua). > Thank you, that looks like it's well thought through. -- Elizabeth
