unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Python and propagation
Date: Wed, 24 Feb 2016 23:09:38 +0100	[thread overview]
Message-ID: <871t81dal9.fsf@gnu.org> (raw)
In-Reply-To: <idja8my5hur.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Thu, 18 Feb 2016 13:21:48 +0100")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> As a Python library it depends on numpy, and thus propagates numpy as
> it is customary in Guix.  This is necessary because Python libraries
> do not have a RUNPATH feature

Does the newfangled “wheels” thing support something like a RUNPATH?

> 1) print a warning when a collision is expected to happen, not when a
> collision has happened.

Sounds like a good idea, indeed.

The file-by-file warnings may still be useful in other cases though, for
example when different packages genuinely provide same-named files.

> 2) avoid PYTHONPATH, patch all Python files invasively!

Sounds like an interesting option.  :-)  There are open issues though,
as you and others note (‘import’ can overridden!).

(This reminds me that, since Guile 2.2 uses ELF, it should be made to
honor RUNPATH!)

Ludo’.

  parent reply	other threads:[~2016-02-24 22:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 12:21 Python and propagation Ricardo Wurmus
2016-02-18 14:28 ` Andreas Enge
2016-02-18 14:45   ` Ricardo Wurmus
2016-02-18 15:03     ` Andreas Enge
2016-02-18 14:56   ` Jookia
2016-02-18 15:03 ` 宋文武
2016-02-19  1:26   ` 宋文武
2016-02-18 22:38 ` Christopher Allan Webber
2016-02-25 10:24   ` Ricardo Wurmus
2016-02-25 16:13     ` Christopher Allan Webber
2016-02-24 22:09 ` Ludovic Courtès [this message]
2016-04-04 22:08 ` Danny Milosavljevic
  -- strict thread matches above, loose matches on Subject: below --
2016-02-22 17:08 Federico Beffa

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=871t81dal9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).