Am 14.03.2018 um 08:49 schrieb Pjotr Prins:
> On Tue, Mar 13, 2018 at 11:02:03PM +0100, Hartmut Goebel wrote:
>> Am 13.03.2018 um 22:44 schrieb Pjotr Prins:
>>> Another problem is that it does not cover special cases where, for
>>> example you compile Python with SSL and without. You don't want the
Hello,
Ricardo Wurmus skribis:
> The problem might be that we are using PYTHONPATH at all. On other
> distributions this is usually not required and thus doesn’t cause any
> problems.
It’s not required because Python modules live at a fixed location, no?
How does pip deal with that? I suppos
On Wed, Mar 14, 2018 at 10:04:21AM +0100, Hartmut Goebel wrote:
> Hi Pjotr,
>
> no offense meant, but I have the impression you did not read my analysis
> and proposals, did you?
No offense taken. I did and do read them, but the analysis is not
exactly accessible for my small brain, especially wh
Ludovic Courtès writes:
> I may well have missed something (sorry about that!), but what are “the
> problems related to how Guix is using PYTHONPATH”?
>
> My first reaction is that Guix is not doing anything special with
> PYTHONPATH, and only defining it as documented by upstream.
The problem
Hartmut Goebel skribis:
> Am 13.03.2018 um 22:23 schrieb Ludovic Courtès:
>> I may well have missed something (sorry about that!), but what are “the
>> problems related to how Guix is using PYTHONPATH”?
>
> In short:
>
> We are using PYTHONPATH for something it is not meant for: PYTHONPATH is
> N
Hi Pjotr,
no offense meant, but I have the impression you did not read my analysis
and proposals, did you?
> I propose we patch the interpreter to tell about the Guix paths. It
> probably only needs to be done in one place. They should go after the
> PYTHONPATH as it is done by Python itself, lik
On Tue, Mar 13, 2018 at 11:02:03PM +0100, Hartmut Goebel wrote:
> Am 13.03.2018 um 22:44 schrieb Pjotr Prins:
> > Another problem is that it does not cover special cases where, for
> > example you compile Python with SSL and without. You don't want them
> > to share user installed libs.
>
> Upstre
On Tue, Mar 13, 2018 at 10:23:08PM +0100, Ludovic Courtès wrote:
> > Preliminary Proposal
> > ===
> >
> > To be able to install different minor versions of Python in the same
> > profile, any environment variable should contain the minor version, too.
> > E.g. …-3.5.
>
> If you
Am 13.03.2018 um 22:44 schrieb Pjotr Prins:
> Another problem is that it does not cover special cases where, for
> example you compile Python with SSL and without. You don't want them
> to share user installed libs.
Upstream does not handle this case, so I do not see a need to handle
this in guix.
Am 13.03.2018 um 22:23 schrieb Ludovic Courtès:
>> Preliminary Proposal
>> ===
>>
>> To be able to install different minor versions of Python in the same
>> profile, any environment variable should contain the minor version, too.
>> E.g. …-3.5.
> If you’re suggesting to have a ‘
Am 13.03.2018 um 22:23 schrieb Ludovic Courtès:
> I may well have missed something (sorry about that!), but what are “the
> problems related to how Guix is using PYTHONPATH”?
In short:
We are using PYTHONPATH for something it is not meant for: PYTHONPATH is
NOT intended (by upstream) for adding s
Hello,
Hartmut Goebel skribis:
> Result
> ==
>
> We can avoid all of the problems related to how Guix is using PYTHONPATH
> quite simple. This will work for virtual environments, too.
I may well have missed something (sorry about that!), but what are “the
problems related to how Guix is
12 matches
Mail list logo
