Merge py-pandas, py-awscrt, texinfo, and ectrans bug fixes from release/1.5.1 (with mods from spack develop) #831
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR brings the bug fixes for the packages listed above that went into
release/1.5.1
first down todevelop
. There is a small update that is due to the modifications from spackdevelop
(see JCSDA/spack#346 for the glorious details), namely the addition of theexcel
variant forpy-pandas
.Note that we need to stick with
[email protected]
for a while, because I encountered build problems on my macOS with newer versions due to some complicatedpy-numba
-llvm
compiler dependencies.Testing
Applications affected
JEDI applications, although
py-pandas+excel
is really only used injedi-tools-env
.Systems affected
All systems that install the unified environment.
Dependencies
Issue(s) addressed
All Github issues were resolved when merging the updates into
release/1.5.1
, this is just bringing the improved and spack-sanctioned versions intodevelop
. However, this PR does solve the current container CI failures for the Intel container (these run only twice a week on a nightly schedule usingdevelop
, errors are reported to the CI slack channel in the JCSDA workspace; see https://github.com/JCSDA/spack-stack/actions/runs/6516462554 for an example of a failed Intel container build).Checklist