Chris Barker wrote: > Hi all, > > I just ran into an issue with py2exe -- my app failed because various > numpy sub-packages weren't included. However, I wasn't using them. But > it failed because numerix imports them, and they weren't included > because it imports them with __import__ > > Anyway, I can work around this, but it made me wonder: is it time to > retire numerix? We all should be using numpy anyway.
Why was numerix getting imported? Is this inherent in py2exe--that it imports all subpackages of a base, if you use that base (matplotlib)? Numerix is there only for the convenience of anyone who has code that depends on it; it is completely unused in matplotlib itself. I would be happy get it out of matplotlib, or phase it out if necessary. I don't think it should be left there forever. Eric > > note that the docstring is out of date, too: > > """ > 1. The value of numerix in matplotlibrc: either Numeric or numarray > > 2. If none of the above is done, the default array package is Numeric. > Because the matplotlibrc always provides *some* value for numerix > (it has it's own system of default values), this default is most > likely never used. > > To summarize: the commandline is examined first, the rc file second, > and the default array package is Numeric. > """ > > -Chris > > > > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
