Re: /usr/bin/python will be removed in macOS 12.3!

[Ryan Schmidt]

On Feb 24, 2022, at 12:35, Bjarne D Mathiesen wrote:

> "#!/usr/bin/env python" might not be a problem
> iff
>   the macports python is also installed as a prerequisite
>   the ${PATH} variable includes '/opt/local/bin'

The /opt/local/bin/python symlink will only exist if the user has used "sudo 
port select python ...". This symlink is intended only for the user's 
convenience. We don't want ports to rely on its existence (or behave 
differently if it exists).

Re: /usr/bin/python will be removed in macOS 12.3!

[Bjarne D Mathiesen]

"#!/usr/bin/env python" might not be a problem
iff
the macports python is also installed as a prerequisite
the ${PATH} variable includes '/opt/local/bin'

Ryan Schmidt wrote:
> On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
> 
>> But how does one (a) find out the dependency exists and (b) make sure the 
>> software finds python from MacPorts?
> 
> General-purpose answers to either question are not possible. Each affected 
> port will need to be investigated and fixed in its own unique way.
> 
> /usr/bin/python might be used
> 
> * directly by the Portfile specifying /usr/bin/python somewhere
> * in a patchfile that references /usr/bin/python explicitly
> * as a shebang line (e.g. "#!/usr/bin/python" or "#!/usr/bin/env python") in 
> files used by the port at build time and/or installed by the port 
> * by a build system that uses the first binary it finds named "python"
> * in unknowable other ways
> 
> To tell the build system to use a particular python, one might need to
> 
> * set the PYTHON environment variable at configure time -- this is 
> accomplished by setting the configure.python option
> * specify some other configure environment variable or argument
> * patch files
> * do something else
> 

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina
2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM
ATI Radeon RX 590 8 GB

Re: /usr/bin/python will be removed in macOS 12.3!

[Bjarne D Mathiesen]

$=> cd
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
$=> fgrep -R '/usr/bin/env python' * \
| awk -F ':' '{print $1}' \
| sort -u \
| wc -l
 140
