Resolve build infrastructure errors (with mpi4py, gams, networkx) #3018
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.
Fixes # .
Summary/Motivation:
This resolves numerous several errors relating to the build/test infrastructure that all arose during the migration to supporting Python 3.12:
openmpi
installation on conda started triggering installation errors. In the end, this switches the tests to not specifying openmpi (and instead defaulting to using mpich). In the course of working on this, it also identified bugs in the logic for skipping MPI tests.networkx
had a broken build pushed to pypi that enabled installation of 3.2 on Python 3.8 (3.2 requires Python >= 3.9). This refines our optional requirements to explicitly exclude networkx 3.2 on Python < 3.9. This highlighted a bug in how we were doing version comparison insetup.py
Changes proposed in this PR:
openmpi
networkx
version for python<3.9GamsExceptionExecution
Legal Acknowledgement
By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution: