From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Call for testing : guix-tox, a version of tox that uses "guix environment".
Date: Thu, 09 Jul 2015 20:38:53 -0500 [thread overview]
Message-ID: <87oajkwsl7.fsf@earlgrey.lan> (raw)
In-Reply-To: <559F15F2.4080206@gmail.com>
Cyril Roelandt writes:
> Hey!
>
> Those of who you write Python code probably know tox[1], a tool used to
> manage tests/builds for Python. It uses virtualenv[2], which allows
> developers to create "isolated" environments and install packages
> without polluting their systems.
>
> I hacked tox to replace virtualenv with "guix environment". The code is
> available at https://git.framasoft.org/Steap/guix-tox , in the
> "guix-tox" branch (the master branch is just a mirror of tox). Note that
> I will probably use "git push -f" on this branch :) I explained the
> details in README.rst.
>
> If there are Python developers on this list, I would love to know what
> they think about this. I intend to propose a 20 minute talk about
> guix-tox at the next PyConFR.
>
> print("Happy Hacking!")
>
> Cyril.
>
>
> [1] https://bitbucket.org/hpk42/tox
> [2] https://virtualenv.pypa.io/en/latest/
This is great! I've also been very interested in "guix environment" as
a universal virtualenv. Replacing tox is an excellent example/usage!
Main challenge right now is getting enough python packages (not to
mention all those javascript dependencies...) packaged to be usable for
many things tox is used for. But that's a more general problem right
now! :)
Hack on,
- Chris
next prev parent reply other threads:[~2015-07-10 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 0:46 Call for testing : guix-tox, a version of tox that uses "guix environment" Cyril Roelandt
2015-07-10 1:38 ` Christopher Allan Webber [this message]
2015-07-10 6:24 ` Amirouche Boubekki
2015-07-10 17:36 ` 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=87oajkwsl7.fsf@earlgrey.lan \
--to=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
--cc=tipecaml@gmail.com \
/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).