On Nov 7, 2007, at 12:04 PM, John Hunter wrote:
On Nov 7, 2007 12:01 PM, Boyd Waters <[EMAIL PROTECTED]> wrote:Tell them they need a "real" enthought traits package. Then they can use their package management to make it right.This is of course assuming their package management has enthought.traits, which by and large, it won't. I am sympathetic to this view, but our recent experience has been that getting enthought.traits to install properly even for matplotlib developers took a fair amount of work and consultation with the enthought dev team.
Ouch, was it really that hard? I don't remember it being that hard, but I am almost certainly forgetting something about the traits tweaks that were needed to get MatPlotLib built... maybe I didn't upgrade MPL after running into MPL build errors with traits. Hmm.
FWIW, here are the MacPorts for "standard" enthought traits that I cobbled up :
enthought-traits-macports.tbz
Description: Binary data
Change the PortGroup value at the top of the Portfile from "PortGroup python25 apple" to "PortGroup python25 1.0" to use the MacPorts- installed Python.
Is there a MPL-tweaked distribution of enthought traits? I am sorry if I have misunderstood.
- boyd Boyd Waters Scientific Programmer National Radio Astronomy Observatory Socorro, New Mexico http://www.aoc.nrao.edu/~bwaters
------------------------------------------------------------------------- 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
