Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add instructions for configuring a spack-stack based python environment #1367

Merged
merged 3 commits into from
Nov 6, 2024

Conversation

srherbener
Copy link
Collaborator

Summary

Instructions are added to the UsingSpackEnvironments.rst showing how to configure and use a consistent python virtual environment based on spack-stack.

Testing

Built html on my Mac laptop and verified that the new instructions are rendered properly.

Applications affected

Documentation only update

Systems affected

Documentation only update

Dependencies

None

Issue(s) addressed

Resolves #1302

Checklist

  • This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.

@@ -5,6 +5,14 @@ Using spack-stack environments

The following tutorial assumes you have a functioning spack-stack environment installed local to your system. This environment is provided on platforms described in :numref:`Section %s <Preconfigured_Sites>`. If you intend to run spack-stack on your developer machine or on a new platform, you can create an environment using the steps described in :numref:`Section %s <NewSiteConfigs>`.

There are three steps in setting up a usable development environment.
The first is to load the spack-stack environment and the second is to create a python virtual environment that is based on the python executable included within the spack-stack installation.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be useful to mention here that as many as possible of the spack-stack Python modules (not just the executable) should be loaded when using/installing additional packages in the virtual environment.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, when you push updates, please include [skip ci] in the commit message - no need to run the tests for doc updates only.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a note encouraging the use of the spack-stack installed python modules.

@climbfuji climbfuji merged commit 38cf079 into JCSDA:develop Nov 6, 2024
1 check passed
@climbfuji climbfuji deleted the feature/doc-python-env branch November 6, 2024 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
INFRA JEDI Infrastructure
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document python environment and methodology
2 participants