Rebase

Please MFC this.

Ports is question have been reported and patches provided:

• https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297837
• https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297836
• https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297823
• misc/py-polars-runtime is open

@vishwin Picked up your comments and addresses this one.

In D53433#1356107, @vishwin wrote:

I guess I didn't make myself clear enough.

In D53433#1356068, @michaelo wrote:

In D53433#1356059, @vishwin wrote:

Most of the D58861 cases are abusing PEP517_BUILD_CMD or PEP517_INSTALL_CMD in some way. Documenting those variables' availability does not necessarily mean they should be used except in exceptional circumstances, such as when build is not available due to circular dependencies.

Most of these cases will go away with a newer version of setuptools; some of them can be fixed by changing the portname, like beautifulsoup to beautifulsoup4. Given there are only tens of ports deviating compared to the thousands of others that already work, I consider them only as background noise.

Those setuptools cases should be patching the relevant metadata file until we can update setuptools itself. The uv cases should be using devel/py-build.

• Simplify Python discovery; the build frontend will pass the interpreter

@vishwin, I have picked up your comments and https://reviews.freebsd.org/D59133 and made this port right.

Remove variable

@vishwin, reduced to a bare minimum now

Make the dir a literal, no more variable, thus implementation detail

In D53433#1356059, @vishwin wrote:

Most of the D58861 cases are abusing PEP517_BUILD_CMD or PEP517_INSTALL_CMD in some way. Documenting those variables' availability does not necessarily mean they should be used except in exceptional circumstances, such as when build is not available due to circular dependencies.

Sort for portclippy

@vishwin, is this as expected now?

Replace += with =

A leftover from previous code, changed and tested

Rebase

@yuri, please have a look.

Addon:
One thing worth spelling out for the record, since it came up earlier: a toggle (whether per-port or tree-wide) wouldn't actually change what's required here. Any port overriding PEP517_BUILD_CMD/PEP517_INSTALL_CMD directly, or invoking a build tool standalone (e.g. maturin), still needs its own explicit path update on both the build and install side regardless of what a switch defaults to — otherwise the two sides silently disagree on where the wheel lives and the port breaks. That's the entire content of the follow-up sweep commit; a toggle doesn't remove or shrink it, since those ports never go through the framework default in the first place.

Subsequent review for ports which require extra treatment: https://reviews.freebsd.org/D58861, all builds pass for me. Some of them will go away as soon as setuptools is being updated, e.g., wheel name normalization.

@vishwin Took me way too long to respond. you are right on the distutils,
I have dropped the entire block and will be moved to a separate discussion,
if at all.

Found this completely by incident while working on python.mk improvements. At least setup.py changes could be upstream. They are straight forward.

@vishwin This should be good now, take another look please.

Changes applied.

Address comments and lowercase wheel name in setup.py

Applies cleanly down to stable/14 with a small fix.

Trying to merge locally and see whether it can easily be MFC'ed after a week. Hold tight.

rebase onto main

In D46313#1349641, @mail_fbsd2.e4m.org wrote:

I am unsure about what is missing apart from the alphabetical sorting (which should be done in a separate review
according to kevans). But I need some advice regarding this -- see my comment above.
If s.th. else is missing please let me know...

As far as I can see there are only a few comments left from @kevans and @ziaee on the manpage and we are good. @mail_fbsd2.e4m.org, can you address them and we are good to merge?

Can I MFC this after three days? Any objections?

Unfortunately, there is very little I can contribute here. My knowledge in regards of all of these FWs is close to zero.

Builds for me.