From mboxrd@z Thu Jan 1 00:00:00 1970 From: Amirouche Boubekki Subject: Re: Call for testing : guix-tox, a version of tox that uses "guix environment". Date: Fri, 10 Jul 2015 08:24:52 +0200 Message-ID: References: <559F15F2.4080206@gmail.com> <87oajkwsl7.fsf@earlgrey.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49706) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZDRk4-0002XP-U4 for guix-devel@gnu.org; Fri, 10 Jul 2015 02:25:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZDRk3-00047j-UE for guix-devel@gnu.org; Fri, 10 Jul 2015 02:25:00 -0400 In-Reply-To: <87oajkwsl7.fsf@earlgrey.lan> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Christopher Allan Webber Cc: guix-devel , guix-devel-bounces+amirouche=hypermove.net@gnu.org On 2015-07-10 03:38, Christopher Allan Webber wrote: > 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. This is great! I'll have a look at it this week end. >> I intend to propose a 20 minute talk about >> guix-tox at the next PyConFR. Nice! > This is great! I've also been very interested in "guix environment" as > a universal virtualenv. Replacing tox is an excellent example/usage! I wondering whether it is possible to use the same recipe for `guix environment` and `guix container`. The idea behind that is that one can use environment for dev and container for deployment.