Or include your prefered Pyrex version in your distribution. <br><br>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.<br>
<br><div class="gmail_quote">On Sun, Dec 21, 2008 at 3:20 PM, Phillip J. Eby <span dir="ltr"><<a href="mailto:pje@telecommunity.com">pje@telecommunity.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">At 12:51 PM 12/21/2008 +0000, <a href="mailto:devel@jonasmelian.com">devel@jonasmelian.com</a> wrote:<br>
>When I use the next command in my home system:<br>
><br>
> $ python setup.py develop<br>
><br>
>Pyrex compiles the '.pyx' file without any problem. But after of<br>
>uploading it to Pypi, and when is installed via 'easy_install' it<br>
>doesn't builds any more. (I had to upload the '.c' file compiled on my<br>
>system)<br>
<br>
</div>This is normal: the person receiving your distribution must either<br>
have Pyrex, or you must include the .c file. I normally just check<br>
the generated .c files into revision control, so that setuptools will<br>
automatically send them out in my source distributions.<br>
<br>
(It can be a good idea to do this even if your target audience has<br>
Pyrex, since it gives you better control over which version of Pyrex<br>
gets used for the building.)<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
Pyrex mailing list<br>
<a href="mailto:Pyrex@lists.copyleft.no">Pyrex@lists.copyleft.no</a><br>
<a href="http://lists.copyleft.no/mailman/listinfo/pyrex" target="_blank">http://lists.copyleft.no/mailman/listinfo/pyrex</a><br>
</div></div></blockquote></div><br>