From: Ricardo Wurmus <rekado@elephly.net>
To: Fredrik Salomonsson <plattfot@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: no binary for interpreter `python' found in $PATH
Date: Sat, 30 Oct 2021 21:35:40 +0000 [thread overview]
Message-ID: <87ee82w5wj.fsf@elephly.net> (raw)
In-Reply-To: <875ytemddm.fsf@posteo.net>
Hi Fredrik,
> (inputs `(("python" ,python)
[…]
> patch-shebang:
> /gnu/store/ddqy6n4br1snnv57cxybdmycgyc2h01f-picmover-1.2.4/bin/picmover:
> warning: no binary for interpreter `python' found in $PATH
[…]
> I've probably missed something obvious in my package definition
> but I
> cannot see what. Shouldn't the inputs field add python to the
> $PATH?
> Does anyone know what I'm missing?
The “python” package only provides the “python3” executable, not
“python”. The “python-wrapper” package is just like the “python”
package, except that it adds the “python” executable that upstream
does not include in the default build of Python.
--
Ricardo
next prev parent reply other threads:[~2021-10-30 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 21:06 no binary for interpreter `python' found in $PATH Fredrik Salomonsson
2021-10-30 21:35 ` Ricardo Wurmus [this message]
2021-10-30 22:57 ` Fredrik Salomonsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ee82w5wj.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=plattfot@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).