Re: Compiling via setuptools

Or include your prefered Pyrex version in your distribution.

It adds under 300k, still allows you to perform IFDEF's for
platform-specific building, and in most cases the .c files would be much
more than +300k compared to the Pyrex sources alone.

On Sun, Dec 21, 2008 at 3:20 PM, Phillip J. Eby <[email protected]>wrote:

> At 12:51 PM 12/21/2008 +0000, [email protected] wrote:
> >When I use the next command in my home system:
> >
> >   $ python setup.py develop
> >
> >Pyrex compiles the '.pyx' file without any problem. But after of
> >uploading it to Pypi, and when is installed via 'easy_install' it
> >doesn't builds any more. (I had to upload the '.c' file compiled on my
> >system)
>
> This is normal: the person receiving your distribution must either
> have Pyrex, or you must include the .c file.  I normally just check
> the generated .c files into revision control, so that setuptools will
> automatically send them out in my source distributions.
>
> (It can be a good idea to do this even if your target audience has
> Pyrex, since it gives you better control over which version of Pyrex
> gets used for the building.)
>
>
> _______________________________________________
> Pyrex mailing list
> [email protected]
> http://lists.copyleft.no/mailman/listinfo/pyrex
>

_______________________________________________
Pyrex mailing list
[email protected]
http://lists.copyleft.no/mailman/listinfo/pyrex