From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Python conflicts. Date: Mon, 29 Jun 2015 14:31:48 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9YEH-0008EL-6N for guix-devel@gnu.org; Mon, 29 Jun 2015 08:32:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9YEB-0002Ja-8h for guix-devel@gnu.org; Mon, 29 Jun 2015 08:32:05 -0400 Received: from sinope.bbbm.mdc-berlin.de ([141.80.25.23]:36639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9YEB-0002J3-0K for guix-devel@gnu.org; Mon, 29 Jun 2015 08:31:59 -0400 Received: from localhost (localhost [127.0.0.1]) by sinope.bbbm.mdc-berlin.de (Postfix) with ESMTP id 62443280868 for ; Mon, 29 Jun 2015 14:31:57 +0200 (CEST) Received: from sinope.bbbm.mdc-berlin.de ([127.0.0.1]) by localhost (sinope.bbbm.mdc-berlin.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2FUMv4b6Llm for ; Mon, 29 Jun 2015 14:31:51 +0200 (CEST) Received: from HTCAONE.mdc-berlin.net (mab.citx.mdc-berlin.de [141.80.36.102]) by sinope.bbbm.mdc-berlin.de (Postfix) with ESMTP for ; Mon, 29 Jun 2015 14:31:51 +0200 (CEST) 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: guix-devel Hi Guix, there are two things related to the installation of Python modules that I would like to see changed; but as I may not understand what side effects the proposed changes might have I'd like to gather some opinions first. 1) Nosetests Installing Python modules that have an input "python-nose" (always?) install "$out/bin/nosetests" and various wrappers around this script. This script is not very useful for a user of the module as it only runs the test suite. As we're often propagating Python module inputs, the installation of one Python module usually results in conflicts with the various versions of "$out/bin/nosetests" that are to be installed into the profile. This makes the nosetests scripts even less useful as an arbitrary version will end up in the profile. I'd like to exclude them from installation in all Python packages, maybe by modifying "python-build-system" such that the files are deleted from the output directory again. What I don't like about using the "python-build-system" for this is that "$out/bin/nosetests" is only created when "python-nose" (or "python2-nose") is a package input. Is there a better way? Can we prevent the creation of the "nosetests" script (and its wrappers), maybe with some flag to setuptools? 2) lib/python$version/site-packages/site.{py,pyc} Another file that frequently causes conflicts is "site.py" (and its compiled cousin). It seems to me that "site.py" doesn't contain any module-specific information and is probably the same for all modules. I would like to change "python-build-system" such that Python modules do not install this file at all. The only problem I see is that the "python" package itself does not come with this file. If it should be provided at all I think that it should come from the "python" package, rather than any of the modules that may or may not be installed. What do you think? ~~ Ricardo