On Mon, Nov 3, 2014 at 9:12 PM, Federico Beffa wrote:
> No, Andreas is right: this patch suffers from the same problem as Numpy.
Maybe I wasn't clear :-) the patch does include python as an input.
So, it will build in master, without any change in python-wrapper.
After the changes in python-wrap
On Mon, Nov 3, 2014 at 8:50 PM, Andreas Enge wrote:
> On Mon, Nov 03, 2014 at 08:42:25PM +0100, Ludovic Courtès wrote:
>> But are you sure you aren’t confusing it with NumPy, which requires the
>> new python-wrapper?
>
> Probably I am confusing things, even less problems then!
>
No, Andreas is ri
On Mon, Nov 03, 2014 at 08:42:25PM +0100, Ludovic Courtès wrote:
> But are you sure you aren’t confusing it with NumPy, which requires the
> new python-wrapper?
Probably I am confusing things, even less problems then!
Andreas
Andreas Enge skribis:
> On Mon, Nov 03, 2014 at 05:57:58PM +0100, Ludovic Courtès wrote:
>> Federico Beffa skribis:
>> > Subject: [PATCH] gnu: Add Cython
>> > * gnu/packages/python.scm(cython,cython2): New variables.
>> Pushed, with missing spaces in the commit log added.
>
> I think that should
On Mon, Nov 03, 2014 at 05:57:58PM +0100, Ludovic Courtès wrote:
> Federico Beffa skribis:
> > Subject: [PATCH] gnu: Add Cython
> > * gnu/packages/python.scm(cython,cython2): New variables.
> Pushed, with missing spaces in the commit log added.
I think that should have gone on the wip-python bran
Federico Beffa skribis:
> From 3155aa1ec614afb01b7bff0bbf3eabb4ee5bb0de Mon Sep 17 00:00:00 2001
> From: Federico Beffa
> Date: Mon, 20 Oct 2014 19:52:45 +0200
> Subject: [PATCH] gnu: Add Cython
>
> * gnu/packages/python.scm(cython,cython2): New variables.
Pushed, with missing spaces in the com
On Fri, Oct 24, 2014 at 9:50 PM, Andreas Enge wrote:
> Maybe we should propagate its input python? Then python-wrapper would
> also install python instead of just adding a few links to the binaries.
>From my point of view this would be desirable. I'm having the same
problem with other packages s
Concerning the following problem with python-wrapper:
On Fri, Oct 24, 2014 at 05:51:12PM +0200, Federico Beffa wrote:
> +;; we need the full python package and not just the python-wrapper
> +;; because we need libpython3.3m.so
Maybe we should propagate its input python? Then python-wrappe
On Thu, Oct 23, 2014 at 8:25 AM, Andreas Enge wrote:
> Since there will be two packages, I suggest to follow our python module
> naming conventions although this is not a python module, and to prepend
> with "python-" and "python2-". Writing "cython2" would look as if this were
> a next generation
On Mon, Oct 20, 2014 at 08:43:38PM +0200, Federico Beffa wrote:
> I'm a little bit unsure about the name of the package. I've not
> prefixed it with "python[2]-" as the program extends the Python
> language and can work with both (2 and 3) Python version series.
> However, the package installs file
On Mon, Oct 20, 2014 at 11:15 PM, Eric Bavier wrote:
>
> It's not a common need when building packages. There are a few other
> packages that need an existing, writable $HOME when building or testing.
OK. But if the directory would exist, then the build system would
cover more packages with no e
Federico Beffa writes:
> In preparing this package I've found that the python-build-system (not
> sure about the others) defines the environment variable HOME as
> "/homeless-shelter". However, that directory does not exist in the
> build chroot. This is a problem for cython, because it wants to
12 matches
Mail list logo
