WIP: PEP 503/625 compatibility and Windows MPI tests #530
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.
This PR is primarily to handle some release and GitHub runner related issues, including:
Source distribution filename (#523)
Making the source distribution filename consistent with PEP 625 in turn requires the package name to be consistent with normalized names from PEP 503: "The name should be lowercased with all runs of the characters ., -, or _ replaced with a single - character."
This means that our package name goes from pyGSTi to pygsti. Note that users cloning the repo from GitHub would still have the folder named pyGSTi because the repo name is remaining unchanged. I'm inclined to keep it that way, but am open to being convinced otherwise. This means that this change is mostly hidden from the user -- the most noticeable change is that keen-eyed users will notice that
pip install
commands will now say pygsti instead of pyGSTi, which is a change I'm mostly fine with since they import lowercase pygsti anyway.MPI installation on Windows runners (#522)
WIP. The issue is the MPI installation is borked on Windows GitHub runners. The only way to test this is to push stuff to a branch, so I've chosen to make this the branch to do so.
Upgrade Python versions to 3.9 - 3.12
We currently support Python 3.8 - 3.11, but 3.8 went EOL at the end of last year and Python 3.12 has been out for over a year. We should update this here. We should also tentatively start testing 3.13 since it has been out, but I feel less strongly about getting that support in here.
Unpin Mac runner version
We had the Mac runner version pinned to
macos-13
due to a wheel issue regarding later Mac version, CVXOPT, and Python 3.8 (an unfortunate confluence of version requirements). Now that we are dropping Python 3.8, we can unpin this and finally test on the latest Mac runner (which is nice since the Mojave (macos-14) runners test the M1 chips that we are all running on now, and the Sequoia (macos-15) runner is in beta).