Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAINT: prepare for SciPy 1.10.0 "final" #17696

Merged

Conversation

tylerjereddy
Copy link
Contributor

  • Backports included:
  • Update the release notes accordingly, including removal of note about SciPy 1.10.0 not being released yet--let me know if you'd prefer that I do an RC3 instead of the final release at this stage
  • I went with pinning pybind11 to version 2.10.1 in pyproject.toml out of an abundance of caution--we really should be safe to unpin because:
    • the fix for the segfault problem is included in this PR
    • pybind11 2.10.2 has been yanked from PyPI
  • perhaps we go super-conservative for 1.10.0, and then relax this later in the 1.10.x series if things are looking solid with newer pybind11 patch releases? (they almost certainly should be just fine)
  • version numbering changes are normally done in the release process proper (i.e, switch from RC3-> final/released, etc.)

@tylerjereddy tylerjereddy added the maintenance Items related to regular maintenance tasks label Jan 1, 2023
@tylerjereddy tylerjereddy added this to the 1.10.0 milestone Jan 1, 2023
@tylerjereddy
Copy link
Contributor Author

CI is all green with no skip directive active.

There was a request to add a missing contributor (#14386 (comment)), so I'm now going to push in a commit that does that, but skips most of the CI outside of docs stuff.

@tylerjereddy
Copy link
Contributor Author

@rgommers I think this is probably ready to go--if you want me to proceed differently with the pyproject.toml I'm happy to change that--I think we're pretty safe now either way with all the discussion/dissection that happened.

Copy link
Member

@rgommers rgommers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pybind11 version constraint looks good to me. I'd recommend squashing the first 3 commits in this PR. Should be good to go for 1.10.0 final, no need for RC3 I think.

EthanSteinberg and others added 5 commits January 3, 2023 10:45
* remove the pybind11 version exclusion from Windows
Meson job in GitHub actions

* pin pybind11 to version `2.10.1` in `pyproject.toml`
out of an abundance of caution re: recent issues with
`2.10.2` (which has since been yanked from PyPI)

* small adjustment to `pypocketfft.cxx` to defened
against the segfault that occurs with pybind11 `2.10.2`
(arguably not a bug, but safer way to initialize here)
[skip azp] [skip actions] [skip cirrus]
@tylerjereddy
Copy link
Contributor Author

I rewrote the history of this branch as requested, including a clearer commit message for the 3 newly-squashed commits.

If the CI passes again, I'll merge and start the release process.

@tylerjereddy tylerjereddy merged commit 7856f28 into scipy:maintenance/1.10.x Jan 3, 2023
@tylerjereddy tylerjereddy deleted the treddy_110_final_prep branch January 3, 2023 18:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Items related to regular maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants