I am fine with that. Others should have a look as well. Do you plan to MFC it to 15?

Here is the reason for 3.3.0: https://github.com/pythongssapi/python-gssapi/commit/4a4d42d22bcd0e2fc99b9b87197b16d825a62528

In D59848#1373592, @vishwin wrote:

Upstream is explicitly not allowing cython 3.3 for the 6.1 branch. The 7.0 branch, which is still only in beta, requires cython 3.3 or later, however.

This is required for https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=298650

@pouria Is this something you can review? I am totally unknowledgeable here.

Thank you @imp , what is your opinion on MFC?

In D52148#1191627, @chandrakanth.patil_broadcom.com wrote:

In D52148#1191111, @imp wrote:

I think that while our driver may be up to date, our man page describing what's supported may be lagging a little, especially for OEMs. Is that something you can look into updating?

ok. I will check what is missing in the man page and will update accordingly.

@kevans Anything holding your off applying it?

See also my testing results in the bugzilla issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294353#c2

Can this be finally applied to 16-CURRENT?

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://wiki.freebsd.org/Python/PortsPolicy#PORTNAME and made this port right.