bjarne@MacPro 19:16:42
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
$=> fgrep -R '/usr/bin/env python' * \
| awk -F ':' '{print $1}' \
| sort -u
audio/xmms2/Portfile
databases/libpqxx/Portfile
devel/aap/files/patch-python27.diff
devel/cask/Portfile
devel/cppcheck/Portfile
devel/diffuse/Portfile
devel/distcc/Portfile
devel/flawfinder/Portfile
devel/git-cinnabar/Portfile
devel/git-cinnabar/files/patch-python3
devel/git-filter-repo/Portfile
devel/git-remote-hg/Portfile
devel/global/Portfile
devel/gtk-mac-bundler/Portfile
devel/icompile/Portfile
devel/kcov/files/bin-to-c-source.py.use-python38.patch
devel/meson/Portfile
devel/nodejs10/Portfile
devel/nodejs12/Portfile
devel/nodejs13/Portfile
devel/nodejs14/Portfile
devel/nodejs15/Portfile
devel/nodejs16/Portfile
devel/nodejs17/Portfile
devel/nodejs8/Portfile
devel/play/Portfile
devel/scons/files/python-interp.patch
devel/tortoisehg/Portfile
devel/viewvc/Portfile
games/pyfa/Portfile
games/ski/files/use-macports-python.patch
games/sounddecompress/Portfile
gis/grass7/Portfile
gis/grass7/files/patch-grass.py.diff
gis/openstreetmap-carto/Portfile
gnome/epiphany/files/patch-post-install-python.diff
gnome/gobject-introspection-devel/Portfile
gnome/mm-common/files/patch-use-our-python3.diff
gnome/virt-manager/Portfile
graphics/asymptote/Portfile
graphics/asymptote/files/patch-Makefile.diff
graphics/comix/Portfile
graphics/gimp-help-en/Portfile
graphics/gimp-resynthesizer/files/patch-python.diff
graphics/ipe-tools/files/patch-svgtoipe-svgtoipe.py.diff
graphics/libepoxy/files/patch-src-gen_dispatch.py.diff
irc/hexchat/files/patch-build-scripts-python3.diff
java/dualist/files/dualist-mecab
kde/py-pykde4/Portfile
lang/emscripten/files/patch-macports_python.diff
lang/ghc-bootstrap/files/clang-wrapper
lang/ghc/Portfile
lang/ispc/Portfile
lang/jython/Portfile
lang/llvm-10/Portfile
lang/llvm-11/Portfile
lang/llvm-3.3/Portfile
lang/llvm-3.4/Portfile
lang/llvm-3.7/Portfile
lang/llvm-5.0/Portfile
lang/llvm-6.0/Portfile
lang/llvm-7.0/Portfile
lang/llvm-8.0/Portfile
lang/llvm-9.0/Portfile
lang/python26/files/patch-Lib-cgi.py.diff
lang/python27/files/patch-Lib-cgi.py.diff
lang/python310/files/patch-Lib-cgi.py.diff
lang/python311-devel/files/patch-Lib-cgi.py.diff
lang/python32/files/patch-Lib-cgi.py.diff
lang/python33/files/patch-Lib-cgi.py.diff
lang/python34/files/patch-Lib-cgi.py.diff
lang/python35/files/patch-Lib-cgi.py.diff
lang/python36/files/patch-Lib-cgi.py.diff
lang/python37/files/patch-Lib-cgi.py.diff
lang/python38/files/patch-Lib-cgi.py.diff
lang/python39/files/patch-Lib-cgi.py.diff
math/dolfin/Portfile
math/libsvm/files/fselect.py
math/libsvm/files/gridregression.py
math/libsvm/files/plotroc.py
math/plda/Portfile
multimedia/mythtv.27/Portfile
multimedia/mythtv.28/Portfile
multimedia/openshot-qt/Portfile
multimedia/subdownloader/Portfile
net/avahi/files/build-db
net/davix/Portfile
net/ipcheck/Portfile
net/iproute2mac/Portfile
net/mosquitto/Portfile
net/munin/Portfile
news/hellanzb/files/patch-hellanzb.py.diff
print/fonttools-utils/Portfile
python/logcat-color3/Portfile
python/py-clang/files/setup.py
python/py-djvubind/Portfile
python/py-geoip/Portfile
python/py-gpilab-framework/Portfile
python/py-isce2/Portfile
python/py-jsonschema/files/patch-setup.py.diff
python/py-logcat-color/Portfile
python/py-magpy/Portfile
python/py-ngl/Portfile
python/py-pmw/Portfile
python/py-pmw/files/patch-pmw2.diff
python/py-pyrexdoc/files/patch-pyrexdoc.py
python/py-xlsx2csv/Portfile
python/quodlibet/Portfile
science/bali-phy/files/patch-bp_analyze.diff
science/bali-phy/files/patch-run_tests.py.diff
science/bowtie/Portfile
science/bowtie2/Portfile
science/gr-air-modes/files/patch-cmake_Modules_GrPython.cmake.diff
science/osmocore/files/patch-fix-python.devel.diff
science/osmocore/files/patch-fix-python.release.diff
science/pdb2pqr/Portfile
science/relax/files/relax.patch
science/root6/Portfile
science/sumo/Portfile
science/tophat/Portfile
science/yorick-spydr/Portfile
science/yorick-yao/Portfile
security/cfv/files/patch-cfv.diff
security/denyhosts/files/patch-daemon-control-dist.diff
security/sqlmap/Portfile
sysutils/autojump/Portfile
sysutils/bpytop/Portfile
sysutils/duplicity/Portfile
sysutils/edmv/Portfile
sysutils/lirc/Portfile
sysutils/pypi2port/Portfile
sysutils/terminator/Portfile
sysutils/zeroinstall-injector/Portfile
textproc/doclifter/Portfile
textproc/grc/Portfile
textproc/simstring/Portfile
textproc/txt2tags/Portfile
www/duckytool/Portfile
www/sitemap_gen/Portfile
www/uzbl/Portfile


Ryan Schmidt wrote:
> On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
> 
>> But how does one (a) find out the dependency exists and (b) make sure the 
>> software finds python from MacPorts?
> 
> General-purpose answers to either question are 

