You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many supporting files that e3sm_diags requires including .cfg, .rgb, .nc, etc. that needs to be installed alongside e3sm_diags. The setup.py file includes logic to move these files around to the correct location in order for them to be correctly installed via python -m pip install ..
Describe the solution you'd like
@xylar suggests that the e3sm_diags data files should have a similar structure internally to what it puts in share/e3sm_diags (related comment). That way the pyproject.toml isn't nearly as bloated and there is less resorting of files required upon installing the package.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
tomvothecoder
changed the title
[DevOps]: Update the structure of supporting files to reduce restoring and bloat in pyproject.toml
[DevOps]: Update the structure of supporting files to reduce re-sorting and bloat in pyproject.tomlNov 20, 2024
Is your feature request related to a problem?
setup.py
withpyproject.toml
for modern Python packaging #895 -- replacessetup.py
withpyproject.toml
There are many supporting files that
e3sm_diags
requires including.cfg
,.rgb
,.nc
, etc. that needs to be installed alongsidee3sm_diags
. The setup.py file includes logic to move these files around to the correct location in order for them to be correctly installed viapython -m pip install .
.Describe the solution you'd like
@xylar suggests that the
e3sm_diags
data files should have a similar structure internally to what it puts inshare/e3sm_diags
(related comment). That way thepyproject.toml
isn't nearly as bloated and there is less resorting of files required upon installing the package.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: