I just downloaded 0.99.1 and ran into some problems using it in Sage. Basically, in the tar.gz file, there was a setup.cfg file, which had the following: Note that some options are already uncommented, forcing a build of tkagg, wxagg, and macosx backends, and forcing the default backend to be tkagg. This is in direct contradiction to the text just above these commands, which say the default is an "auto" option. # You can uncomment any the following lines if you know you do # not want to use the GUI toolkit. Acceptible values are: # True: build the extension. Exits with a warning if the # required dependencies are not available # False: do not build the extension # auto: build if the required dependencies are available, # otherwise skip silently. This is the default # behavior # #gtk = False #gtkagg = False tkagg = True wxagg = True macosx = True [rc_options] # User-configurable options # # Default backend, one of: Agg, Cairo, CocoaAgg, GTK, GTKAgg, GTKCairo, # FltkAgg, MacOSX, Pdf, Ps, QtAgg, Qt4Agg, SVG, TkAgg, WX, WXAgg. # # The Agg, Ps, Pdf and SVG backends do not require external # dependencies. Do not choose GTK, GTKAgg, GTKCairo, MacOSX, TkAgg or WXAgg # if you have disabled the relevent extension modules. Agg will be used # by default. # backend = TkAgg Should I just delete the setup.cfg file? It looks like it shouldn't be in the release, since there is a template file there. Thanks, Jason
On Tue, Sep 22, 2009 at 5:38 PM, <jas...@cr...> wrote: > I just downloaded 0.99.1 and ran into some problems using it in Sage. > Basically, in the tar.gz file, there was a setup.cfg file, which had the > following: This was a bug in the tarball -- mpl doesn't keep a copy of setup.cfg in svn and shouldn't ship with it. We do ship setup.cfg.template which you can use to create and customize a setup.cfg, but there shouldn't be one by default. It's not listed in MANIFEST.in, but apparently when I built the tarball I had not done an svn-clean. setup.cfg *was* in my MANIFEST (which is autogenerated at build time) on my build machine, but I am not sure why it was added since it isn't in MANIFEST.in. In any case, I just rebuilt and reuploaded the tarball with no setup.cfg from a clean dir https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.1/ Thanks for the report. JDH
Received from John Hunter on Tue, Sep 22, 2009 at 09:57:37PM EDT: > On Tue, Sep 22, 2009 at 5:38 PM, <jas...@cr...> wrote: > > I just downloaded 0.99.1 and ran into some problems using it in Sage. > > Basically, in the tar.gz file, there was a setup.cfg file, which had the > > following: > > This was a bug in the tarball -- mpl doesn't keep a copy of setup.cfg > in svn and shouldn't ship with it. We do ship setup.cfg.template > which you can use to create and customize a setup.cfg, but there > shouldn't be one by default. > > It's not listed in MANIFEST.in, but apparently when I built the > tarball I had not done an svn-clean. setup.cfg *was* in my MANIFEST > (which is autogenerated at build time) on my build machine, but I am > not sure why it was added since it isn't in MANIFEST.in. > > In any case, I just rebuilt and reuploaded the tarball with no > setup.cfg from a clean dir > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.1/ > > Thanks for the report. > > JDH The latest tarball (downloaded as of a few minutes ago) still seems to contain a setup.cfg file: $ tar zft matplotlib-0.99.1.tar.gz |grep setup.cfg matplotlib-0.99.1/setup.cfg matplotlib-0.99.1/setup.cfg.template L.G.
On Wed, Sep 23, 2009 at 8:47 AM, Lev Givon <le...@co...> wrote: > contain a setup.cfg file: > > $ tar zft matplotlib-0.99.1.tar.gz |grep setup.cfg > matplotlib-0.99.1/setup.cfg > matplotlib-0.99.1/setup.cfg.template It seems to depend on which mirror you get the file from. From Voxel, I see setup.cfg but from "German Research Network (Berlin, Germany) " I do not see it. We may just need time for the mirrors to update. I probably should have used a different file name... JDH
John Hunter <jdh2358@...> writes: > > On Wed, Sep 23, 2009 at 8:47 AM, Lev Givon <lev@...> wrote: > > contain a setup.cfg file: > > > > $ tar zft matplotlib-0.99.1.tar.gz |grep setup.cfg > > matplotlib-0.99.1/setup.cfg > > matplotlib-0.99.1/setup.cfg.template > > It seems to depend on which mirror you get the file from. From Voxel, > I see setup.cfg but from "German Research Network (Berlin, Germany) " > I do not see it. We may just need time for the mirrors to update. I > probably should have used a different file name... John Hunter <jdh2358@...> writes: > > On Wed, Sep 23, 2009 at 8:47 AM, Lev Givon <lev@...> wrote: > > contain a setup.cfg file: > > > > $ tar zft matplotlib-0.99.1.tar.gz |grep setup.cfg > > matplotlib-0.99.1/setup.cfg > > matplotlib-0.99.1/setup.cfg.template > > It seems to depend on which mirror you get the file from. From Voxel, > I see setup.cfg but from "German Research Network (Berlin, Germany) " > I do not see it. We may just need time for the mirrors to update. I > probably should have used a different file name... I also find setup.cfg in 0.99.1.1.tar.gz, and had to delete it to begin building: $ wget http://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib- 0.99.1/matplotlib-0.99.1.1.tar.gz?use_mirror=kent ... 20:44:41 (2.11 MB/s) - `matplotlib-0.99.1.1.tar.gz' saved [11905737/11905737] $ tar xf matplotlib-0.99.1.1.tar.gz $ cd matplotlib-0.99.1.1 $ ls setup.cfg setup.cfg Chris