Re: /usr/bin/python will be removed in macOS 12.3!

[Bjarne D Mathiesen]

=> $cd
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
=> fgrep -R '/usr/bin/python' * \
| awk -F ':' '{print $1}' \
| sort -u \
| wc -l
  67
bjarne@MacPro 19:06:33
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports
$=> fgrep -R '/usr/bin/python' * \
| awk -F ':' '{print $1}' \
| sort -u
aqua/namebench/Portfile
devel/bakefile/Portfile
devel/gtk-mac-bundler/files/patch-0.7.4-to-24Feb2016.diff
devel/icompile/Portfile
devel/icu/Portfile
devel/icu58/Portfile
devel/libtapi/Portfile
devel/redo/Portfile
devel/reinteract/files/patch-python.diff
editors/MacVim/files/patch-python.diff
editors/vim/files/patch-python.diff
gis/mapnik/Portfile
graphics/Aseprite/Portfile
graphics/birdfont/Portfile
graphics/gimp3-devel/Portfile
graphics/netpbm/Portfile
graphics/netpbm/files/patch-python.diff
graphics/opencv3-devel/Portfile
graphics/opencv3/Portfile
graphics/opencv4-devel/Portfile
graphics/opencv4/Portfile
lang/ghc-bootstrap/files/clang-wrapper
lang/llvm-10/Portfile
lang/llvm-11/Portfile
lang/llvm-3.3/Portfile
lang/llvm-3.7/Portfile
lang/llvm-5.0/Portfile
lang/llvm-6.0/Portfile
lang/llvm-7.0/Portfile
lang/llvm-8.0/Portfile
lang/llvm-9.0/Portfile
lang/mrustc/Portfile
mail/signing-party/Portfile
math/plda/Portfile
multimedia/mythtv.27/Portfile
multimedia/mythtv.28/Portfile
net/http-replicator/Portfile
net/ipcheck/Portfile
net/pastebinit/Portfile
python/py-gdata/Portfile
python/py-geoip/Portfile
python/py-gtfs/Portfile
python/py-urlgrabber/Portfile
python/trim_osc/Portfile
science/gr-air-modes/files/patch-cmake_Modules_GrPython.cmake.diff
science/pdb2pqr/Portfile
science/root6/Portfile
sysutils/python2_select/files/python23-apple
sysutils/python2_select/files/python25-apple
sysutils/python2_select/files/python25-apple.mtln
sysutils/python2_select/files/python26-apple
sysutils/python2_select/files/python26-apple.mtln
sysutils/python2_select/files/python27-apple
sysutils/python2_select/files/python27-apple.mtln
sysutils/python_select/files/python23-apple
sysutils/python_select/files/python25-apple
sysutils/python_select/files/python25-apple.mtln
sysutils/python_select/files/python26-apple
sysutils/python_select/files/python26-apple.mtln
sysutils/python_select/files/python27-apple
sysutils/python_select/files/python27-apple.mtln
textproc/doclifter/Portfile
textproc/unicode/Portfile
textproc/xmlbird/Portfile
www/clearsilver/Portfile
www/lighttpd/files/patch-conf.diff
www/webkit-gtk-2.0/Portfile


Ryan Schmidt wrote:
> On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
> 
>> But how does one (a) find out the dependency exists and (b) make sure the 
>> software finds python from MacPorts?
> 
> General-purpose answers to either question are not possible. Each affected 
> port will need to be investigated and fixed in its own unique way.
> 
> /usr/bin/python might be used
> 
> * directly by the Portfile specifying /usr/bin/python somewhere
> * in a patchfile that references /usr/bin/python explicitly
> * as a shebang line (e.g. "#!/usr/bin/python" or "#!/usr/bin/env python") in 
> files used by the port at build time and/or installed by the port 
> * by a build system that uses the first binary it finds named "python"
> * in unknowable other ways
> 
> To tell the build system to use a particular python, one might need to
> 
> * set the PYTHON environment variable at configure time -- this is 
> accomplished by setting the configure.python option
> * specify some other configure environment variable or argument
> * patch files
> * do something else
> 

