From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Anomalies in Python search-path
Date: Mon, 16 Jan 2017 10:23:56 +0100 [thread overview]
Message-ID: <587C912C.9090304@crazy-compilers.com> (raw)
In-Reply-To: <87eg04i0uu.fsf@gmail.com>
Am 15.01.2017 um 20:23 schrieb Maxim Cournoyer:
> 1. Remove the current "python-2.7-site-prefixes" patch.
I'm afraid, we'll still need this patch. Since "native-inputs" will not
be available at build time otherwise. But you way give it a try.
> 2. Apply a new patch to site.py to add "$HOME/.guix-profile"
> as well as "$GUIX_ENVIRONMENT".
I already tried this and unfortunately the test-case "test_site" failed:
The user-site-packages directory was not in sys.path. I had not time for
investigating this.
BTW: I'd not use a patch, but simply "substitute" it in a phase. But
that's a matter of taste.
> 3. Remove the 'native-search-paths' field.
I assume we can remove this. But I do not really understand what
"native-search-paths" *really* does. Ludo?
--
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:[~2017-01-16 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 18:41 [PATCH] Update python-pip to 9.0.1 Maxim Cournoyer
2017-01-09 14:52 ` Ludovic Courtès
2017-01-12 16:44 ` Maxim Cournoyer
2017-01-14 17:43 ` Ludovic Courtès
2017-01-15 17:55 ` Anomalies in Python search-path (was: [PATCH] Update python-pip to 9.0.1) Maxim Cournoyer
2017-01-15 22:10 ` Anomalies in Python search-path Ludovic Courtès
2017-01-16 9:30 ` Hartmut Goebel
2017-01-19 11:48 ` Ludovic Courtès
2017-01-14 21:02 ` Anomalies in Python search-path (was: [PATCH] Update python-pip to 9.0.1) Hartmut Goebel
2017-01-15 19:23 ` Anomalies in Python search-path Maxim Cournoyer
2017-01-16 9:23 ` 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=587C912C.9090304@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.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).