Federico Beffa <be...@ieee.org> skribis: > On Sun, Dec 14, 2014 at 9:28 PM, Ludovic Courtès <l...@gnu.org> wrote:
[...] >> Is PACKAGE.pth a common convention? I mean, does Python (or >> setuptools?) actually use files called PYTHON.pth? > > Yes, the basename of path configuration files with extension .pth does > not matter. The site module will load them all. Setuptools, on top of > easy-install.pth, installs a site.py file. This program adds (with > site.addsitedir) all directories in PYTHONPATH to the list of > directories to be processed by the site module. > > https://docs.python.org/2/library/site.html > > Before writing the path I had conflicts, e.g., between matplotlib and > cairocffi resulting in import failures. After the patch they work > nicely together. > > Using NAME.pth instead of easy-install.pth should guarantee that no > package configuration file collisions occurs between different > packages installed with setuptools, nor between two versions of the > same library. OK, thanks for the explanation. > From d32c6b5b51c4d61a2aef7467705073dafc1087d5 Mon Sep 17 00:00:00 2001 > From: Federico Beffa <be...@fbengineering.ch> > Date: Sat, 13 Dec 2014 22:19:08 +0100 > Subject: [PATCH 1/4] build/python-build-system: Fix easy-install.pth > collisions. > > * guix/build/python-build-system.scm (rename-pth-file): New rename-pth-file > phase and corresponding function. Perfect, thanks! Ludo’.
