matplotlib-devel — matplotlib developers

Re: [matplotlib-devel] Refactoring the axes module

[Damon M. <dam...@gm...>]

On Sat, Jun 29, 2013 at 4:10 PM, Benjamin Root <ben...@ou...> wrote:

> Perhaps it would be a good idea to exercise the mpl toolkits with this
> since it is more likely for them to do more esoteric things with axes.
> Don't forget Base map and possibly cartopy and pandas.
>

Thanks Ben.  I already did some playing with mplot3d, but I haven't tried
axes_grid{,1} or basemap yet.


> Cheers!
> Ben Root
> On Jun 28, 2013 5:20 PM, "Nelle Varoquaux" <nel...@gm...>
> wrote:
>
>> Hello pythonistas,
>>
>> We've just finished refactoring the axes module at the scipy sprint, and
>> before merging we would like to inform developers of the changes. The axes
>> module contained more than 9k loc, and a few classes. It used to be a
>> file.
>>
>> Now, it became a folder called "axes". This module contains several
>> private submodules:
>> - _base.py: this private module contains a new class _AxesBase, that
>> inherits from Artist. This new class contains all the methods except
>> the plotting and labelling methods. It is now 3k loc
>> - _axes.py contains the Axes class. This class inherists from _AxesBase,
>> and contains all the methods concerning plotting and labelling. It is now
>> 6k loc
>> - _subplots.py contains all the subplots directive.
>>
>> The API has not changed: only the private methods from axes are not
>> directly importable from axes anymore. All tests pass (travis shows a
>> failed test on py3k, which I am not able to reproduce on my computer). The
>> pull request can be seen here: https://github.com/matplotlib/matplotlib
>> /pull/1931
>>
>> Once this is merged, you may need to remove cleanly the previous
>> installed version of matplotlib. Indeed, installing a package replaces
>> the old files, but does not delete them. Thus, installing this new
>> submodule will not remove the axes.py file. Hence, a manual deletion of
>> this file is necessary.
>>
>> Thanks,
>> N
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>


-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Re: [matplotlib-devel] Refactoring the axes module

[Benjamin R. <ben...@ou...>]

Perhaps it would be a good idea to exercise the mpl toolkits with this
since it is more likely for them to do more esoteric things with axes.
Don't forget Base map and possibly cartopy and pandas.

Cheers!
Ben Root
On Jun 28, 2013 5:20 PM, "Nelle Varoquaux" <nel...@gm...>
wrote:

> Hello pythonistas,
>
> We've just finished refactoring the axes module at the scipy sprint, and
> before merging we would like to inform developers of the changes. The axes
> module contained more than 9k loc, and a few classes. It used to be a
> file.
>
> Now, it became a folder called "axes". This module contains several
> private submodules:
> - _base.py: this private module contains a new class _AxesBase, that
> inherits from Artist. This new class contains all the methods except
> the plotting and labelling methods. It is now 3k loc
> - _axes.py contains the Axes class. This class inherists from _AxesBase,
> and contains all the methods concerning plotting and labelling. It is now
> 6k loc
> - _subplots.py contains all the subplots directive.
>
> The API has not changed: only the private methods from axes are not
> directly importable from axes anymore. All tests pass (travis shows a
> failed test on py3k, which I am not able to reproduce on my computer). The
> pull request can be seen here: https://github.com/matplotlib/matplotlib
> /pull/1931
>
> Once this is merged, you may need to remove cleanly the previous installed
> version of matplotlib. Indeed, installing a package replaces the old
> files, but does not delete them. Thus, installing this new submodule will
> not remove the axes.py file. Hence, a manual deletion of this file is
> necessary.
>
> Thanks,
> N
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Re: [matplotlib-devel] Refactoring the axes module

[Nathaniel S. <nj...@po...>]

On Sat, Jun 29, 2013 at 8:13 PM, Damon McDougall
<dam...@gm...> wrote:
> To reiterate, remember that you'll need to nuke your previous local install.  Installing over an existing mpl distribution will cause problems.  This is because `python setup.py install` will not remove the old axes.py for you.

NB that this is in general a good reason to make a habit of using 'pip
install .' instead of 'python setup.py install'. pip *will* nuke old
versions for you, and thus gives you a better chance of importing the
code that was actually shipped.

-n

Re: [matplotlib-devel] Refactoring the axes module

[Damon M. <dam...@gm...>]

On Fri, Jun 28, 2013 at 5:20 PM, Nelle Varoquaux
<nel...@gm...>wrote:

> Hello pythonistas,
>
> We've just finished refactoring the axes module at the scipy sprint, and
> before merging we would like to inform developers of the changes. The axes
> module contained more than 9k loc, and a few classes. It used to be a
> file.
>
> Now, it became a folder called "axes". This module contains several
> private submodules:
> - _base.py: this private module contains a new class _AxesBase, that
> inherits from Artist. This new class contains all the methods except
> the plotting and labelling methods. It is now 3k loc
> - _axes.py contains the Axes class. This class inherists from _AxesBase,
> and contains all the methods concerning plotting and labelling. It is now
> 6k loc
> - _subplots.py contains all the subplots directive.
>
> The API has not changed: only the private methods from axes are not
> directly importable from axes anymore. All tests pass (travis shows a
> failed test on py3k, which I am not able to reproduce on my computer). The
> pull request can be seen here: https://github.com/matplotlib/matplotlib
> /pull/1931
>
> Once this is merged, you may need to remove cleanly the previous installed
> version of matplotlib. Indeed, installing a package replaces the old
> files, but does not delete them. Thus, installing this new submodule will
> not remove the axes.py file. Hence, a manual deletion of this file is
> necessary.
>


Thanks Nelle.  This is fantastic work and rather tedious given the size of
our axes.py file.  I've done some sanity checks on this and worked with
Nelle to minimise any potential issues people may have.  Some things have
changed.  It's probably best to refer to the Github issue to see the paper
trail.

To reiterate, remember that you'll need to nuke your previous local
install.  Installing over an existing mpl distribution will cause problems.
 This is because `python setup.py install` will not remove the old axes.py
for you.

Thanks,
Damon

-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

[matplotlib-devel] MEP13

[Tony Yu <ts...@gm...>]

Hi matplotlib-devs,

I just added an alternate proposal to MEP13 (scroll to the bottom):

https://github.com/matplotlib/matplotlib/wiki/MEP13

which suggests that axes methods mirror the names of pyplot functions just
so it's easier to switch between the two. We could maintain the current
interface but with easier conversion.

Thoughts?

Cheers!
-Tony

[matplotlib-devel] Refactoring the axes module

[Nelle V. <nel...@gm...>]

Hello pythonistas,

We've just finished refactoring the axes module at the scipy sprint, and
before merging we would like to inform developers of the changes. The axes
module contained more than 9k loc, and a few classes. It used to be a file.

Now, it became a folder called "axes". This module contains several private
submodules:
- _base.py: this private module contains a new class _AxesBase, that
inherits from Artist. This new class contains all the methods except
the plotting and labelling methods. It is now 3k loc
- _axes.py contains the Axes class. This class inherists from _AxesBase,
and contains all the methods concerning plotting and labelling. It is now
6k loc
- _subplots.py contains all the subplots directive.

