[MacPorts] #69788: byobu @5.133: byobu-config could not import the python snack module (was: byobu @ 5.133 byobu-config could not import the python snack module)
MacPorts
noreply at macports.org
Sat Apr 20 17:13:59 UTC 2024
#69788: byobu @5.133: byobu-config could not import the python snack module
-------------------------+----------------------
Reporter: danielbair | Owner: l2dy
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.9.3
Resolution: | Keywords:
Port: byobu |
-------------------------+----------------------
Changes (by ryandesign):
* keywords: byobu-config =>
Old description:
> When trying to run 'byobu-config' I get, ERROR: Could not import the
> python snack module.
>
> So I attempted to install snack with 'pip install snack' and that failed
> with an error. Then searching for that error lead me to learn that snack
> hasn't been ported to python3 and there is no solution (see
> https://apple.stackexchange.com/questions/423515/byobu-not-working-on-
> new-installation-of-macos).
New description:
When trying to run 'byobu-config' I get,
{{{
ERROR: Could not import the python snack module.
}}}
So I attempted to install snack with 'pip install snack' and that failed
with an error. Then searching for that error lead me to learn that snack
hasn't been ported to python3 and there is no solution (see
https://apple.stackexchange.com/questions/423515/byobu-not-working-on-new-
installation-of-macos).
--
Comment:
Weird: the byobu port doesn't mention that it uses python. But you're
right, the contents of `byobu-config` are just:
{{{#!sh
#!/bin/sh -e
}}}
{{{#!sh
PKG="byobu"
[ -z "${BYOBU_PREFIX}" ] && export BYOBU_PREFIX="/opt/local" || export
BYOBU_PREFIX
. "${BYOBU_PREFIX}/lib/${PKG}/include/common"
${BYOBU_PYTHON} "${BYOBU_PREFIX}/lib/${PKG}/include/config.py"
}}}
So the byobu port should declare a library dependency on whatever newest
version of python it is compatible with and the build process should
ensure that that version of python is used.
You can use `pip` to install modules for your own use in your own user
directories (e.g. in a virtualenv) but shouldn't use it to try to install
things into the system (MacPorts) directories.
--
Ticket URL: <https://trac.macports.org/ticket/69788#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list