[Top][All Lists]

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

Re: Python applications that are also libraries

From: Hartmut Goebel
Subject: Re: Python applications that are also libraries
Date: Thu, 5 Apr 2018 09:05:53 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

Am 04.04.2018 um 22:13 schrieb Ricardo Wurmus:
If this is a "pure" application, I'd install it with*out* propagated
inputs. This might not be easy to determine, though.
It is both.  It is often used just as an application, but the procedures
that make up the application are just as often used in an interactive
Python session or as a library.

So I'm afraid, we need to install it with propagated inputs.

Stimulated by your question I rethought whether we might come around propagated inputs, and I did not find a solution. There must only be one version of a library in each profile, otherwise we'd get conflicts. We could provide our own implementation of (or to avoid *propagating*, but this would not avoid the *conflicts* but only hide the cause of the conflicts and make them hard to find (as we already discusses a year or two ago).
This is about wrapping (or not) using virtual envs.  I don’t really see
how this relates to this problem, but maybe I’m missing something

Sorry for the confusion, this link shouldn't have been there. I had pasted it in since I thought it is related and I'm going to refer to is, but it is not.

Hartmut Goebel

| Hartmut Goebel          | address@hidden               |
| | compilers which you thought are impossible |

reply via email to

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