From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Wade Zhang <dochang@gmail.com>, help-guix@gnu.org
Subject: Re: Issue about building python on a foreign distro
Date: Thu, 16 Sep 2021 13:24:48 +0200 [thread overview]
Message-ID: <11db7282-2c97-c4da-8dd8-4c9089934435@crazy-compilers.com> (raw)
In-Reply-To: <CANBNykuUganjSKkvaofcicxhO=itzUtAbLZXLQcpyWO0B4MF=A@mail.gmail.com>
Am 22.08.21 um 13:27 schrieb Wade Zhang:
> Recently I installed Guix on a Debian buster host. I want to install all build
> dependencies by Guix. Since I use pyenv to manage Python versions, I have to
> install Python outside Guix. Now I get stuck during the Python installation.
I never used pyenv, but Python's virtual environments a lot. Lately I
moved on to "direnv" for most projects, as this matches my "directory
based" working style. Maybe you want to give it a try?
A typical ".envrc" file for me looks like this (combining both a guix
profile and a virtual env for developing the current package)
...8<-------
use_guix --load-path=../guix-channel \
-v 1 --keep-failed \
--ad-hoc glibc-utf8-locales python-wrapper python-pip
python-virtualenv \
python-pep-adapter sequoia python-pyyaml python-requests \
python-setuptools python-setuptools-scm python-wheel python-babel \
python-pytest@5.3.5 python-pytest-cov python-pytest-mp \
python-requests-mock python-filelock python-pexpect
layout_python3 --system-site-packages
pip install -e .
path_add PYTHONPATH $PWD
...8<-------
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
prev parent reply other threads:[~2021-09-16 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 11:27 Issue about building python on a foreign distro Wade Zhang
2021-08-23 16:41 ` zimoun
2021-08-23 19:30 ` Wade Zhang
2021-08-25 13:08 ` zimoun
2021-08-29 22:29 ` Wade Zhang
2021-09-16 11:24 ` Hartmut Goebel [this message]
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=11db7282-2c97-c4da-8dd8-4c9089934435@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=dochang@gmail.com \
--cc=help-guix@gnu.org \
/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).