From: Simon Tournier <zimon.toutoune@gmail.com>
To: 62448@debbugs.gnu.org, dev@jpoiret.xyz, skyvine@protonmail.com
Subject: bug#62448: [PATCH] doc: Note that `guix shell` should contain base language packages.
Date: Wed, 12 Apr 2023 13:07:33 +0200 [thread overview]
Message-ID: <87y1mxgxze.fsf@gmail.com> (raw)
In-Reply-To: <e0ff6805cf50096274d9fb666ef361b2cbf3a4e8.1680208930.git.dev@jpoiret.xyz>
Hi,
On jeu., 30 mars 2023 at 22:42, Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> +Note that it is necessary to include the main @code{python} package in
> +this command even if it is already installed into your environment. This
> +is so that the shell environment knows to set @env{PYTHONPATH} and other
> +related variables. The shell environment cannot check the previously
> +installed environment, because then it would be non-deterministic. This
> +is true for most libraries: their corresponding language package should
> +be included in the shell invocation.
Nitpick: Missing double space for sentences.
Otherwise, LGTM.
Cheers,
simon
next prev parent reply other threads:[~2023-04-12 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 19:10 bug#62448: Inconsistent guile enviornment from guix shell Skyler via Bug reports for GNU Guix
2023-03-29 21:23 ` Skyler via Bug reports for GNU Guix
2023-03-30 20:24 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-30 20:42 ` bug#62448: [PATCH] doc: Note that `guix shell` should contain base language packages Josselin Poiret via Bug reports for GNU Guix
2023-04-11 22:57 ` Skyler via Bug reports for GNU Guix
2023-04-12 8:35 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-12 12:43 ` Maxim Cournoyer
2023-04-13 19:53 ` Skyler via Bug reports for GNU Guix
2023-04-12 11:07 ` Simon Tournier [this message]
2023-08-25 16:30 ` Josselin Poiret via Bug reports for GNU Guix
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=87y1mxgxze.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=62448@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=skyvine@protonmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).