py-pythran: add py312 subport

[erikbs]

Description

Backporting #258ab9a from master (I skipped the test files, since they are not run by MacPorts). MacPorts will install the py312 subport successfully without this patch, but one quickly runs into runtime exceptions. It should be removed the next time the port version is updated.

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 10.9.5 13F1911 x86_64
Xcode 6.2 6C131e

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• checked your Portfile with port lint --nitpick?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

Testing the binaries: I tested the binary indirectly by successfully building SciPy with it.

[macportsbot]

Notifying maintainers:
@reneeotten for port py-pythran.

[barracuda156]

@erikbs This won’t break building of scipy with distutils, right?

[reneeotten]

@erikbs I will add py312 subports for Python ports once I have verified they work. I am/was assuming you do before you submit PRs but from PR #21553 it's clear that didn't happen. So no point submitting PRs for adding py312 subports for Python ports that I maintain.

[erikbs]

@erikbs This won’t break building of scipy with distutils, right?

@barracuda156 It should not. They have simply added try-except blocks that first try to import from distutils, then setuptools if distutils failed.

[erikbs]

@erikbs I will add py312 subports for Python ports once I have verified they work. I am/was assuming you do before you submit PRs but from PR #21553 it's clear that didn't happen. So no point submitting PRs for adding py312 subports for Python ports that I maintain.

@reneeotten Sorry, my intention has not been to put extra work on you. I do not want to disturb if you get the py312 subports done more efficiently alone.

Regarding PR #21553 it was a draft and I did leave the testing checkboxes unchecked. If port content reports that there are binaries, I always try to run them, preferably with options to verify that they actually work. If I have no clue how to use the tool (e.g. if the package is only a dependency for one I need), I leave the checkbox alone and usually leave a note about what I did (as in this case, at the very bottom of the first comment). Also I usually import the package, dir() it and try using a couple of things from it.

I will admit that in this case I failed to reflect enough on the fact that the output of port content was too short, I assumed that it was fine since it contained the same files as the py311 subport you added last year, which was my reference.

[reneeotten]

waiting for the new release before updating the port (see: serge-sans-paille/pythran#2149 and serge-sans-paille/pythran#2167)

[erikbs]

Apparently the py312 subport was added last week (but without the patch that makes it work), so I close this one. See #22080 for the 0.15.0 update.