On 07/31/2013 01:47 PM, Russell E. Owen wrote: > In article <51f92f58.6020...@stsci.edu>, > Michael Droettboom <md...@stsci.edu> > wrote: > >> I have tagged and uploaded matplotlib 1.3.0 final. Congratulations to >> all involved! It was a long slog getting this release out, and I >> appreciate everyone's patience. >> >> Once we have binaries uploaded to SourceForge, I will make a formal >> announcement in the usual channels. > I built the Mac binary on MacOS X 10.6 but have run into two problems: > - Most of the unit tests are missing, so I can't properly test the > results. But my application that uses matplotlib and TkAgg works fine, > so may well be OK. Also, I checked and the installer was trying to build > all expected backends (including the native Mac backend).
What do you mean the unit tests are missing? They don't run? Can you send the output from nose? Glad to hear about the installer building the macosx backend -- that was pretty serious when it wasn't doing that. > > - When the 1.3.0 installer is used to overwrite matplotlib 1.2.1 (and > the pytz and dateutil that it installs) it breaks pytz and dateutils, by > deleting most of the contents, leaving only a subdir named zoneinfo in > each package (with different contents for each package). > > Installing a new pytz and dateutils and running the 1.3.0 binary > installer (overwriting matplotlib 1.3.0 or no matplotlib at all) leaves > these packages functional (though it changes the modification date, so > it's doing something). I thought you were including pytz and dateutils in your installer. Is that not the case? If not, isn't it enough to document that matplotlib now doesn't ship with these dependencies, and they will need to be installed using pip or other means? Can they be installed afterward and have things work? Cheers, Mike > > I have replicated this several times. > > I'm not sure whether to upload this installer. It's a bit dangerous and > ill tested. > > -- Russell > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
