[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/14] Change python-build-system (fixes bug 20765)
From: |
Leo Famulari |
Subject: |
Re: [PATCH 00/14] Change python-build-system (fixes bug 20765) |
Date: |
Sat, 1 Oct 2016 22:27:54 -0400 |
User-agent: |
Mutt/1.7.0 (2016-08-17) |
On Wed, Sep 28, 2016 at 03:58:13PM +0200, Hartmut Goebel wrote:
> this is a patch-series fixing bug 20765.
>
> Bug 20765 is about problems caused by python packages being installed as
> "zipped eggs" (basically these are zip-files).
Thanks for taking this on!
I will read it more thoroughly tomorrow.
I will test a few packages and, if they work, I plan to create a
python-build-system job on Hydra and try building it the entire package
tree (assuming that Hydra has the capacity).
> This series implements what I proposed in
> <http://lists.gnu.org/archive/html/guix-devel/2016-09/msg02021.html>.
>
> A) For python2 include python2-setuptools as a native-input by default.
Do all python-2 packages require setuptools, or just most of them?
> B) Install Python packages using --single-version-externally-managed
Okay.
> C) Strip python-setuptools and python2-setuptools from all native-inputs
> defined in packages.
Hydra will test this :)
> * update Python to 2.7.12 and 3.4.5.
Python 2.7.12 and 3.5.2 are on core-updates. Should I cherry-pick those
changes will testing these patches? Or should they work with the Python
packages that we have on master?
- Re: [PATCH 00/14] Change python-build-system (fixes bug 20765),
Leo Famulari <=