The API has not changed: only the private methods from axes are not
directly importable from axes anymore. All tests pass (travis shows a
failed test on py3k, which I am not able to reproduce on my computer). The
pull request can be seen here: https://github.com/matplotlib/matplotlib
/pull/1931

Once this is merged, you may need to remove cleanly the previous installed
version of matplotlib. Indeed, installing a package replaces the old files,
but does not delete them. Thus, installing this new submodule will not
remove the axes.py file. Hence, a manual deletion of this file is necessary.

Thanks,
N

[matplotlib-devel] Matplotlib Sprints

[Michael D. <md...@st...>]

For those not in Austin who are interested in following along with the 
matplotlib sprint at Scipy, feel free to visit here:

https://etherpad.mozilla.org/MatplotlibSprint

Mike

Re: [matplotlib-devel] Creating 3d file

[James C. <jcs...@gm...>]

This was my original attempt to go about this problem. This however, did
not give back the data that I need. Using the get_path() method returns the
vertices for the 2d protection of the 3d functions. The data that I need is
the raw 3d data for the function.

James
On Jun 26, 2013 12:42 PM, "Erik Bray" <eri...@gm...> wrote:

> On Tue, Jun 25, 2013 at 8:52 AM, James Cline <jcs...@gm...>
> wrote:
> > Hi,
> >
> > I am trying to use matplotlib to create obj file that I can render in
> > blender. I have already created the code to create the file itself. I am
> > currently trying to find the best place to put my code into. I have tried
> > editing the axes3d file and was able to create a working file. However,
> I am
> > worried there will be too much code recreation at this level.  I have
> also
> > attempted to edit the art3d file to try to have less code generation.
> > However, I was unable to find all of the data for the points. Any help or
> > ideas on where to put the code would be greatly appreciated.
> >
> > If anymore information is needed please let me know, this is my first
> post
> > so I apologize if I left something out.
>
> I'm not an expert on Matplotlib's 3D toolkit, but it sounds to me like
> you're trying to insert your code directly into Matplotlib itself
> somewhere?  And I don't think that's what you want to be doing.  If
> you already have code to write the blender format then in order to
> dump, say, the polygons for the model call .get_children() on the
> Axes3D object and look for the Poly3DCollection.  Then call
> .get_paths() on that it will return a list of all the polygons in the
> model and the vertices that define them.  Check the documentation for
> the Path class for understanding these.
>
> Erik
>

Re: [matplotlib-devel] Creating 3d file

[Erik B. <eri...@gm...>]

On Tue, Jun 25, 2013 at 8:52 AM, James Cline <jcs...@gm...> wrote:
> Hi,
>
> I am trying to use matplotlib to create obj file that I can render in
> blender. I have already created the code to create the file itself. I am
> currently trying to find the best place to put my code into. I have tried
> editing the axes3d file and was able to create a working file. However, I am
> worried there will be too much code recreation at this level.  I have also
> attempted to edit the art3d file to try to have less code generation.
> However, I was unable to find all of the data for the points. Any help or
> ideas on where to put the code would be greatly appreciated.
>
> If anymore information is needed please let me know, this is my first post
> so I apologize if I left something out.

I'm not an expert on Matplotlib's 3D toolkit, but it sounds to me like
you're trying to insert your code directly into Matplotlib itself
somewhere?  And I don't think that's what you want to be doing.  If
you already have code to write the blender format then in order to
dump, say, the polygons for the model call .get_children() on the
Axes3D object and look for the Poly3DCollection.  Then call
.get_paths() on that it will return a list of all the polygons in the
model and the vertices that define them.  Check the documentation for
the Path class for understanding these.

Erik

[matplotlib-devel] Creating 3d file

[James C. <jcs...@gm...>]

Hi,

I am trying to use matplotlib to create obj file that I can render in
blender. I have already created the code to create the file itself. I am
currently trying to find the best place to put my code into. I have tried
editing the axes3d file and was able to create a working file. However, I
am worried there will be too much code recreation at this level.  I have
also attempted to edit the art3d file to try to have less code generation.
However, I was unable to find all of the data for the points. Any help or
ideas on where to put the code would be greatly appreciated.

If anymore information is needed please let me know, this is my first post
so I apologize if I left something out.

Thanks,
James

[matplotlib-devel] "sprint" milestone

[Michael D. <md...@st...>]

Thanks for all of the bug triaging that went on over the weekend. As I'm 
going through it, some of these are things that are pretty high 
priority, which I'm milestoning as "1.3.x blocker", and some are lower 
priority, but are good candidates for good things to discuss in person 
during the sprint, which I'm milestoning as "sprint".

Feel free to do the same for anything else that you think would make 
sense as a sprint topic -- not necessarily to work on, but at least to 
discuss in person.

Mike

[matplotlib-devel] Building matplotlib on Windows

[Alexander B. <ale...@gm...>]

Hi all,

I try to build matplotlib 1.2.1 under Windows and create package for
OSGeo4W [0].
OSGeo4W contains most of the necessary dependencies: Python 2.7.2, numpy 1.5.1,
libpng 1.2.34, Qt 4.7.1, freetype 2.3.7 and others.

After downloading and unpacking matplotlib sources I edited
setupext.py file and add
'C:\OSGeo4W' to basedir list

basedir = defaultdict(lambda: ['/usr/local', '/usr'], {
    # execptions to the ['/usr/local', '/usr'] defaults
    'win32'  : ['win32_static', 'c:\\OSGeo4W'],                     #
<---- here is it
    'darwin' : ['/usr/local/', '/usr', '/usr/X11', '/opt/local'],
    'sunos5' : [os.getenv('MPLIB_BASE') or '/usr/local',],
    'gnu0' : ['/usr'],
    'aix5' : ['/usr/local'],
    })

Than in commandline I run python setup.py build, from output I found
that include
files can't be found by compiler (see build.log.1 file from attached
zip). So I open
setupext.py again and modify check_for_freetype and add_ft2font_flags functions
adding to them path to osgeo4w includes (freetype includes in osgeo4w located at
C:\OSGeo4W\include\freetype, without 2 at end), modified file attached.

After this modification build process started, there are no missed includes, but
another error appears, see file build.log.2. I checked and found that in OSGeo4W
freetype library localed here C:\OSGeo4W\lib\freetype237.lib.

Is it possible to specify name of the library file somewhere? Maybe
there is build
guide? I found instructions at github [1], but all this guildes used
self-compiled
dependencies, while I want to use dependencies from OSGeo4W to make fully
compatible package.

Any hints and help is welcome

[0] http://trac.osgeo.org/osgeo4w/
[1] https://github.com/matplotlib/matplotlib/issues/1717

Thanks and sorry for my English
-- 
Alexander Bruy

[matplotlib-devel] matplotlib 1.3.0rc4 (was: matplotlib 1.3.0rc3 tomorrow)

[Michael D. <md...@st...>]

I have made a new release candidate (1.3.0rc4) that fixes the following 
vs. 1.3.0rc3:

- It doesn't add a setup.cfg file to the tarball