-- 
Bjarne D Mathiesen
Korsør ; Danmark ; Europa
---
denne besked er skrevet i et totalt M$-frit miljø
MacPro 2010 ; OpenCore + macOS 10.15.7 Catalina
2 x 3,46 GHz 6-Core Intel Xeon ; 256 GB 1333 MHz DDR3 ECC RDIMM
ATI Radeon RX 590 8 GB

Re: /usr/bin/python will be removed in macOS 12.3!

[Jason Liu]

SIP is only the beginning of your boot disk headaches.

Starting with Catalina, and continuing into Big Sur, Apple made it
increasingly difficult to make any modifications to anything in the system
volume. In Catalina, the root volume was split into two: the System volume
and Data volume, and the System volume is mounted read-only. Starting in
Big Sur, the System volume is not just read-only, but the entire volume is
now also cryptographically signed, and is referred to as a Signed System
Volume (SSV).

https://eclecticlight.co/2020/06/25/big-surs-signed-system-volume-added-security-protection/

I remember reading online somewhere that an SSV which has been unsealed can
never be fully re-sealed, even if you bless a new snapshot, but I can't
seem to find where it was that I saw that anymore.

See also:

https://apple.stackexchange.com/questions/395508/can-i-mount-the-root-system-filesystem-as-writable-in-big-sur

-- 
Jason Liu


On Tue, Feb 22, 2022 at 6:17 PM Gerben Wierda via macports-dev <
macports-dev@lists.macports.org> wrote:

> > For a test I was planning to adapt the migration approach. Save the
> ‘requested’ list. Uninstall all ports. Temporary mv /usr/bin/python out of
> the way. Build the requested list.
> >
> > I can do this on a secondary system.
> >
> > This would tell me at least that the ports I have installed all install
> without /usr/bin/python, which takes care of any build dependencies.
>
> I did try, but failed. I was able to turn off system integrity protection,
> but that still leaves me with a boot disk that is read-only, so temporarily
> moving /usr/bin/python out of the way did not work. I haven’t investigated
> going beyond simply disabling SIP.
>
> So far, then, no success at trying to emulate the 12.3 macOS situation
> regarding python on macOS 12.2.1.
>
> G

Re: /usr/bin/python will be removed in macOS 12.3!

[Gerben Wierda via macports-dev]

> For a test I was planning to adapt the migration approach. Save the 
> ‘requested’ list. Uninstall all ports. Temporary mv /usr/bin/python out of 
> the way. Build the requested list.
> 
> I can do this on a secondary system.
> 
> This would tell me at least that the ports I have installed all install 
> without /usr/bin/python, which takes care of any build dependencies.

I did try, but failed. I was able to turn off system integrity protection, but 
that still leaves me with a boot disk that is read-only, so temporarily moving 
/usr/bin/python out of the way did not work. I haven’t investigated going 
beyond simply disabling SIP.

So far, then, no success at trying to emulate the 12.3 macOS situation 
regarding python on macOS 12.2.1.

G

Re: /usr/bin/python will be removed in macOS 12.3!

[Gerben Wierda via macports-dev]

> On 21 Feb 2022, at 17:06, Ryan Schmidt  wrote:
> 
> On Feb 19, 2022, at 11:06, Gerben Wierda wrote:
> 
>> But how does one (a) find out the dependency exists and (b) make sure the 
>> software finds python from MacPorts?
> 
> General-purpose answers to either question are not possible. Each affected 
> port will need to be investigated and fixed in its own unique way.
> 
> /usr/bin/python might be used
> 
> * directly by the Portfile specifying /usr/bin/python somewhere
> * in a patchfile that references /usr/bin/python explicitly
> * as a shebang line (e.g. "#!/usr/bin/python" or "#!/usr/bin/env python") in 
> files used by the port at build time and/or installed by the port 
> * by a build system that uses the first binary it finds named "python"
> * in unknowable other ways
> 
> To tell the build system to use a particular python, one might need to
> 
> * set the PYTHON environment variable at configure time -- this is 
> accomplished by setting the configure.python option
> * specify some other configure environment variable or argument
> * patch files
> * do something else


For a test I was planning to adapt the migration approach. Save the ‘requested’ 
list. Uninstall all ports. Temporary mv /usr/bin/python out of the way. Build 
the requested list.

