3310eaab99
The current implementation of `spack-python` will leave an extra shell around while it runs. That shell should really replace itself with spack. - [x] add exec to spack-python script
25 lines
744 B
Bash
Executable file
25 lines
744 B
Bash
Executable file
#!/bin/sh
|
|
#
|
|
# Copyright 2013-2020 Lawrence Livermore National Security, LLC and other
|
|
# Spack Project Developers. See the top-level COPYRIGHT file for details.
|
|
#
|
|
# SPDX-License-Identifier: (Apache-2.0 OR MIT)
|
|
|
|
#
|
|
# spack-python
|
|
#
|
|
# If you want to write your own executable Python script that uses Spack
|
|
# modules, on Mac OS or maybe some others, you may be able to do it like
|
|
# this:
|
|
#
|
|
# #!/usr/bin/env spack python
|
|
#
|
|
# Mac OS supports the above syntax, but it's not standard and most Linuxes
|
|
# don't support more than one argument after the shebang command. This
|
|
# script is a workaround. Do this in your Python script instead:
|
|
#
|
|
# #!/usr/bin/env spack-python
|
|
#
|
|
# This is compatible across platforms.
|
|
#
|
|
exec /usr/bin/env spack python "$@"
|