- It doesn't install the KnownFailure nose plugin as a pkg_resources 
entry_point (this conflicted with IPython's plugin of the same name)

- We get a known failure from the pep8 test if pep8 isn't installed

Hopefully that's enough to get to the point of giving this release 
candidate some wider exposure before putting out a final release. We can 
use some sprint time at Scipy to get this release polished if desired 
and necessary, too.

Mike

On 06/19/2013 06:10 PM, Michael Droettboom wrote:
> On 06/19/2013 05:45 PM, Michael Droettboom wrote:
>> On 06/19/2013 05:03 PM, Russell E. Owen wrote:
>>> In article<51C...@st...>,
>>>   Michael Droettboom<md...@st...>  
>>>   wrote:
>>>
>>>> I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
>>>>
>>>> We may not get all the binaries up in the next little while, so I'll
>>>> wait for those and then make an announcement on matplotlib-users.  After
>>>> a couple of weeks, assuming no serious problems, we'll be ready for
>>>> 1.3.0 final.
>>>>
>>>> Thanks again to everyone for their help with this release!
>>> I have uploaded the MacOS 10.6 64-bit binary. However, there were a few
>>> unit test failures, including the font complaint that I first saw in an
>>> earlier 1.3.0 prerelease, plus one about pep8 that I've never seen
>>> before.
>>
>> The font issue was reportedly fixed by 9ccacff 
>> <https://github.com/pwuertz/matplotlib/commit/9ccacffe81e0d4a48e4a4b19064460b94c6f77c9>, 
>> but apparently not.  I'll ping Peter Wuertz about that.
> My bad.  It was determined that this was too difficult to fix at the 
> moment.  See issue https://github.com/matplotlib/matplotlib/pull/2117.
>
> Let's just ignore this for now -- for finesse we can trap this case 
> and mark it as "known fail", but I don't think that needs to hold 
> things up for now.
>
> Mike
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

[Fernando P. <fpe...@gm...>]

Thanks a ton, Mike! Great not to have to worry about this on our side.

cheers,

f

On Wed, Jun 19, 2013 at 10:02 AM, Michael Droettboom <md...@st...> wrote:
> Just to close the loop on this, I have created:
>
> https://github.com/matplotlib/matplotlib/pull/2139
>
>
> On 06/18/2013 07:18 PM, Fernando Perez wrote:
>
> Good point, I didn't know about that new mechanism.
>
> I think we should keep 2.6 support for IPython 1.0, but drop it
> afterwards. We can discuss that during the dev meeting...
>
> Cheers,
>
> f
>
> On Tue, Jun 18, 2013 at 4:16 PM, Thomas Kluyver <th...@kl...>
> wrote:
>
> On 19 June 2013 00:09, Fernando Perez <fpe...@gm...> wrote:
>
> I wish we could just fix this plugin issue.
>
> When we drop support for Python 2.6, I think we can use the expectedFailure
> mechanism included in unittest from 2.7 onwards. So long as nose recognises
> that, we should be able to drop our copy of the KnownFailure plugin.
>
> Thomas
>
>
>



-- 
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Michael D. <md...@st...>]

On 06/19/2013 05:45 PM, Michael Droettboom wrote:
> On 06/19/2013 05:03 PM, Russell E. Owen wrote:
>> In article<51C...@st...>,
>>   Michael Droettboom<md...@st...>  
>>   wrote:
>>
>>> I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
>>>
>>> We may not get all the binaries up in the next little while, so I'll
>>> wait for those and then make an announcement on matplotlib-users.  After
>>> a couple of weeks, assuming no serious problems, we'll be ready for
>>> 1.3.0 final.
>>>
>>> Thanks again to everyone for their help with this release!
>> I have uploaded the MacOS 10.6 64-bit binary. However, there were a few
>> unit test failures, including the font complaint that I first saw in an
>> earlier 1.3.0 prerelease, plus one about pep8 that I've never seen
>> before.
>
> The font issue was reportedly fixed by 9ccacff 
> <https://github.com/pwuertz/matplotlib/commit/9ccacffe81e0d4a48e4a4b19064460b94c6f77c9>, 
> but apparently not.  I'll ping Peter Wuertz about that.
My bad.  It was determined that this was too difficult to fix at the 
moment.  See issue https://github.com/matplotlib/matplotlib/pull/2117.

Let's just ignore this for now -- for finesse we can trap this case and 
mark it as "known fail", but I don't think that needs to hold things up 
for now.

Mike

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Russell O. <ro...@uw...>]

I found setup.cfg in the 1.3.0rc3 tarball that I downloaded from the usual location:<http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.3.0rc3/matplotlib-1.3.0rc3.tar.gz/download>

Here is the complete contents. None of these entries except [egg_info] appear in setup.cfg.template. However,  setup.cfg.template has *NO* entries after [egg_info] which suggests that it could use more documentation.

--- start setup.cfg ----
[egg_info]
tag_build = 
tag_date = 0
tag_svn_revision = 0

--- end setup.cfg ----


-- Russell


On Jun 19, 2013, at 2:13 PM, Damon McDougall <dam...@gm...> wrote:

> 
> 
> 
> On Wed, Jun 19, 2013 at 2:29 PM, Russell E. Owen <ro...@uw...> wrote:
> In article <51C...@st...>,
>  Michael Droettboom <md...@st...>
>  wrote:
> 
> > I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
> >
> > We may not get all the binaries up in the next little while, so I'll
> > wait for those and then make an announcement on matplotlib-users.  After
> > a couple of weeks, assuming no serious problems, we'll be ready for
> > 1.3.0 final.
> >
> > Thanks again to everyone for their help with this release!
> >
> > Mike
> 
> Why does the distro include a setup.cfg, and why does it bear no
> resemblance to setup.cfg.template? (setup.cfg has just a few lines, and
> none of them are described in setup.cfg.template)
> 
> I don't see a setup.cfg file.  I'm looking here: https://github.com/matplotlib/matplotlib/tree/v1.3.x
> 
> All I see is the setup.cfg.template file.
>  
> 
> -- Russell
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
> 
> Build for Windows Store.
> 
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> 
> -- 
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Michael D. <md...@st...>]

On 06/19/2013 05:03 PM, Russell E. Owen wrote:
> In article <51C...@st...>,
>   Michael Droettboom <md...@st...>
>   wrote:
>
>> I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
>>
>> We may not get all the binaries up in the next little while, so I'll
>> wait for those and then make an announcement on matplotlib-users.  After
>> a couple of weeks, assuming no serious problems, we'll be ready for
>> 1.3.0 final.
>>
>> Thanks again to everyone for their help with this release!
> I have uploaded the MacOS 10.6 64-bit binary. However, there were a few
> unit test failures, including the font complaint that I first saw in an
> earlier 1.3.0 prerelease, plus one about pep8 that I've never seen
> before.

The pep8 one is because the pep8 tool is not installed on your system.  
We attempted to fix this so it was not a hard requirement, but obviously 
missed this.  I'll fix that as part of the next release candidate.

The font issue was reportedly fixed by 9ccacff 
<https://github.com/pwuertz/matplotlib/commit/9ccacffe81e0d4a48e4a4b19064460b94c6f77c9>, 
but apparently not.  I'll ping Peter Wuertz about that.