I can do this on a secondary system.

This would tell me at least that the ports I have installed all install without 
/usr/bin/python, which takes care of any build dependencies.

Gerben Wierda (LinkedIn )
R IT Strategy  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

Re: /usr/bin/python will be removed in macOS 12.3!

[Ryan Schmidt]

On Feb 19, 2022, at 11:06, Gerben Wierda wrote:

> But how does one (a) find out the dependency exists and (b) make sure the 
> software finds python from MacPorts?

General-purpose answers to either question are not possible. Each affected port 
will need to be investigated and fixed in its own unique way.

/usr/bin/python might be used

* directly by the Portfile specifying /usr/bin/python somewhere
* in a patchfile that references /usr/bin/python explicitly
* as a shebang line (e.g. "#!/usr/bin/python" or "#!/usr/bin/env python") in 
files used by the port at build time and/or installed by the port 
* by a build system that uses the first binary it finds named "python"
* in unknowable other ways

To tell the build system to use a particular python, one might need to

* set the PYTHON environment variable at configure time -- this is accomplished 
by setting the configure.python option
* specify some other configure environment variable or argument
* patch files
* do something else

Re: /usr/bin/python will be removed in macOS 12.3!

[Steven Smith]

> On Sat, Feb 19, 2022 at 05:23:41PM +, Christopher Jones wrote:
>>> But how does one (a) find out the dependency exists and (b) make
>>> sure the software finds python from MacPorts?


Lots of ports take the obvious approach of simply creating a symlink or 
“python3" to MacPorts’s  Python in, say, ${workpath}/bin$, then sticking this 
directory at the front of PATH.

See, e.g.

https://github.com/macports/macports-ports/blob/master/databases/arangodb/Portfile
 




smime.p7s
Description: S/MIME cryptographic signature

Re: /usr/bin/python will be removed in macOS 12.3!

[Clemens Lang]

On Sat, Feb 19, 2022 at 05:23:41PM +, Christopher Jones wrote:
> > But how does one (a) find out the dependency exists and (b) make
> > sure the software finds python from MacPorts?
> 
> Not so easy, as it could be hidden away in the build infrastructure.
> It might not be at all obvious from just looking at the port file...

You could patch trace mode to deny access to /usr/bin/python or files in
/usr/lib/python2.7. See src/port1.0/porttrace.tcl around line 200.

-- 
Clemens

Re: /usr/bin/python will be removed in macOS 12.3!

[Christopher Jones]

> On 19 Feb 2022, at 5:06 pm, Gerben Wierda  wrote:
>
> Well, yes, I kind of knew already that it was a terrible idea. Kind of felt 
> terrible in the first place (was just checking).
>
> But how does one (a) find out the dependency exists and (b) make sure the 
> software finds python from MacPorts?

Not so easy, as it could be hidden away in the build infrastructure. It might 
not be at all obvious from just looking at the port file...

Probably the only way is to wait for the bug reports once 12.3 is out ...

>
> G
>
> Sent from my iPhone
>
>> On 19 Feb 2022, at 17:26, Christopher Jones  wrote:
>>
>> 
>>
>>> On 19 Feb 2022, at 1:58 pm, Gerben Wierda via macports-dev 
>>>  wrote:
>>>
>>> Oof.
>>>
>>> I’m happy to check as soon as 12.3 is out, but I wonder how to check. 
>>> Installing a port is easy enough to do, but how do I find out if a port 
>>> uses it in some arcane way? And if it does, how should one fix.
>>>
>>> I was wondering if a reasonable band-aid would be to have /usr/bin/python 
>>> link to the one from MacPorts when installed, but given Apple’s strategy in 
>>> clamping down, I guess that will not work in the long term, even if it 
>>> might work in the short term. And of course, such a band-at only hides the 
>>> debt that has now been created in the ports so it is a bad idea in other 
>>> senses as well.
>>
>> Terrible idea all round. Don’t do it.
>>
>> Note /usr/bin/python3 is still there (for now). Ports that can use python3 
>> instead could just use this, on the OSes that provide it.
>>
>> Better solution, as it works across more OSes, is to declare a dependency 
>> (build, or lib depending on how python3 is used) on one of the macports 
>> python3 versions and configure the builds to find that directly in ${prefix}.
>>
>> Chris
>>
>>



