bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2020-04-20 Thread Arun Isaac
Hi, > Have you been able to figure out why some of the items differ in the > two lists? The two lists are the same if `guix build' is invoked with the `--no-grafts' flag. I don't understand grafts very well and am not sure how that can be fixed. Any ideas? See different output below with and wi

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2019-02-07 Thread Ricardo Wurmus
Arun Isaac writes: >> + ;; TODO: Something like this: >> + ;; (disallowed-references native-inputs) > > What is this part for? This is to ensure that no references to any native input are retained in the output. (Think of it as an assertion that is ch

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2017-04-04 Thread Arun Isaac
> How does it look? I tried your patch. But native-inputs are still there in the wrapped PYTHONPATH. I printed out the results from various steps from the wrap phase. They are as follows: `build-time-inputs' is ("/gnu/store/5wbi6vsi12bmpzygwhys3c0cc6sjdw40-python-beautifulsoup4-4.5.3" "/gnu/sto

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2017-03-30 Thread Arun Isaac
> “Build-side” modules, which typically live in (guix build …), should not > depend on “host-side” modules such as (guix packages). That’s because > if we did that, we’d effectively end up importing all of Guix on the > build side, but then we’d also have to serialize data structures such as > pa

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2017-03-30 Thread Ludovic Courtès
Hello, Arun Isaac skribis: > I'm working on fixing this bug. I have modified > guix/build/python-build-system.scm for the same. In particular, I have > added #:use-module (guix packages) because I need the functions > `package-name' and `package-transitive-target-inputs'. But, when I try > build

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2017-03-29 Thread Arun Isaac
I'm working on fixing this bug. I have modified guix/build/python-build-system.scm for the same. In particular, I have added #:use-module (guix packages) because I need the functions `package-name' and `package-transitive-target-inputs'. But, when I try building any python-build-system package wit

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2016-12-26 Thread Leo Famulari
On Tue, Dec 20, 2016 at 03:00:50PM +0100, Ludovic Courtès wrote: > Marius Bakke skribis: > > > The 'wrap' phase of 'python-build-system' adds native-inputs to > > PYTHONPATH of the wrapped programs. This causes unnecessary runtime > > dependencies and may create problems when cross-compiling. > >

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2016-12-20 Thread Ludovic Courtès
Marius Bakke skribis: > The 'wrap' phase of 'python-build-system' adds native-inputs to > PYTHONPATH of the wrapped programs. This causes unnecessary runtime > dependencies and may create problems when cross-compiling. > > Given that all python dependencies are now supposed to be propagated, > pe

bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

2016-12-19 Thread Marius Bakke
The 'wrap' phase of 'python-build-system' adds native-inputs to PYTHONPATH of the wrapped programs. This causes unnecessary runtime dependencies and may create problems when cross-compiling. Given that all python dependencies are now supposed to be propagated, perhaps we can simply remove the wra