On Sunday 11 November 2007 7:08:38 pm Andrew Straw wrote: > Eric Firing wrote: > > Darren Dale wrote: > >> 3) We can not include traits-3 without either adding setuptools as an > >> external dependency (which is already true for python-2.3 users) or > >> monkey-patching distutils. traits-3 includes some pyrex code, which > >> standard distutils does not recognize. > > > > Is it a viable alternative to add pyrex as an external dependency? > > Pyrex.Distutils makes it easy to use pyrex modules via otherwise > > standard setup.py scripts. And pyrex itself is pure python, very easy > > to install. > > We can also just package the .c file built by Pyrex whenever the > developer changes the .pyx file. That way, there is no further > infrastructure to include. On the other hand, as Darren suggested later, > one can do what setuptools' build_ext command does without setuptools > (if an extension source ends in .pyx, call pyrexc on it. If pyrexc is > not available, skip that step. In both cases, then compile the .c file > with the c compiler.) Darren, if you're still having trouble with this, > I can dig up the old code I had that did this (I switched to setuptools > for this, and other stuff, a long time ago).
Thanks for the offer. For now, I think it is best that we use traits-2.6, which doesnt have any pyrex code. Once traits-3 stabilizes and is released, I'll try what you have suggested. Darren ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