Mike

>
> I have appended the output from python -c "import matplotlib as m ;
> m.test(verbosity=1)"
>
> -- Russell
>
> Last login: Wed Jun 19 12:36:54 on ttys001
> localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)"
> .........................................................................
> .........................................................................
> .........................................................................
> ..........kpathsea: Invalid fontname `Bitstream Vera Serif', contains ' '
> Ekpathsea: Invalid fontname `Bitstream Vera Serif', contains ' '
> EK.....K.................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> .........................................................................
> ...................................../Library/Frameworks/Python.framework
> /Versions/2.7/lib/python2.7/site-packages/numpy/ma/core.py:777:
> RuntimeWarning: invalid value encountered in absolute
>    return umath.absolute(a) * self.tolerance >= umath.absolute(b)
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/ma/core.py:3791: UserWarning: Warning: converting a masked
> element to nan.
>    warnings.warn("Warning: converting a masked element to nan.")
> .........................................../Library/Frameworks/Python.fra
> mework/Versions/2.7/lib/python2.7/site-packages/matplotlib/gridspec.py:29
> 8: UserWarning: This figure includes Axes that are not compatible with
> tight_layout, so its results might be incorrect.
>    warnings.warn("This figure includes Axes that are not "
> ............................................/Library/Frameworks/Python.fr
> amework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py:8
> 07: RuntimeWarning: invalid value encountered in absolute
>    z = abs(x-y)
> ........E
> ======================================================================
> ERROR: matplotlib.tests.test_backend_pgf.test_pathclip
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/nose/case.py", line 197, in runTest
>      self.test(*self.arg)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/tests/test_backend_pgf.py", line 45, in backend_switcher
>      result = func(*args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/tests/test_backend_pgf.py", line 146, in test_pathclip
>      plt.savefig(os.path.join(result_dir, "pgf_pathclip.pdf"))
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/pyplot.py", line 561, in savefig
>      return fig.savefig(*args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/figure.py", line 1410, in savefig
>      self.canvas.print_figure(*args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backend_bases.py", line 2220, in print_figure
>      **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 865, in print_pdf
>      self._print_pdf_to_fh(fh, *args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 823, in _print_pdf_to_fh
>      self.print_pgf(fname_pgf, *args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 805, in print_pgf
>      self._print_pgf_to_fh(fh, *args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 785, in _print_pgf_to_fh
>      RendererPgf(self.figure, fh),
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 409, in __init__
>      self.latexManager = LatexManagerFactory.get_latex_manager()
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 223, in get_latex_manager
>      new_inst = LatexManager()
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 309, in __init__
>      raise LatexError("LaTeX returned an error, probably missing font or
> error in preamble:\n%s" % stdout)
> LatexError: LaTeX returned an error, probably missing font or error in
> preamble:
> This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012)
>   restricted \write18 enabled.
> **entering extended mode
> LaTeX2e <2011/06/27>
> Babel <v3.8m> and hyphenation patterns for english, dumylang,
> nohyphenation, ge
> rman-x-2012-05-30, ngerman-x-2012-05-30, afrikaans, ancientgreek,
> ibycus, arabi
> c, armenian, basque, bulgarian, catalan, pinyin, coptic, croatian,
> czech, danis
> h, dutch, ukenglish, usenglishmax, esperanto, estonian, ethiopic, farsi,
> finnis
> h, french, friulan, galician, german, ngerman, swissgerman, monogreek,
> greek, h
> ungarian, icelandic, assamese, bengali, gujarati, hindi, kannada,
> malayalam, ma
> rathi, oriya, panjabi, tamil, telugu, indonesian, interlingua, irish,
> italian,
> kurmanji, latin, latvian, lithuanian, mongolian, mongolianlmc, bokmal,
> nynorsk,
>   polish, portuguese, romanian, romansh, russian, sanskrit, serbian,
> serbianc, s
> lovak, slovenian, spanish, swedish, turkish, turkmen, ukrainian,
> uppersorbian,
> welsh, loaded.
>
> *(/usr/local/texlive/2012/texmf-dist/tex/latex/base/minimal.cls
> Document Class: minimal 2001/05/25 Standard LaTeX minimal class
> )
> (Please type a command or say `\end')
> *
> *(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3names.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3bootstrap.sty))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/etex-pkg/etex.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/color.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/color.cfg)
> (/usr/local/texlive/2012/texmf-dist/tex/xelatex/xetex-def/xetex.def))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/graphics.cfg))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3basics.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3expan.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3tl.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3seq.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3int.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3quark.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prg.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3clist.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3token.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prop.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3msg.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3file.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3skip.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3keys.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3fp.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3box.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3coffins.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3color.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3luatex.sty))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3packages/xparse/xparse.st
> y)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-patches.s
> ty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/base/fixltx2e.sty)
> *************************************************
> * LaTeX warning: "xparse/redefine-command"
> *
> * Redefining document command \oldstylenums with arg. spec. 'm' on line
> 107.
> *************************************************
> )
> (/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1enc.def)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmr.fd))
> (/usr/local/texlive/2012/texmf-dist/tex/xelatex/xunicode/xunicode.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/tipa/t3enc.def
> (/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmss.fd))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/keyval.sty)))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !
> ! fontspec error: "font-not-found"
> !
> ! The font "Bitstream Vera Serif" cannot be found.
> !
> ! See the fontspec documentation for further information.
> !
> ! For immediate help type H <return>.
> !...............................................
>                                                    
> <*> \setmainfont{Bitstream Vera Serif}
>                                        
> No pages of output.
> Transcript written on texput.log.
>
>
> ======================================================================
> ERROR: matplotlib.tests.test_backend_pgf.test_mixedmode
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/nose/case.py", line 197, in runTest
>      self.test(*self.arg)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/tests/test_backend_pgf.py", line 45, in backend_switcher
>      result = func(*args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/tests/test_backend_pgf.py", line 158, in test_mixedmode
>      compare_figure('pgf_mixedmode.pdf')
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/tests/test_backend_pgf.py", line 56, in compare_figure
>      plt.savefig(actual)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/pyplot.py", line 561, in savefig
>      return fig.savefig(*args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/figure.py", line 1410, in savefig
>      self.canvas.print_figure(*args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backend_bases.py", line 2220, in print_figure
>      **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 865, in print_pdf
>      self._print_pdf_to_fh(fh, *args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 823, in _print_pdf_to_fh
>      self.print_pgf(fname_pgf, *args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 805, in print_pgf
>      self._print_pgf_to_fh(fh, *args, **kwargs)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 785, in _print_pgf_to_fh
>      RendererPgf(self.figure, fh),
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 409, in __init__
>      self.latexManager = LatexManagerFactory.get_latex_manager()
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 223, in get_latex_manager
>      new_inst = LatexManager()
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/backends/backend_pgf.py", line 309, in __init__
>      raise LatexError("LaTeX returned an error, probably missing font or
> error in preamble:\n%s" % stdout)
> LatexError: LaTeX returned an error, probably missing font or error in
> preamble:
> This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012)
>   restricted \write18 enabled.
> **entering extended mode
> LaTeX2e <2011/06/27>
> Babel <v3.8m> and hyphenation patterns for english, dumylang,
> nohyphenation, ge
> rman-x-2012-05-30, ngerman-x-2012-05-30, afrikaans, ancientgreek,
> ibycus, arabi
> c, armenian, basque, bulgarian, catalan, pinyin, coptic, croatian,
> czech, danis
> h, dutch, ukenglish, usenglishmax, esperanto, estonian, ethiopic, farsi,
> finnis
> h, french, friulan, galician, german, ngerman, swissgerman, monogreek,
> greek, h
> ungarian, icelandic, assamese, bengali, gujarati, hindi, kannada,
> malayalam, ma
> rathi, oriya, panjabi, tamil, telugu, indonesian, interlingua, irish,
> italian,
> kurmanji, latin, latvian, lithuanian, mongolian, mongolianlmc, bokmal,
> nynorsk,
>   polish, portuguese, romanian, romansh, russian, sanskrit, serbian,
> serbianc, s
> lovak, slovenian, spanish, swedish, turkish, turkmen, ukrainian,
> uppersorbian,
> welsh, loaded.
>
> *(/usr/local/texlive/2012/texmf-dist/tex/latex/base/minimal.cls
> Document Class: minimal 2001/05/25 Standard LaTeX minimal class
> )
> (Please type a command or say `\end')
> *
> *(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3names.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3bootstrap.sty))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/etex-pkg/etex.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/color.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/color.cfg)
> (/usr/local/texlive/2012/texmf-dist/tex/xelatex/xetex-def/xetex.def))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/graphics.cfg))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3basics.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3expan.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3tl.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3seq.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3int.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3quark.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prg.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3clist.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3token.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prop.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3msg.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3file.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3skip.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3keys.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3fp.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3box.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3coffins.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3color.sty)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3luatex.sty))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/l3packages/xparse/xparse.st
> y)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-patches.s
> ty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/base/fixltx2e.sty)
> *************************************************
> * LaTeX warning: "xparse/redefine-command"
> *
> * Redefining document command \oldstylenums with arg. spec. 'm' on line
> 107.
> *************************************************
> )
> (/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/base/fontenc.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1enc.def)
> (/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmr.fd))
> (/usr/local/texlive/2012/texmf-dist/tex/xelatex/xunicode/xunicode.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/tipa/t3enc.def
> (/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmss.fd))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/keyval.sty)))
> (/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !
> ! fontspec error: "font-not-found"
> !
> ! The font "Bitstream Vera Serif" cannot be found.
> !
> ! See the fontspec documentation for further information.
> !
> ! For immediate help type H <return>.
> !...............................................
>                                                    
> <*> \setmainfont{Bitstream Vera Serif}
>                                        
> No pages of output.
> Transcript written on texput.log.
>
>
> ======================================================================
> ERROR: Failure: NameError (name 'pep8' is not defined)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/nose/loader.py", line 379, in loadTestsFromName
>      module = resolve_name(addr.module)
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/nose/util.py", line 321, in resolve_name
>      module = __import__('.'.join(parts_copy))
>    File
> "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
> kages/matplotlib/tests/test_coding_standards.py", line 18, in <module>
>      class StandardReportWithExclusions(pep8.StandardReport):
> NameError: name 'pep8' is not defined
>
> ----------------------------------------------------------------------
> Ran 1458 tests in 699.485s
>
> FAILED (KNOWNFAIL=2, errors=3)
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/matplotlib/__init__.py:1141: UserWarning:  This call to
> matplotlib.use() has no effect
> because the the backend has already been chosen;
> matplotlib.use() must be called *before* pylab, matplotlib.pyplot,
> or matplotlib.backends is imported for the first time.
>
>    warnings.warn(_use_error_msg)
> localhost$
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Michael D. <md...@st...>]

