[MacPorts] #65478: glib2, glib2-devel, glib2-upstream: only has a build dependency on python?!

[MacPorts]

#65478: glib2, glib2-devel, glib2-upstream: only has a build dependency on python?!
-------------------------------------------------+---------------------
  Reporter:  RJVB                                |      Owner:  mascguy
      Type:  enhancement                         |     Status:  closed
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:
Resolution:  fixed                               |   Keywords:
      Port:  glib2, glib2-devel, glib2-upstream  |
-------------------------------------------------+---------------------

Comment (by mascguy):

 Replying to [comment:9 RJVB]:
 > FWIW, the reason I'm triggering on this is that I have the impression
 I'm flooding my install with python installations, without (AFAIK) a good
 way to update an entire python x.y "universe" (including all add-on
 packages) to a newer version. And with the experience that newer versions
 keep getting a bit slower than the previous one. This is noticeable going
 from 3.7 to 3.9 for instance, and I'm certain I noticed going to 3.7 too.
 Python 2.7 remains a lot faster which is a perfect reason for me to keep
 using it for code that doesn't need the latest version (for features or
 security considerations).

 Based on the Python release notes, 3rd-party articles, etc, each Python
 3.x release has included performance improvements. And while there may be
 some past occasions when there was a minor performance reduction - and
 that doesn't seem common - those were then addressed in a subsequent
 release.

 Meanwhile, Python 3.11 is slated to include significant performance
 increases, vis-a-vis 3.10:

 https://towardsdatascience.com/python-is-about-to-become-64-faster-
 python-3-10-vs-python-3-11-benchmark-3a6abcc25b90

 Ultimately I'll defer to Josh and others for a more definitive answer. But
 it's clear that the project - and the industry - has rallied around
 improving performance in each major Python release. And that's a great
 thing!

 Otherwise, this is somewhat of a pointless discussion: If a given open-
 source project requires Python for build and/or runtime support, then it
 is what is is.

 The best we can do is validate dependencies for a given port, and remove
 things when they aren't needed. For example, Josh recently noticed that
 Python and Perl aren't needed at build time for `evolution-data-server`,
 per issue:65409. And that was addressed.

 I've also been more cognizant of that in recent months, with much more
 scrutiny on configure output... combined with extensive use of trace mode.

 But at the end of the day, let me pose this question: Is it possible that
 your perception of Python 3.x being slower with each new release, is
 simply that... perception? Something to consider.

-- 
Ticket URL: <https://trac.macports.org/ticket/65478#comment:10>
MacPorts <https://www.macports.org/>
Ports system for macOS