Skip to content

Remove Python 3.8 support - #224

Open
MatthewRHermes wants to merge 1 commit into
pyscf:masterfrom
MatthewRHermes:drop-py38
Open

MatthewRHermes wants to merge 1 commit into
pyscf:masterfrom
MatthewRHermes:drop-py38

Conversation

@MatthewRHermes

Copy link
Copy Markdown
Collaborator

Follows pyscf/pyscf#3500, which dropped Python 3.8 from PySCF core.

Changes

  • ci.yml: the linux-build matrix tests 3.9 instead of 3.8 (now 3.9, 3.10, 3.12).
  • setup.py: add python_requires='>=3.9'. pyscf-forge didn't declare a minimum Python before, so pip on 3.8 would still install new releases. Afterwards, pip on 3.8 stays on pyscf-forge 1.1.1.

Nothing else in the repo assumes 3.8. The lint jobs and the manylinux wheel build in publish.yml already use 3.9, and there are no sys.version_info shims for 3.8. pyscf.afqmc keeps its own 3.10+ requirement.

This should also retire the intermittent linux-build (3.8) segfault in occri/test/test_regression.py (inside LAPACK ?sygvd via scipy.linalg.eigh, _decomp.py:577). That crash has only been seen on the 3.8 leg, where scipy<1.16 resolves to scipy 1.10.1 / numpy 1.24.4.

No conflicts with #221 or #223: the three PRs touch disjoint files.

Code changes and this description were drafted with the assistance of Claude Opus 5.5.

🤖 Generated with Claude Code

Follow pyscf/pyscf#3500: test Python 3.9 in CI instead of 3.8, and
declare python_requires='>=3.9' so pip on 3.8 no longer picks up new
pyscf-forge releases.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant