Hmm…not sold on this either.

This is not an outright rejection, but rather would like to see the meld test suite in action first. They have still not released anything apart from the odd-numbered development release series.

remove typing-extensions from RUN_DEPENDS, only needed for < 3.10

• rebase
• use ${PY_TOMLI} shorthand and remove Python < 3.10 stuff

fix botched rebase

• update to 9.2.2

No longer immediately relevant after the revert. Worth discussing the venn diagram regarding __ISO_C_VISIBLE et al since there are gotchas in C as well.

revert to initial diff

use __STDC_VERSION__ to ensure visibility only on C23 and later

There shouldn't be C23-compliant codebases that define their own unreachable(). Based on my understanding of sys/sys/_visible.h, it looks like __ISO_C_VISIBLE is getting defined as 2023 almost unconditionally, at least in base, so it leaked into jemalloc. It may leak into other C codebases if a standard is not explicitly passed or other macros defined during build steps.

In D53433#1232130, @michaelo wrote:

@vishwin Have you had time to check the updated patch? The distutils approach is now behind a switch, being an opt-in.

In D53433#1223609, @arrowd wrote:

In D53433#1223585, @michaelo wrote:

Here is the definition: https://packaging.python.org/en/latest/specifications/binary-distribution-format/

There is a notion of a "platform tag" which denotes the platform for which the wheel has been built if it contains native code, by default it does "$(os}_${release}_${arch}". Run " pip debug --verbose" and see for compatible tags. If a wheel has been compiled with 13.5-RELEASE-p5 it won't be consumed by 13.5-RELEASE-p6. "wheel tags --remove --platform-tag=..." renames the file for multiplatform AND modfies the metadata (Tag: ) in WHEEL file. So I am not rebuilding, I am retagging. I first assumed a bug in poudriere: https://github.com/freebsd/poudriere/issues/1277, but then realized otherwise.

Well, to me it is the python part that should be fixed. FreeBSD guarantees ABI compatibility between minor releases, so the tag should look like py310-none-freebsd_13_amd64. This is the same how pkg handles our native packages ABI.

In D53433#1224442, @michaelo wrote:

In D53433#1224438, @vishwin wrote:

USES=distutils is going away because upstream is removing support for this entirely. It had been deprecated for quite some time but they are finally pulling the switch.

I know, this is why I said that with PEP 517 wheels already there, they just need to be in a distinct, explicit place for consumption.

Can you explain why this change needs revision? ATM, I don't see a way to make it even simple than this. Again, I don't expect you do upload anthing to PyPI. It is just a possible usecaes. I am happy if people can host their own indexes with this.

In D53433#1223076, @michaelo wrote:

My ideal longterm goal: The Project hosts canonical poudriere builds and these could produce FreeBSD-specific wheels which could be uploaded to PyPI and would dramatically improve the situation for the Python ecosystem on FreeBSD.

sync reference to libuuid

• lang/python313: update to 3.13.9