[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 RJVB):

 Nope, I've measured it, with actual usually simple apps of the sort that
 are often written in Python. I know of Python's background so I'm willing
 to believe that series, complex apps are seeing performance increases.
 Python is an interpreted language and it's almost inevitable that it gets
 more sluggish when more features get added, if not only in the initial
 startup time, which can be a significant part of the total execution time
 of trivial tasks. For instance, try various `time python3.x /opt/local/bin
 /youtube-dl --help` (a few times to get a stable result); I see a
 continuous increase in execution time from 3.4 to 3.6; 3.7 is a bit slower
 than 3.4 but faster than 3.5 and 3.9 is maybe a hair faster tham 3.6 . I
 don't have 3.10 on the machine I'm on.

 I think it would be a great idea if the Python PG provided a way to add
 python variants to ports like this that don't extend Python and can't or
 don't want to use the system-provided version. Or make a MacPorts "system
 python" for this purpose, one that that installs into a non-versioned
 location, or uses a non-versioned site-packages location and that you can
 keep up to date as you deem fit without leaving a clutter of unused python
 ports around.
 Of course there could also have been a single Python3 port which would now
 be at 3.10.x . I see 3.10 still should work with very old OS X versions,
 and have there ever been add-ons that didn't work with the newest Python 3
 version?


 PS: You can see a similar evolution of performance with clang; it's still
 being tauted as a lot faster than GCC but that is no longer the case at
 all.

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