[MacPorts] #51691: py27-pymvpa: unable to execute 'swig': No such file or directory
MacPorts
noreply at macports.org
Mon Aug 12 22:20:43 UTC 2019
#51691: py27-pymvpa: unable to execute 'swig': No such file or directory
-------------------------+----------------------
Reporter: andytsai@… | Owner: stromnov
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: fixed | Keywords:
Port: py-pymvpa |
-------------------------+----------------------
Changes (by reneeotten):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"6f39e802189a7ea5ed35dec0407893a52c3d0418/macports-ports"
6f39e802189a7ea5ed35dec0407893a52c3d0418/macports-ports] (master):
{{{
#!ConfigurableCommitTicketReference repository="macports-ports"
revision="6f39e802189a7ea5ed35dec0407893a52c3d0418"
py-pymvpa: install binaries and make them PY3-compatible
Upstream provided setup.py file makes Python code compatible using the
2to3 converstion tool. However, it does not include the files in "bin"
and, therefore, scripts were only installed for py27-pymvpa.
This commits resolves that issue in the pre/post-destroot phases as I
couldn't find a way of accomplishing it by patching the setup.py file...
Also added a note about limited PY3 compatibility (there are indeed more
test failures with py37-mvpa) and upstream's recommendation to use PY27.
Closes: https://trac.macports.org/ticket/51691
}}}
--
Ticket URL: <https://trac.macports.org/ticket/51691#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list