This appears to be created by setuptools.  I create the tarball using 
`python setup.py sdist`, which is obviously doing this.  I'll look into 
why it's doing this.

Due to this, some of the things that Russell reported, and

https://github.com/matplotlib/matplotlib/pull/2139

there's going to need to be another rc in short order, so stay tuned.

Mike

On 06/19/2013 05:33 PM, Damon McDougall wrote:
>
>
>
> On Wed, Jun 19, 2013 at 4:21 PM, Russell Owen <ro...@uw... 
> <mailto:ro...@uw...>> wrote:
>
>     I found setup.cfg in the 1.3.0rc3 tarball that I downloaded from
>     the usual
>     location:<http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.3.0rc3/matplotlib-1.3.0rc3.tar.gz/download>
>
>
>     Here is the complete contents. None of these entries except
>     [egg_info] appear in setup.cfg.template. However,
>      setup.cfg.template has *NO* entries after [egg_info] which
>     suggests that it could use more documentation.
>
>     --- start setup.cfg ----
>     [egg_info]
>     tag_build =
>     tag_date = 0
>     tag_svn_revision = 0
>
>     --- end setup.cfg ----
>
>
> Ah, I see it now.
>
> It looks like something that was put in automatically, but I doubt 
> it's git.
>
> Mike, did you do the standard git archive --format=tar v1.3.0rc3 | 
> gzip > foo.tar.gz ?  I'd be surprised if that futzed with the tree...
>
>
>
>     -- Russell
>
>
>     On Jun 19, 2013, at 2:13 PM, Damon McDougall
>     <dam...@gm... <mailto:dam...@gm...>> wrote:
>
>>
>>
>>
>>     On Wed, Jun 19, 2013 at 2:29 PM, Russell E. Owen <ro...@uw...
>>     <mailto:ro...@uw...>> wrote:
>>
>>         In article <51C...@st...
>>         <mailto:51C...@st...>>,
>>          Michael Droettboom <md...@st... <mailto:md...@st...>>
>>          wrote:
>>
>>         > I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
>>         >
>>         > We may not get all the binaries up in the next little
>>         while, so I'll
>>         > wait for those and then make an announcement on
>>         matplotlib-users.  After
>>         > a couple of weeks, assuming no serious problems, we'll be
>>         ready for
>>         > 1.3.0 final.
>>         >
>>         > Thanks again to everyone for their help with this release!
>>         >
>>         > Mike
>>
>>         Why does the distro include a setup.cfg, and why does it bear no
>>         resemblance to setup.cfg.template? (setup.cfg has just a few
>>         lines, and
>>         none of them are described in setup.cfg.template)
>>
>>
>>     I don't see a setup.cfg file.  I'm looking here:
>>     https://github.com/matplotlib/matplotlib/tree/v1.3.x
>>
>>     All I see is the setup.cfg.template file.
>>
>>
>>         -- Russell
>>
>>
>>         ------------------------------------------------------------------------------
>>         This SF.net <http://SF.net> email is sponsored by Windows:
>>
>>         Build for Windows Store.
>>
>>         http://p.sf.net/sfu/windows-dev2dev
>>         _______________________________________________
>>         Matplotlib-devel mailing list
>>         Mat...@li...
>>         <mailto:Mat...@li...>
>>         https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
>>
>>
>>     -- 
>>     Damon McDougall
>>     http://www.damon-is-a-geek.com <http://www.damon-is-a-geek.com/>
>>     Institute for Computational Engineering Sciences
>>     201 E. 24th St.
>>     Stop C0200
>>     The University of Texas at Austin
>>     Austin, TX 78712-1229
>
>
>
>
> -- 
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Damon M. <dam...@gm...>]

