From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Python conflicts. Date: Tue, 30 Jun 2015 10:04:47 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56554) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9qXL-00007X-Km for guix-devel@gnu.org; Tue, 30 Jun 2015 04:05:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9qXI-0001Sd-EJ for guix-devel@gnu.org; Tue, 30 Jun 2015 04:04:59 -0400 Received: from venus.bbbm.mdc-berlin.de ([141.80.25.30]:33313) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9qXI-0001SF-5N for guix-devel@gnu.org; Tue, 30 Jun 2015 04:04:56 -0400 In-Reply-To: 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: Federico Beffa Cc: Guix-devel Federico Beffa writes: >> 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. > > 'site.py[c]' is installed and used by 'setuptools' based > programs/libraries. The purpose of the file is to add sub-directories to > PYTHONPATH. If you remove the file, libraries configured with setuptools > will not work anymore, unless you do the work done by 'site.py' in > another way. > > https://pythonhosted.org/setuptools/easy_install.html Currently, we have *many* packages providing this file. My goal is to avoid the confusing and verbose conflict warnings by only providing it once. Is it feasible to let our "python" package install "site.py" once and remove the file from all other packages? Right now we only have one of these many files installed at a time anyway, so I assume they all have the same contents. The "python" package creates lib/python${version}/site-packages/ with a README already in which "site.py" is mentioned. I suggest we let "python" install "site.py" once and for all. Obviously, we cannot *just* remove it and expect things to continue working. ~~ Ricardo