smime.p7s
Description: S/MIME cryptographic signature

Re: /usr/bin/python will be removed in macOS 12.3!

[Gerben Wierda via macports-dev]

Well, yes, I kind of knew already that it was a terrible idea. Kind of felt 
terrible in the first place (was just checking).

But how does one (a) find out the dependency exists and (b) make sure the 
software finds python from MacPorts?

G

Sent from my iPhone

> On 19 Feb 2022, at 17:26, Christopher Jones  wrote:
> 
> 
> 
>> On 19 Feb 2022, at 1:58 pm, Gerben Wierda via macports-dev 
>>  wrote:
>> 
>> Oof. 
>> 
>> I’m happy to check as soon as 12.3 is out, but I wonder how to check. 
>> Installing a port is easy enough to do, but how do I find out if a port uses 
>> it in some arcane way? And if it does, how should one fix.
>> 
>> I was wondering if a reasonable band-aid would be to have /usr/bin/python 
>> link to the one from MacPorts when installed, but given Apple’s strategy in 
>> clamping down, I guess that will not work in the long term, even if it might 
>> work in the short term. And of course, such a band-at only hides the debt 
>> that has now been created in the ports so it is a bad idea in other senses 
>> as well.
> 
> Terrible idea all round. Don’t do it.
> 
> Note /usr/bin/python3 is still there (for now). Ports that can use python3 
> instead could just use this, on the OSes that provide it.
> 
> Better solution, as it works across more OSes, is to declare a dependency 
> (build, or lib depending on how python3 is used) on one of the macports 
> python3 versions and configure the builds to find that directly in ${prefix}.
> 
> Chris
> 
> 

Re: /usr/bin/python will be removed in macOS 12.3!

[Christopher Jones]

> On 19 Feb 2022, at 1:58 pm, Gerben Wierda via macports-dev 
>  wrote:
>
> Oof.
>
> I’m happy to check as soon as 12.3 is out, but I wonder how to check. 
> Installing a port is easy enough to do, but how do I find out if a port uses 
> it in some arcane way? And if it does, how should one fix.
>
> I was wondering if a reasonable band-aid would be to have /usr/bin/python 
> link to the one from MacPorts when installed, but given Apple’s strategy in 
> clamping down, I guess that will not work in the long term, even if it might 
> work in the short term. And of course, such a band-at only hides the debt 
> that has now been created in the ports so it is a bad idea in other senses as 
> well.

Terrible idea all round. Don’t do it.

Note /usr/bin/python3 is still there (for now). Ports that can use python3 
instead could just use this, on the OSes that provide it.

Better solution, as it works across more OSes, is to declare a dependency 
(build, or lib depending on how python3 is used) on one of the macports python3 
versions and configure the builds to find that directly in ${prefix}.

Chris




smime.p7s
Description: S/MIME cryptographic signature

Re: /usr/bin/python will be removed in macOS 12.3!

[Gerben Wierda via macports-dev]

Oof. 

I’m happy to check as soon as 12.3 is out, but I wonder how to check. 
Installing a port is easy enough to do, but how do I find out if a port uses it 
in some arcane way? And if it does, how should one fix.

I was wondering if a reasonable band-aid would be to have /usr/bin/python link 
to the one from MacPorts when installed, but given Apple’s strategy in clamping 
down, I guess that will not work in the long term, even if it might work in the 
short term. And of course, such a band-at only hides the debt that has now been 
created in the ports so it is a bad idea in other senses as well.

Gerben Wierda (LinkedIn )
R IT Strategy  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

/usr/bin/python will be removed in macOS 12.3!

[Ryan Schmidt]

It has been announced that /usr/bin/python will be removed in macOS 12.3, of 
which a beta is already out.

If you have ports that use /usr/bin/python, please ensure that at minimum they 
are switched to use MacPorts python27 on macOS 12 and later. Better yet, see if 
you can switch them to use a MacPorts python3x, since python27 is EOL.