On Wed, Jun 19, 2013 at 4:21 PM, Russell Owen <ro...@uw...> wrote:

> I found setup.cfg in the 1.3.0rc3 tarball that I downloaded from the usual
> location:<
> http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.3.0rc3/matplotlib-1.3.0rc3.tar.gz/download
> >
>
> Here is the complete contents. None of these entries except [egg_info]
> appear in setup.cfg.template. However,  setup.cfg.template has *NO* entries
> after [egg_info] which suggests that it could use more documentation.
>
> --- start setup.cfg ----
> [egg_info]
> tag_build =
> tag_date = 0
> tag_svn_revision = 0
>
> --- end setup.cfg ----
>

Ah, I see it now.

It looks like something that was put in automatically, but I doubt it's git.

Mike, did you do the standard git archive --format=tar v1.3.0rc3 | gzip >
foo.tar.gz ?  I'd be surprised if that futzed with the tree...


>
>
> -- Russell
>
>
> On Jun 19, 2013, at 2:13 PM, Damon McDougall <dam...@gm...>
> wrote:
>
>
>
>
> On Wed, Jun 19, 2013 at 2:29 PM, Russell E. Owen <ro...@uw...> wrote:
>
>> In article <51C...@st...>,
>>  Michael Droettboom <md...@st...>
>>  wrote:
>>
>> > I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
>> >
>> > We may not get all the binaries up in the next little while, so I'll
>> > wait for those and then make an announcement on matplotlib-users.  After
>> > a couple of weeks, assuming no serious problems, we'll be ready for
>> > 1.3.0 final.
>> >
>> > Thanks again to everyone for their help with this release!
>> >
>> > Mike
>>
>> Why does the distro include a setup.cfg, and why does it bear no
>> resemblance to setup.cfg.template? (setup.cfg has just a few lines, and
>> none of them are described in setup.cfg.template)
>>
>
> I don't see a setup.cfg file.  I'm looking here:
> https://github.com/matplotlib/matplotlib/tree/v1.3.x
>
> All I see is the setup.cfg.template file.
>
>
>>
>> -- Russell
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
>
>
> --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
>


-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Damon M. <dam...@gm...>]

On Wed, Jun 19, 2013 at 2:29 PM, Russell E. Owen <ro...@uw...> wrote:

> In article <51C...@st...>,
>  Michael Droettboom <md...@st...>
>  wrote:
>
> > I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
> >
> > We may not get all the binaries up in the next little while, so I'll
> > wait for those and then make an announcement on matplotlib-users.  After
> > a couple of weeks, assuming no serious problems, we'll be ready for
> > 1.3.0 final.
> >
> > Thanks again to everyone for their help with this release!
> >
> > Mike
>
> Why does the distro include a setup.cfg, and why does it bear no
> resemblance to setup.cfg.template? (setup.cfg has just a few lines, and
> none of them are described in setup.cfg.template)
>

I don't see a setup.cfg file.  I'm looking here:
https://github.com/matplotlib/matplotlib/tree/v1.3.x

All I see is the setup.cfg.template file.


>
> -- Russell
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>



-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Russell E. O. <ro...@uw...>]

In article <51C...@st...>,
 Michael Droettboom <md...@st...> 
 wrote:

> I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
> 
> We may not get all the binaries up in the next little while, so I'll 
> wait for those and then make an announcement on matplotlib-users.  After 
> a couple of weeks, assuming no serious problems, we'll be ready for 
> 1.3.0 final.
> 
> Thanks again to everyone for their help with this release!

I have uploaded the MacOS 10.6 64-bit binary. However, there were a few 
unit test failures, including the font complaint that I first saw in an 
earlier 1.3.0 prerelease, plus one about pep8 that I've never seen 
before.

I have appended the output from python -c "import matplotlib as m ; 
m.test(verbosity=1)"

-- Russell

Last login: Wed Jun 19 12:36:54 on ttys001
localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)"
.........................................................................
.........................................................................
.........................................................................
..........kpathsea: Invalid fontname `Bitstream Vera Serif', contains ' '
Ekpathsea: Invalid fontname `Bitstream Vera Serif', contains ' '
EK.....K.................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
...................................../Library/Frameworks/Python.framework
/Versions/2.7/lib/python2.7/site-packages/numpy/ma/core.py:777: 
RuntimeWarning: invalid value encountered in absolute
  return umath.absolute(a) * self.tolerance >= umath.absolute(b)
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/ma/core.py:3791: UserWarning: Warning: converting a masked 
element to nan.
  warnings.warn("Warning: converting a masked element to nan.")
