Skip to content

Conversation

@edgarrmondragon
Copy link
Contributor

@edgarrmondragon edgarrmondragon commented Jun 6, 2025

The second beta was published a little over a week ago and the the first RC is coming out next month, so it's probably a good time to start building these 🙂

Successful "Package" job: https://github.com/edgarrmondragon/py-setproctitle/actions/runs/15587496141.

env:
CIBW_BUILD: ${{matrix.pyver}}-*
CIBW_ENABLE: cpython-freethreading
CIBW_ENABLE: cpython-prerelease
Copy link
Owner

Choose a reason for hiding this comment

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

I see that you moved this setting in the pyproject.toml file. Why is this setting defined here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's following advice from https://cibuildwheel.pypa.io/en/stable/options/#enable:

It is generally not recommended to use cpython-prerelease in a config file, as it's intended for testing pre-releases for a 2-3 month period only.

No strong opinion from me either way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

...and that suggestion is gone in the latest docs so I guess it's OK to move this to pyproject.toml 😅

env:
CIBW_BUILD: pp*
CIBW_SKIP: pp37-*
CIBW_ENABLE: pypy-eol
Copy link
Owner

Choose a reason for hiding this comment

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

I would rather drop support for EOL'd versions, contextually with the 3.14 release or earlier.

Copy link
Contributor Author

@edgarrmondragon edgarrmondragon Jun 9, 2025

Choose a reason for hiding this comment

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


- name: Build wheels
uses: pypa/cibuildwheel@v2.23.3
uses: pypa/cibuildwheel@v3.0.0rc2
Copy link
Owner

Choose a reason for hiding this comment

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

Maybe we should wait for the final version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Of course, happy to wait for the final 3.0 release!

Copy link
Contributor Author

@edgarrmondragon edgarrmondragon Jun 10, 2025

Choose a reason for hiding this comment

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

Copy link
Contributor Author

@edgarrmondragon edgarrmondragon Jun 11, 2025

Choose a reason for hiding this comment

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

This is now using the final v3.0.0 release v3.1.0 release.

@edgarrmondragon edgarrmondragon force-pushed the cp314-wheels branch 2 times, most recently from 2ccdaf2 to b6bd48c Compare July 24, 2025 03:33
@edgarrmondragon
Copy link
Contributor Author

@dvarrazzo this is g2g imo

@dvarrazzo
Copy link
Owner

Thank you! I squashed your commits and trying a build on our side. If packages are all ok I'll merge.

@dvarrazzo dvarrazzo merged commit 0225735 into dvarrazzo:master Sep 4, 2025
131 checks passed
@edgarrmondragon edgarrmondragon deleted the cp314-wheels branch September 4, 2025 21:02
@edgarrmondragon
Copy link
Contributor Author

Thanks!

One of the builds seems to have got stuck: https://github.com/dvarrazzo/py-setproctitle/actions/runs/17476102842/job/49636232418

@dvarrazzo
Copy link
Owner

Yes, I got it unstucked and released 1.3.7 packages on PyPI.

Thank you very much!

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.

2 participants