Hi,
On Thu, 25 Nov 2021 at 00:39, zimoun wrote:
> On Tue, 23 Jan 2018 at 13:00, Ricardo Wurmus wrote:
>
>>> When a python module needs to load a dynamic shared object, it looks in the
>>> path provided by *LD_LIBRARY_PATH*(1), but guix doesn't modify this
>>> environment
>>> variable to export t
Hi,
On Tue, 23 Jan 2018 at 13:00, Ricardo Wurmus wrote:
>> When a python module needs to load a dynamic shared object, it looks in the
>> path provided by *LD_LIBRARY_PATH*(1), but guix doesn't modify this
>> environment
>> variable to export the needed path for python.
>
> We cannot set this e
Hi,
> When a python module needs to load a dynamic shared object, it looks in the
> path provided by *LD_LIBRARY_PATH*(1), but guix doesn't modify this
> environment
> variable to export the needed path for python.
We cannot set this environment variable by default lest we break other
packages
Hi,
Fis Trivial skribis:
> In my case, it's lightgbm (installed by pip), needs libgomp.so from gcc:lib
> for
> openmp support. Here is the backtrace:
>
> Traceback (most recent call last):
> File "ex1.py", line 5, in
> import lightgbm as lgb
> File
> "/home/fis/Workspace/tianchi/medic
>
> In general, though, I recommend using Guix for package management and
> development instead of virtualenv and pip.
>
I understand the importance for having a self-contained dependency graph.
After trying guix a few months, I came to realize that, at the a theoretical
level, the environment v
When a python module needs to load a dynamic shared object, it looks in the
path provided by *LD_LIBRARY_PATH*(1), but guix doesn't modify this environment
variable to export the needed path for python.
* Backtrace
In my case, it's lightgbm (installed by pip), needs libgomp.so from gcc:lib for
op
