On Mon, Nov 24, 2014 at 10:06 PM, Ludovic Courtès wrote:
> OK. Note that you can also test once it’s private, with
>
> guix build -e '(@@ (gnu packages python) python-numpy-bootstrap)'
>
OK, thanks. Will keep in mind for the future.
> LGTM, please push.
Pushed.Thanks.
Fede
Federico Beffa skribis:
> Please find attached the first step with initial (bootstrap) numpy
> versions. I've tested that the packages build before changing
> "define-public" to "define".
OK. Note that you can also test once it’s private, with
guix build -e '(@@ (gnu packages python) python
On Sat, Nov 22, 2014 at 6:21 PM, Ludovic Courtès wrote:
> Sounds like a good plan.
Please find attached the first step with initial (bootstrap) numpy
versions. I've tested that the packages build before changing
"define-public" to "define".
Regards,
Fede
From 9be3873522b2c4b642a467e421bd8684068
Federico Beffa skribis:
> In the mean time version 1.9.1 was released. With this release I
> noticed that the pdf documentation gets updated and therefore the hash
> changes and breaks the package.
Oh, OK.
> For this reason I think that, as you suggested before, we should build
> the documenta
Sorry for taking this long to answer.
On Wed, Nov 19, 2014 at 10:04 AM, Ludovic Courtès wrote:
> IIUC, this patch can now be applied. Please push it if there’s no
> blocker left.
In the mean time version 1.9.1 was released. With this release I
noticed that the pdf documentation gets updated an
Federico Beffa skribis:
> Please note that this patch will NOT build until the 'python-wrapper'
> will be applied (but I tested it again with my previous
> 'python-wrapper' patch). It is my understanding that Andreas will look
> into the 'python-wrapper' patch at a suitable time.
The ‘python-wra
l...@gnu.org (Ludovic Courtès) skribis:
> This is because Python is not added to ‘LIBRARY_PATH’, right?
>
> I think this is fixed by this patch:
>
> --- a/guix/build-system/python.scm
> +++ b/guix/build-system/python.scm
> @@ -110,10 +110,11 @@ prepended to the name."
>
On Thu, Oct 30, 2014 at 05:56:53PM +0100, Federico Beffa wrote:
> On Wed, Oct 29, 2014 at 11:20 PM, Andreas Enge wrote:
> > So we should add tk as an input to the python package?
>
> That would be great! In this way the python package should build the
> Tkinter library which currently is missing
On Thu, Oct 30, 2014 at 6:03 PM, Andreas Enge wrote:
> Okay. I think I should do this together with the changes to python-wrapper
> in the python branch to be created. For both python-2 and python-3?
Yes, please. That will allow making a matplotlib package for both
versions of python.
Regards,
On Wed, Oct 29, 2014 at 11:20 PM, Andreas Enge wrote:
> On Mon, Oct 27, 2014 at 09:26:41PM +0100, Federico Beffa wrote:
>> I get error messages that matplotlib is missing. I started looking at
>> matplotlib as well, but I've found that, for the TkAgg back-end, it
>> needs TKinter which is part of
On Wed, Oct 29, 2014 at 11:11 PM, Ludovic Courtès wrote:
>> +(define python2-numpy-reference python-numpy-reference)
>> +
>> +(define python2-numpy-userguide python-numpy-userguide)
>
> These variables are unused and not needed, so they can be removed.
Ah, you are right. I thought that 'package-
On Wed, Oct 29, 2014 at 08:55:52PM +0100, Federico Beffa wrote:
> Updated patch.
> - (python (string-append (assoc-ref %build-inputs "python")
> "/bin/")))
> + (python (string-append (assoc-ref %build-inputs "python")
> "/bin/"))
> + (lib (string-a
On Tue, Oct 28, 2014 at 10:34:48AM +0100, Ludovic Courtès wrote:
> Ah right. And what if you again remove Python from ‘inputs’, and add
> #:python ,python
> to the arguments?
> That means it will use the actual Python 3.x package, not the wrapper,
> so everything will be visible. The downside i
On Mon, Oct 27, 2014 at 09:26:41PM +0100, Federico Beffa wrote:
> I get error messages that matplotlib is missing. I started looking at
> matplotlib as well, but I've found that, for the TkAgg back-end, it
> needs TKinter which is part of the standard python libraries and it is
> built if, during
Federico Beffa skribis:
> From 6673a353080fd4b5136553624a7d777d243fc9a2 Mon Sep 17 00:00:00 2001
> From: Federico Beffa
> Date: Wed, 29 Oct 2014 20:44:33 +0100
> Subject: [PATCH] gnu: Add numpy.
>
> * gnu/packages/python.scm (python-numpy, python2-numpy): New variables.
> (python-wrapper): Add
Federico Beffa skribis:
> On Tue, Oct 28, 2014 at 10:34 AM, Ludovic Courtès wrote:
[...]
>> Perhaps the right fix will be to change ‘python-wrapper’ to symlink the
>> ‘lib’ sub-directory of ‘python’.
>
> It was also suggested to make python a propagating input of the wrapper.
> https://lists.g
Federico Beffa skribis:
> In my opinion the fact that guix makes it easy to build a package on
> the user machine is really a key advantage over other package
> managers/distributions, for a few, somewhat special packages, ATLAS
> being one. It would really be a pity to give up such nice a featu
Updated patch.
Regards,
Fede
From 6673a353080fd4b5136553624a7d777d243fc9a2 Mon Sep 17 00:00:00 2001
From: Federico Beffa
Date: Wed, 29 Oct 2014 20:44:33 +0100
Subject: [PATCH] gnu: Add numpy.
* gnu/packages/python.scm (python-numpy, python2-numpy): New variables.
(python-wrapper): Add symlink
> Personally my main use of ATLAS is through numpy/scipy. Therefore I
> would like to be able to use a good performing ATLAS with those
> packages. If that needs a manual installation step, that's fine with
> me.
>
> In principle we could make a second package and add a suffix to the
> version num
l...@gnu.org (Ludovic Courtès) skribis:
> After some more thought, I’ve finally bit the bullet:
>
> 1. Commit 77b0ac9 adds the #:substitutable? flag to gnu-build-system.
>
> 2. Commit f15615b uses it for ATLAS.
There was a related bug: ‘guix build atlas’ and similar would tell you
that atlas
On Tue, Oct 28, 2014 at 10:34 AM, Ludovic Courtès wrote:
> Ah right. And what if you again remove Python from ‘inputs’, and add
>
> #:python ,python
>
> to the arguments?
>
> That means it will use the actual Python 3.x package, not the wrapper,
> so everything will be visible. The downside is
Federico Beffa skribis:
> On Sun, Oct 26, 2014 at 7:56 PM, Ludovic Courtès wrote:
>> Can these manuals be built from source?
>
> I get error messages that matplotlib is missing. I started looking at
> matplotlib as well, but I've found that, for the TkAgg back-end, it
> needs TKinter which is p
On Sun, Oct 26, 2014 at 7:56 PM, Ludovic Courtès wrote:
> Can these manuals be built from source?
I get error messages that matplotlib is missing. I started looking at
matplotlib as well, but I've found that, for the TkAgg back-end, it
needs TKinter which is part of the standard python libraries
Federico Beffa skribis:
> From 063b33562c4fee2ea4e3fd1b53a27770047e9201 Mon Sep 17 00:00:00 2001
> From: Federico Beffa
> Date: Sun, 26 Oct 2014 15:03:17 +0100
> Subject: [PATCH 1/2] gnu: Add numpy
>
> * gnu/packages/python.scm(python-numpy, python2-num
Here the first packages depending on ATLAS.
Regards,
Fede
From 063b33562c4fee2ea4e3fd1b53a27770047e9201 Mon Sep 17 00:00:00 2001
From: Federico Beffa
Date: Sun, 26 Oct 2014 15:03:17 +0100
Subject: [PATCH 1/2] gnu: Add numpy
* gnu/packages/python.scm(python-numpy, python2-numpy): New variables
25 matches
Mail list logo
