Skip to content

0.30 release #6126

Description

@davidhewitt

While the 0.29 release is not yet out the door, there have been a few topics which have been notable but not quite ready to ship in 0.29. I wanted to list these here now so that we can avoid forgetting these as we work towards 0.30.

Activity

  1. added theissue type on Jun 11, 2026
  2. ngoldbaum commented on Oct 3, 2026

    @ngoldbaum
    Contributor

    I'm not sure what your plans are @davidhewitt, but it might be nice to do a quick 0.30 release without too much delay, to unblock rust-numpy abi3t support: PyO3/rust-numpy#556 (comment)

  3. davidhewitt commented on Oct 4, 2026

    @davidhewitt
    MemberAuthor

    Agreed, my intent is to test #6321, decide whether it's trivial to ship in 0.30 (or wait to 0.31, sorry for the delay either way @lucascolley), and then prep the release.

    ... have just recently been bogged down in the pile of fixes which ended up being 0.29.3.

  4. dnicolodi commented on Oct 5, 2026

    @dnicolodi

    Agreed, my intent is to test #6321, decide whether it's trivial to ship in 0.30 (or wait to 0.31, sorry for the delay either way @lucascolley), and then prep the release.

    Note that #6321 may not contain the latest tested version of the Meson code required to build PyO3 (I haven't updated it and I don't know whether @lucascolley did). The latest is in mesonbuild/meson-python#874 and applies to PyO3 0.23.2. I haven't looked at the diff between 0.23.2 and 0.23.3 to determine if any update is required.

    It would be great if someone that better understand the PyO3 build would look at this Meson code, and it would be even better if testing of it could be integrated in the PyO3 project. On the other hand, Meson support for Rust is not very mature and integrating the Meson build system upstream may run into some sharp edges.

  5. ngoldbaum commented on Oct 5, 2026

    @ngoldbaum
    Contributor

    and it would be even better if testing of it could be integrated in the PyO3 project

    Yeah, I like the idea of somehow running the full PyO3 test suite using meson instead of build.rs files. Anything else is likely to bitrot.

    So definitely not trivial to merge as-is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions