[MacPorts] #74285: legacy-support does not work correctly with Python packages

MacPorts noreply at macports.org
Sun Aug 16 00:55:42 UTC 2026


#74285: legacy-support does not work correctly with Python packages
-----------------------------+--------------------
  Reporter:  barracuda156    |      Owner:  (none)
      Type:  defect          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  legacy-support  |    Version:  2.12.5
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+--------------------

Comment (by fhgwright):

 Care to provide a usable example?:
 {{{
 MacPro:macports-ports fw$ port info py-dukpy
 Error: Port py-dukpy not found
 }}}
 If this is from your own MacPorts fork, can you find an example in
 standard MacPorts?

 Note that when Python is built, it captures the options used in its own
 build, and makes that info available to Python programs.  It's common for
 builds of Python C extensions to use these compile/link options for their
 own builds.  If that overrides the injection of the `legacy-support`
 options by the `legacysupport` PG, and that Python version itself didn't
 need `legacy-support`, then this sort of behavior would be expected.

 The description `legacy-support does not work correctly` is almost
 certainly incorrect - a program's failing to build with `legacy-support`
 isn't a failure of the latter.

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


More information about the macports-tickets mailing list