.........................................../Library/Frameworks/Python.fra
mework/Versions/2.7/lib/python2.7/site-packages/matplotlib/gridspec.py:29
8: UserWarning: This figure includes Axes that are not compatible with 
tight_layout, so its results might be incorrect.
  warnings.warn("This figure includes Axes that are not "
............................................/Library/Frameworks/Python.fr
amework/Versions/2.7/lib/python2.7/site-packages/numpy/testing/utils.py:8
07: RuntimeWarning: invalid value encountered in absolute
  z = abs(x-y)
........E
======================================================================
ERROR: matplotlib.tests.test_backend_pgf.test_pathclip
----------------------------------------------------------------------
Traceback (most recent call last):
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/tests/test_backend_pgf.py", line 45, in backend_switcher
    result = func(*args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/tests/test_backend_pgf.py", line 146, in test_pathclip
    plt.savefig(os.path.join(result_dir, "pgf_pathclip.pdf"))
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/pyplot.py", line 561, in savefig
    return fig.savefig(*args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/figure.py", line 1410, in savefig
    self.canvas.print_figure(*args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backend_bases.py", line 2220, in print_figure
    **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 865, in print_pdf
    self._print_pdf_to_fh(fh, *args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 823, in _print_pdf_to_fh
    self.print_pgf(fname_pgf, *args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 805, in print_pgf
    self._print_pgf_to_fh(fh, *args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 785, in _print_pgf_to_fh
    RendererPgf(self.figure, fh),
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 409, in __init__
    self.latexManager = LatexManagerFactory.get_latex_manager()
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 223, in get_latex_manager
    new_inst = LatexManager()
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 309, in __init__
    raise LatexError("LaTeX returned an error, probably missing font or 
error in preamble:\n%s" % stdout)
LatexError: LaTeX returned an error, probably missing font or error in 
preamble:
This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012)
 restricted \write18 enabled.
**entering extended mode
LaTeX2e <2011/06/27>
Babel <v3.8m> and hyphenation patterns for english, dumylang, 
nohyphenation, ge
rman-x-2012-05-30, ngerman-x-2012-05-30, afrikaans, ancientgreek, 
ibycus, arabi
c, armenian, basque, bulgarian, catalan, pinyin, coptic, croatian, 
czech, danis
h, dutch, ukenglish, usenglishmax, esperanto, estonian, ethiopic, farsi, 
finnis
h, french, friulan, galician, german, ngerman, swissgerman, monogreek, 
greek, h
ungarian, icelandic, assamese, bengali, gujarati, hindi, kannada, 
malayalam, ma
rathi, oriya, panjabi, tamil, telugu, indonesian, interlingua, irish, 
italian, 
kurmanji, latin, latvian, lithuanian, mongolian, mongolianlmc, bokmal, 
nynorsk,
 polish, portuguese, romanian, romansh, russian, sanskrit, serbian, 
serbianc, s
lovak, slovenian, spanish, swedish, turkish, turkmen, ukrainian, 
uppersorbian, 
welsh, loaded.

*(/usr/local/texlive/2012/texmf-dist/tex/latex/base/minimal.cls
Document Class: minimal 2001/05/25 Standard LaTeX minimal class
)
(Please type a command or say `\end')
*
*(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3names.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3bootstrap.sty))
(/usr/local/texlive/2012/texmf-dist/tex/latex/etex-pkg/etex.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/color.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/color.cfg)
(/usr/local/texlive/2012/texmf-dist/tex/xelatex/xetex-def/xetex.def))
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/graphics.cfg))
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3basics.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3expan.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3tl.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3seq.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3int.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3quark.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prg.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3clist.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3token.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prop.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3msg.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3file.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3skip.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3keys.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3fp.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3box.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3coffins.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3color.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3luatex.sty))
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3packages/xparse/xparse.st
y)
(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-patches.s
ty
(/usr/local/texlive/2012/texmf-dist/tex/latex/base/fixltx2e.sty)
*************************************************
* LaTeX warning: "xparse/redefine-command"
* 
* Redefining document command \oldstylenums with arg. spec. 'm' on line 
107.
*************************************************
) 
(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/base/fontenc.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1enc.def)
(/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmr.fd))
(/usr/local/texlive/2012/texmf-dist/tex/xelatex/xunicode/xunicode.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/tipa/t3enc.def
(/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmss.fd))
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/keyval.sty)))
(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.cfg)))

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! fontspec error: "font-not-found"
! 
! The font "Bitstream Vera Serif" cannot be found.
! 
! See the fontspec documentation for further information.
! 
! For immediate help type H <return>.
!...............................................  
                                                  
<*> \setmainfont{Bitstream Vera Serif}
                                      
No pages of output.
Transcript written on texput.log.


======================================================================
ERROR: matplotlib.tests.test_backend_pgf.test_mixedmode
----------------------------------------------------------------------
Traceback (most recent call last):
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/tests/test_backend_pgf.py", line 45, in backend_switcher
    result = func(*args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/tests/test_backend_pgf.py", line 158, in test_mixedmode
    compare_figure('pgf_mixedmode.pdf')
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/tests/test_backend_pgf.py", line 56, in compare_figure
    plt.savefig(actual)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/pyplot.py", line 561, in savefig
    return fig.savefig(*args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/figure.py", line 1410, in savefig
    self.canvas.print_figure(*args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backend_bases.py", line 2220, in print_figure
    **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 865, in print_pdf
    self._print_pdf_to_fh(fh, *args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 823, in _print_pdf_to_fh
    self.print_pgf(fname_pgf, *args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 805, in print_pgf
    self._print_pgf_to_fh(fh, *args, **kwargs)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 785, in _print_pgf_to_fh
    RendererPgf(self.figure, fh),
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 409, in __init__
    self.latexManager = LatexManagerFactory.get_latex_manager()
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 223, in get_latex_manager
    new_inst = LatexManager()
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/backends/backend_pgf.py", line 309, in __init__
    raise LatexError("LaTeX returned an error, probably missing font or 
error in preamble:\n%s" % stdout)
LatexError: LaTeX returned an error, probably missing font or error in 
preamble:
This is XeTeX, Version 3.1415926-2.4-0.9998 (TeX Live 2012)
 restricted \write18 enabled.
**entering extended mode
LaTeX2e <2011/06/27>
Babel <v3.8m> and hyphenation patterns for english, dumylang, 
nohyphenation, ge
rman-x-2012-05-30, ngerman-x-2012-05-30, afrikaans, ancientgreek, 
ibycus, arabi
c, armenian, basque, bulgarian, catalan, pinyin, coptic, croatian, 
czech, danis
h, dutch, ukenglish, usenglishmax, esperanto, estonian, ethiopic, farsi, 
finnis
h, french, friulan, galician, german, ngerman, swissgerman, monogreek, 
greek, h
ungarian, icelandic, assamese, bengali, gujarati, hindi, kannada, 
malayalam, ma
rathi, oriya, panjabi, tamil, telugu, indonesian, interlingua, irish, 
italian, 
kurmanji, latin, latvian, lithuanian, mongolian, mongolianlmc, bokmal, 
nynorsk,
 polish, portuguese, romanian, romansh, russian, sanskrit, serbian, 
serbianc, s
lovak, slovenian, spanish, swedish, turkish, turkmen, ukrainian, 
uppersorbian, 
welsh, loaded.

*(/usr/local/texlive/2012/texmf-dist/tex/latex/base/minimal.cls
Document Class: minimal 2001/05/25 Standard LaTeX minimal class
)
(Please type a command or say `\end')
*
*(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3names.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3bootstrap.sty))
(/usr/local/texlive/2012/texmf-dist/tex/latex/etex-pkg/etex.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/color.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/color.cfg)
(/usr/local/texlive/2012/texmf-dist/tex/xelatex/xetex-def/xetex.def))
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/latexconfig/graphics.cfg))
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3basics.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3expan.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3tl.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3seq.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3int.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3quark.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prg.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3clist.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3token.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3prop.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3msg.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3file.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3skip.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3keys.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3fp.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3box.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3coffins.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3color.sty)
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3kernel/l3luatex.sty))
(/usr/local/texlive/2012/texmf-dist/tex/latex/l3packages/xparse/xparse.st
y)
(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-patches.s
ty
(/usr/local/texlive/2012/texmf-dist/tex/latex/base/fixltx2e.sty)
*************************************************
* LaTeX warning: "xparse/redefine-command"
* 
* Redefining document command \oldstylenums with arg. spec. 'm' on line 
107.
*************************************************
) 
(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/base/fontenc.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1enc.def)
(/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmr.fd))
(/usr/local/texlive/2012/texmf-dist/tex/xelatex/xunicode/xunicode.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/tipa/t3enc.def
(/usr/local/texlive/2012/texmf-dist/tex/latex/euenc/eu1lmss.fd))
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/local/texlive/2012/texmf-dist/tex/latex/graphics/keyval.sty)))
(/usr/local/texlive/2012/texmf-dist/tex/latex/fontspec/fontspec.cfg)))

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! fontspec error: "font-not-found"
! 
! The font "Bitstream Vera Serif" cannot be found.
! 
! See the fontspec documentation for further information.
! 
! For immediate help type H <return>.
!...............................................  
                                                  
<*> \setmainfont{Bitstream Vera Serif}
                                      
No pages of output.
Transcript written on texput.log.


======================================================================
ERROR: Failure: NameError (name 'pep8' is not defined)
----------------------------------------------------------------------
Traceback (most recent call last):
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/nose/loader.py", line 379, in loadTestsFromName
    module = resolve_name(addr.module)
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/nose/util.py", line 321, in resolve_name
    module = __import__('.'.join(parts_copy))
  File 
