Re: [Nix-dev] Python: getting rid of PYTHONPATH in Nixpkgs

You can do something like: (python3.withPackages (ps: [ ps.mrbob ])).override(foo: {ignoreCollisions = true;}) On Wed, Nov 2, 2016 at 11:33 AM, Thomas Hunger wrote: > I played with `withPackages` and it's rather nice. The only problem I had > was "collision between A and B"

Re: [Nix-dev] Python: getting rid of PYTHONPATH in Nixpkgs

I played with `withPackages` and it's rather nice. The only problem I had was "collision between A and B" style errors. Is there any plan to allow for collisions? On 2 November 2016 at 06:05, Dmitry Kalinkin wrote: > > > On 01 Nov 2016, at 11:56, Freddy Rietdijk

Re: [Nix-dev] Python: getting rid of PYTHONPATH in Nixpkgs

> On 01 Nov 2016, at 11:56, Freddy Rietdijk wrote: > > > > To solve 2) you could also make a wrapper that combines selected outputs of > > the multiple output package without python itself. I think, this is what > > texlive does. That way all the burden of wrapping

Re: [Nix-dev] Python: getting rid of PYTHONPATH in Nixpkgs

I'm +1 on this because I encountered lots of problems with PYTHONPATH, especially for programs that have their own module loading logic (e.g. gunicorn, some Django code). I don't know what new problems this change will introduce (other than what you mentioned) but since this is closer to how

Re: [Nix-dev] Python: getting rid of PYTHONPATH in Nixpkgs

> On 01 Nov 2016, at 06:22, Freddy Rietdijk wrote: > > Hi, > > Currently we use PYTHONPATH a lot in Nixpkgs to let applications and the > interpreter find Python modules. This typically works fine, but there are > problems with this method and so I would like to get

[Nix-dev] Python: getting rid of PYTHONPATH in Nixpkgs

Hi, Currently we use PYTHONPATH a lot in Nixpkgs to let applications and the interpreter find Python modules. This typically works fine, but there are problems with this method and so I would like to get rid of it and use only