unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "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: Fri, 04 Feb 2022 21:50:54 +0100	[thread overview]
Message-ID: <87v8xumk41.fsf@gnu.org> (raw)
In-Reply-To: <87wnj22ouh.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 14 Jan 2022 18:45:26 +0100")

Hello!

Ludovic Courtès <ludovic.courtes@inria.fr> skribis:

>>From Marek’s message, it would seem that somewhere file names are
> constructed by appending “..”.  Given Unix’s weird dot-dot semantics,
> relative symlinks could be interfering:

Some news!  Here’s a recap of the IRC discussion earlier today:
‘sys.prefix’ looks like
/tmp/pack2/bin/../../zmv1alp7dzjd6hkc7l6fjz817n2mfzzw-python-3.9.9R.

‘sys.normpath’ does lexical dot-dot resolution (which is incorrect on
POSIX):

  https://docs.python.org/3.11/library/os.path.html#os.path.normpath

Thus, passing the prefix above to ‘sys.normpath’ leads “pack2” to be
erased.

Josselin mentioned “path_hooks” as a possible solution, though I’m not
sure what that means; could you explain?  :-)

Thanks!

Ludo’.




  reply	other threads:[~2022-02-04 21:12 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 [this message]
2022-02-05 22:28     ` Josselin Poiret via Bug reports for GNU Guix
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=87v8xumk41.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=53258@debbugs.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).