[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#27271: Avoiding ‘propagated-inputs’ for Python dependencies

From: Ludovic Courtès
Subject: bug#27271: Avoiding ‘propagated-inputs’ for Python dependencies
Date: Sat, 10 Jun 2017 15:39:56 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)


(+Cc: Hartmut.)

Marius Bakke <address@hidden> skribis:

> Ludovic Courtès <address@hidden> writes:


>> Perhaps we could modify ‘sys.path’ from the top of ‘’ file to
>> get something similar to RUNPATH.  I’m not sure if there are any
>> downsides or gotchas.  Thoughts?
> Python actually has a native mechanism for setting up package-specific
> search paths:
> In short, it looks for a file "package.pth" where additional search
> paths can be specified (other sys.path manipulations are allowed too).

Looks good at first sight.

> I asked Hartmut about this during the python-build-system refactoring,
> and the counter-argument was that if package A and B depends on
> different versions of package C, odd failures could occur. I'm not
> convinced propagation sidesteps this problem, however:

I think we’re in trouble anyway if multiple versions of a package end up
in the dependency graph because that’s not something Python supports
(the same is probably true for most languages, with the notable
exception of Node.)

Perhaps it would be worth making a PoC to see what happens with a small
set of packages?

(I’m not volunteering though, just trying to tweak others into doing
it.  :-))


reply via email to

[Prev in Thread] Current Thread [Next in Thread]