unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add python-contextlib2
Date: Thu, 26 Nov 2015 14:44:38 +0100	[thread overview]
Message-ID: <87mvu0x4c9.fsf@gnu.org> (raw)
In-Reply-To: <CAEKzfHmniiQWKkFumA2FY_gSJAOKu2yaHg+_sEzNgvaFbmeBrA@mail.gmail.com> (Chris Marusich's message of "Sat, 21 Nov 2015 13:28:41 -0800")

Hi!

Sorry for the delay.

Chris Marusich <cmmarusich@gmail.com> skribis:

> However, there is one curiosity. I've noticed that when I run
> "./pre-inst-env guix environment python2-contextlib2", the PYTHONPATH
> is configured to allow importation of contextlib2 from the
> $profile/lib/python3.4/site-packages directory tree, rather than
> $profile/lib/python2.7/site-packages. When I run python in this
> environment, I get a Python 2.7 interpreter.

The interpreter you get here is probably one that was already in PATH,
because the command above lacks --pure.

If you want to be sure, use:

  ./pre-inst-env guix environment --pure \
        python2-contextlib python-2 -- python

(Even better: --container instead of --pure.)

Can you confirm?

> I'm also curious: why does the "(#:phases" part need to be
> quasi-quoted with the backtick symbol "`"?

The #:phases part specified build code (info "(guix) G-Expressions").
That code is quoted because we don’t want to evaluate it; we merely want
to pass the code itself for future execution in the build environment.

Does that make sense?

Thanks,
Ludo’.

  reply	other threads:[~2015-11-26 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  8:31 [PATCH] gnu: Add python-contextlib2 Chris Marusich
2015-11-18  8:46 ` Andreas Enge
2015-11-18  8:46 ` Chris Marusich
2015-11-18 12:55 ` Ben Woodcroft
2015-11-21 21:28   ` Chris Marusich
2015-11-26 13:44     ` Ludovic Courtès [this message]
2015-12-01  8:22       ` Chris Marusich
2015-12-06 21:49         ` Ludovic Courtès
2015-12-08  5:14           ` Chris Marusich
2015-12-13 23:16             ` Ludovic Courtès
2015-12-14  2:15               ` Chris Marusich
2015-12-14  8:44                 ` Ludovic Courtès

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=87mvu0x4c9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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.
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).