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

Document python environment and methodology #1302

Closed
srherbener opened this issue Sep 17, 2024 · 4 comments · Fixed by #1367
Closed

Document python environment and methodology #1302

srherbener opened this issue Sep 17, 2024 · 4 comments · Fixed by #1367
Assignees
Labels
INFRA JEDI Infrastructure

Comments

@srherbener
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Python package management is difficult to do in a consistent manner across many platforms. There exist many ways to tackle this problem and if a wide variety of approaches are utilized this becomes unmanageable in regard to support and maintenance.

There exist two areas of concern

  • The python environment being used by spack (ie, SPACK_PYTHON)
  • The python environment being used by an application that was built based on a spack-stack environment

spack-stack development has been moving toward a relatively simple and consistent method for setting up and using the spack python environment and the application python environment. At this point we need to document and help foster adoption of these method.

Describe the solution you'd like
Documentation exists that explains the management of python for both spack-stack development, and applications (built upon spack-stack) environments.

Additional context
None

@srherbener srherbener self-assigned this Sep 17, 2024
@srherbener srherbener added the INFRA JEDI Infrastructure label Sep 17, 2024
@climbfuji
Copy link
Collaborator

@christinaholtNOAA FYI

@christinaholtNOAA
Copy link

Documentation in this area would be a huge value add.

@srherbener
Copy link
Collaborator Author

Any thoughts about where this documentation should live: spack-stack ReadTheDocs, spack-stack Wiki? I'm leaning toward the Wiki, but I'm okay if ReadTheDocs (or some other place) is preferred. tagging @climbfuji, @AlexanderRichert-NOAA.

Thanks!

@climbfuji
Copy link
Collaborator

I'd say readthedocs

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 a pull request may close this issue.

4 participants