"/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pac
kages/matplotlib/tests/test_coding_standards.py", line 18, in <module>
    class StandardReportWithExclusions(pep8.StandardReport):
NameError: name 'pep8' is not defined

----------------------------------------------------------------------
Ran 1458 tests in 699.485s

FAILED (KNOWNFAIL=2, errors=3)
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/matplotlib/__init__.py:1141: UserWarning:  This call to 
matplotlib.use() has no effect
because the the backend has already been chosen;
matplotlib.use() must be called *before* pylab, matplotlib.pyplot,
or matplotlib.backends is imported for the first time.

  warnings.warn(_use_error_msg)
localhost$

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Russell E. O. <ro...@uw...>]

In article <51C...@st...>,
 Michael Droettboom <md...@st...> 
 wrote:

> I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
> 
> We may not get all the binaries up in the next little while, so I'll 
> wait for those and then make an announcement on matplotlib-users.  After 
> a couple of weeks, assuming no serious problems, we'll be ready for 
> 1.3.0 final.
> 
> Thanks again to everyone for their help with this release!
> 
> Mike

Why does the distro include a setup.cfg, and why does it bear no 
resemblance to setup.cfg.template? (setup.cfg has just a few lines, and 
none of them are described in setup.cfg.template)

-- Russell

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

[Michael D. <md...@st...>]

Just to close the loop on this, I have created:

https://github.com/matplotlib/matplotlib/pull/2139

On 06/18/2013 07:18 PM, Fernando Perez wrote:
> Good point, I didn't know about that new mechanism.
>
> I think we should keep 2.6 support for IPython 1.0, but drop it
> afterwards. We can discuss that during the dev meeting...
>
> Cheers,
>
> f
>
> On Tue, Jun 18, 2013 at 4:16 PM, Thomas Kluyver <th...@kl...> wrote:
>> On 19 June 2013 00:09, Fernando Perez <fpe...@gm...> wrote:
>>> I wish we could just fix this plugin issue.
>>
>> When we drop support for Python 2.6, I think we can use the expectedFailure
>> mechanism included in unittest from 2.7 onwards. So long as nose recognises
>> that, we should be able to drop our copy of the KnownFailure plugin.
>>
>> Thomas
>
>

Re: [matplotlib-devel] Weird KnownFailure problem in IPython test suite with mpl master

[Michael D. <md...@st...>]

On 06/18/2013 07:09 PM, Fernando Perez wrote:
> Hi Mike,
>
> On Tue, Jun 18, 2013 at 3:37 PM, Michael Droettboom <md...@st...> wrote:
>> This was an attempt to fix a bug that mpl's KnownFailure plugin wouldn't
>> load when running tests directly using the nosetests commandline
>> script.  I see IPython has a testing wrapper script (iptest) -- is that
>> in part to solve that problem?
> Only in part. We wrote iptest because we need to start nose multiple
> times in different subprocesses for each chunk of IPython, as trying
> to load all of IPython into a single python process ends up producing
> tears (conflicts between things that don't like to live together in
> sys.modules like multiple gui toolkits, etc).

We are likely to have to do the same thing in the near future -- we 
already have to spawn subprocesses in the setup script because we can't, 
for example, import pygtk (classic) and pygi (the new hotness) in the 
same process.

>
>> In any case, the revert should be simple -- can you try commenting out
>> the "entry_points" kwarg at the bottom of the setup.py script?  (You'll
>> probably need to blitz the matplotlib installation directory and `build`
>> for good measure).  I can't actually reproduce the bug myself, but I
>> suspect that's because this is somewhat dependent on the order in which
>> things are installed into the virtualenv or the phases of the moon...
> Yup, problem gone. With this change:
>
> ((v1.3.0rc3))longs[matplotlib]> git diff
> diff --git a/setup.py b/setup.py
> index 5f1b561..b4d1763 100644
> --- a/setup.py
> +++ b/setup.py
> @@ -230,9 +230,9 @@ if __name__ == '__main__':
>             zip_safe=False,
>
>             # Install our nose plugin so it will always be found
> -          entry_points={
> -              'nose.plugins.0.10': [
> -                  'KnownFailure = matplotlib.testing.noseclasses:KnownFailure'
> -                ]
> -            },
> +         # entry_points={
> +         #     'nose.plugins.0.10': [
> +         #         'KnownFailure = matplotlib.testing.noseclasses:KnownFailure'
> +         #       ]
> +         #   },
>            )
>
> I get as expected:
>
> ((v1.3.0rc3))longs[matplotlib]> iptest -vx IPython.core.tests.test_run
>
> [...]
>
> ----------------------------------------------------------------------
> Ran 23 tests in 2.277s
>
> OK (KNOWNFAIL=1)
>
>> If that works for you, we can just take that out and require testers to
>> use our testing script (and unfortunately will have to make another
>> release candidate).
> Well, I wouldn't want to force mpl to have to ship a custom testing
> script, that's kind of an ugly kludge that we live with but that is
> really sub-optimal.  I wish we could just fix this plugin issue. The
> problem, I suspect, is the presence of multiple KnownFailure classes
> in a way that trips an isisnstance() check somewhere.

Well, this wouldn't be anything new.  The 1.2 series (and I think as far 
back as we've had nosetests) requires this already, I was just hoping 
this would be a solution to that.

I think I'm fine with just taking this out for 1.3.0 and, as Thomas 
Kluyver suggested, dealing with this properly once we drop support for 
Python 2.6.

Cheers,
Mike

>
> Cheers,
>
> f

Re: [matplotlib-devel] matplotlib 1.3.0rc3 tomorrow

[Damon M. <dam...@gm...>]

On Tue, Jun 18, 2013 at 2:20 PM, Michael Droettboom <md...@st...> wrote:

>  I have tagged a 1.3.0rc3 and uploaded a tarball to Sourceforge.
>
> We may not get all the binaries up in the next little while, so I'll wait
> for those and then make an announcement on matplotlib-users.  After a
> couple of weeks, assuming no serious problems, we'll be ready for 1.3.0
> final.
>

Russell, I see you seem to have had no issues (except for some warnings)
building the earlier 1.3 release candidates.  That said, let me know if I
can do anything to help.


>
> Thanks again to everyone for their help with this release!
>

> Mike
>
>
> On 06/17/2013 02:53 PM, Damon McDougall wrote:
>
>
>
>
> On Mon, Jun 17, 2013 at 9:50 AM, Michael Droettboom <md...@st...>wrote:
>
>> We're a little behind schedule for 1.3.0 -- held up by the
>> distribute/setuptools upgrade debacle.  I'd like to put out a 1.3.0rc3
>> late tonight or tomorrow, and hopefully get a final release out early
>> next week in advance of Scipy if all goes well.  Any objections?
>>
>
>  I'm too far behind on my email to be apprised of the state of distribute
> vs setuptools.  I trust your judgement :)
>
>
>>
>> Mike
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Windows:
>>
>> Build for Windows Store.
>>
>> http://p.sf.net/sfu/windows-dev2dev
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
>
>
>  --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
>


-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229