From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Marek Felšöci" <marek@felsoci.sk>
Cc: 53258@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#53258: Python unable to find modules within a Singularity container created with guix pack
Date: Sat, 05 Feb 2022 23:28:39 +0100 [thread overview]
Message-ID: <87v8xt3q3s.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87v8xumk41.fsf@gnu.org>
Hello everyone,
After the IRC investigation, it turned out the use of abspath in
Lib/site.py was in fact the culprit. Replacing all its uses with
realpath and doing `./pre-inst-env guix pack -RR python python-numpy -S
/bin=bin -S /etc=etc` did in fact resolve the issue!
I've raised the issue upstream at [1]. The fix itself is pretty simple,
but it's theoretically a breaking change, so we'll see how Python
maintainers want to move forward with it. We could backport this fix
for the next core-updates cycle, whether or not it gets accepted
upstream, and we will also need to modify sitecustomize.py as well to
call os.path.realpath on python_site.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-02-05 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:20 bug#53258: Python unable to find modules within a Singularity container created with guix pack Marek Felšöci
2022-01-14 17:45 ` Ludovic Courtès
2022-02-04 20:50 ` Ludovic Courtès
2022-02-05 22:28 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2022-02-05 22:30 ` Josselin Poiret via Bug reports for GNU Guix
2022-03-07 8:25 ` Ludovic Courtès
2023-02-02 14:44 ` Josselin Poiret via Bug reports for GNU Guix
2023-02-02 15:40 ` Maxim Cournoyer
2023-02-06 17:34 ` Simon Tournier
2024-01-04 12:35 ` Konrad Hinsen
2024-01-04 13:01 ` Konrad Hinsen
2024-01-05 15:23 ` Konrad Hinsen
2024-01-21 18:31 ` Maxim Cournoyer
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=87v8xt3q3s.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=53258@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@gnu.org \
--cc=marek@felsoci.sk \
--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).