unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Fis Trivial <ybbs.daans@hotmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "30229@debbugs.gnu.org" <30229@debbugs.gnu.org>
Subject: bug#30229: Python modules installed by pip in virtualenv can't find shared objects.
Date: Tue, 23 Jan 2018 13:21:10 +0000	[thread overview]
Message-ID: <MWHPR16MB0063FE6E9AB2B17F44A8B9A692E30@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
In-Reply-To: <87h8rczsx3.fsf@elephly.net>

> 
> 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 variables are not treated as part of the dependency
graph in the Guix world. Dangling environment variables happens, and can not
be solved by installing everything with guix(1).

I really hope that we can come up with some methods to solve these problems
in a systematical way. I will keep reporting bugs caused by environment
variables, hoping that it might be helpful in future development.


[1]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30093

  reply	other threads:[~2018-01-23 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 11:49 bug#30229: Python modules installed by pip in virtualenv can't find shared objects Fis Trivial
2018-01-23 12:00 ` Ricardo Wurmus
2018-01-23 13:21   ` Fis Trivial [this message]
2021-11-24 23:39   ` zimoun
2022-01-13 14:59     ` zimoun
2018-01-24 15:01 ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR16MB0063FE6E9AB2B17F44A8B9A692E30@MWHPR16MB0063.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=30229@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).