[matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 
I'm pleased to announce the tagging of matplotlib-1.3.0rc1.

Once the binaries from Christoph and Russell have been uploaded, I'll 
make a broader announcement to get some testing of this in advance of 
the final release.

The tarball is available here:

https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz

The documentation for this version is viewable here:

http://matplotlib.org/1.3.0

Thanks everyone for their hard work getting this out the door!

Mike

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Christoph Gohlke 
Hi,

minor issue: the tarball contains a lib\matplotlib.egg-info directory. 
The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and therefore 
fails to build on my system. Deleting the lib\matplotlib.egg-info folder 
works.

Does the release announcement mention that Windows binaries won't 
include required dependencies (pytz, dateutil, pyparsing, six) any longer?

Christoph


On 5/29/2013 11:41 AM, Michael Droettboom wrote:
> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>
> Once the binaries from Christoph and Russell have been uploaded, I'll
> make a broader announcement to get some testing of this in advance of
> the final release.
>
> The tarball is available here:
>
> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>
>
> The documentation for this version is viewable here:
>
> http://matplotlib.org/1.3.0
>
> Thanks everyone for their hard work getting this out the door!
>
> Mike
>

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 
On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
> Hi,
>
> minor issue: the tarball contains a lib\matplotlib.egg-info directory. 
> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and 
> therefore fails to build on my system. Deleting the 
> lib\matplotlib.egg-info folder works.

Doh.  This is the first time building with setuptools -- I'll fix that 
and create a new tarball...  1.3.0rc2 here we come!
>
> Does the release announcement mention that Windows binaries won't 
> include required dependencies (pytz, dateutil, pyparsing, six) any 
> longer?

Yes. http://matplotlib.org/1.3.0/users/whats_new.html#new-setup-script
>
> Christoph
>
>
> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>
>> Once the binaries from Christoph and Russell have been uploaded, I'll
>> make a broader announcement to get some testing of this in advance of
>> the final release.
>>
>> The tarball is available here:
>>
>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>>  
>>
>>
>>
>> The documentation for this version is viewable here:
>>
>> http://matplotlib.org/1.3.0
>>
>> Thanks everyone for their hard work getting this out the door!
>>
>> Mike
>>


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 
It seems that in the setuptools way [TM] it is rather difficult to not 
include this folder.  Does it work if you only remove those hardcoded 
paths?  It should be easy for me to fix that by not having it search for 
system libraries when building a tarball.

Mike

On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
> Hi,
>
> minor issue: the tarball contains a lib\matplotlib.egg-info directory. 
> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and 
> therefore fails to build on my system. Deleting the 
> lib\matplotlib.egg-info folder works.
>
> Does the release announcement mention that Windows binaries won't 
> include required dependencies (pytz, dateutil, pyparsing, six) any 
> longer?
>
> Christoph
>
>
> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>
>> Once the binaries from Christoph and Russell have been uploaded, I'll
>> make a broader announcement to get some testing of this in advance of
>> the final release.
>>
>> The tarball is available here:
>>
>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>>  
>>
>>
>>
>> The documentation for this version is viewable here:
>>
>> http://matplotlib.org/1.3.0
>>
>> Thanks everyone for their hard work getting this out the door!
>>
>> Mike
>>


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Christoph Gohlke 
Removing the hardcoded paths works.

I noticed two more build issues.

1) On Python 3.x I see the following errors/warnings, however the build 
succeeds.

```
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py 
line 1265: ParseError: bad token: type=55, value="'", context=('', 
(1265, 38))
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py line 
3344: TokenError: ('EOF in multi-line statement', (2, 0))
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py line 
3345: ParseError: bad input: type=5, value='  ', 
context=('\n\n\n\n', (3345, 0))
Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py line 
3346: ParseError: bad input: type=5, value='  ', 
context=('\n\n\n\n', (3346, 0))
Can't parse docstring in 
build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322: 
TokenError: ('EOF in multi-line statement', (2, 0))
```

2) On Python 2.6 with distribute-0.6.45, the build fails during 
packaging. See 

Christoph


On 5/29/2013 12:08 PM, Michael Droettboom wrote:
> It seems that in the setuptools way [TM] it is rather difficult to not
> include this folder.  Does it work if you only remove those hardcoded
> paths?  It should be easy for me to fix that by not having it search for
> system libraries when building a tarball.
>
> Mike
>
> On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
>> Hi,
>>
>> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
>> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
>> therefore fails to build on my system. Deleting the
>> lib\matplotlib.egg-info folder works.
>>
>> Does the release announcement mention that Windows binaries won't
>> include required dependencies (pytz, dateutil, pyparsing, six) any
>> longer?
>>
>> Christoph
>>
>>
>> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>>
>>> Once the binaries from Christoph and Russell have been uploaded, I'll
>>> make a broader announcement to get some testing of this in advance of
>>> the final release.
>>>
>>> The tarball is available here:
>>>
>>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>>>
>>>
>>>
>>> The documentation for this version is viewable here:
>>>
>>> http://matplotlib.org/1.3.0
>>>
>>> Thanks everyone for their hard work getting this out the door!
>>>
>>> Mike
>>>
>

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 
On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
> Removing the hardcoded paths works.
>
> I noticed two more build issues.
>
> 1) On Python 3.x I see the following errors/warnings, however the 
> build succeeds.
>
> ```
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py 
> line 1265: ParseError: bad token: type=55, value="'", context=('', 
> (1265, 38))
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py 
> line 3344: TokenError: ('EOF in multi-line statement', (2, 0))
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py 
> line 3345: ParseError: bad input: type=5, value='  ', 
> context=('\n\n\n\n', (3345, 0))
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py 
> line 3346: ParseError: bad input: type=5, value='  ', 
> context=('\n\n\n\n', (3346, 0))
> Can't parse docstring in 
> build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322: 
> TokenError: ('EOF in multi-line statement', (2, 0))
> ```

While annoying, I think these are benign --- the 2to3 tool is tripping 
up on these docstrings.  Overtime, the docstrings will get rewritten in 
numpydoc format and we *might* see these go away.

>
> 2) On Python 2.6 with distribute-0.6.45, the build fails during 
> packaging. See 

Good catch.  Thanks.

Mike
>
> Christoph
>
>
> On 5/29/2013 12:08 PM, Michael Droettboom wrote:
>> It seems that in the setuptools way [TM] it is rather difficult to not
>> include this folder.  Does it work if you only remove those hardcoded
>> paths?  It should be easy for me to fix that by not having it search for
>> system libraries when building a tarball.
>>
>> Mike
>>
>> On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
>>> Hi,
>>>
>>> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
>>> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
>>> therefore fails to build on my system. Deleting the
>>> lib\matplotlib.egg-info folder works.
>>>
>>> Does the release announcement mention that Windows binaries won't
>>> include required dependencies (pytz, dateutil, pyparsing, six) any
>>> longer?
>>>
>>> Christoph
>>>
>>>
>>> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
 I'm pleased to announce the tagging of matplotlib-1.3.0rc1.

 Once the binaries from Christoph and Russell have been uploaded, I'll
 make a broader announcement to get some testing of this in advance of
 the final release.

 The tarball is available here:

 https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
  




 The documentation for this version is viewable here:

 http://matplotlib.org/1.3.0

 Thanks everyone for their hard work getting this out the door!

 Mike

>>


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 
Ok, folks.  1.3.0rc2 is here:

https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc2/matplotlib-1.3.0rc2.tar.gz


Mike



On 05/29/2013 03:41 PM, Michael Droettboom wrote:
> On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
>> Removing the hardcoded paths works.
>>
>> I noticed two more build issues.
>>
>> 1) On Python 3.x I see the following errors/warnings, however the
>> build succeeds.
>>
>> ```
>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py
>> line 1265: ParseError: bad token: type=55, value="'", context=('',
>> (1265, 38))
>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
>> line 3344: TokenError: ('EOF in multi-line statement', (2, 0))
>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
>> line 3345: ParseError: bad input: type=5, value='  ',
>> context=('\n\n\n\n', (3345, 0))
>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
>> line 3346: ParseError: bad input: type=5, value='  ',
>> context=('\n\n\n\n', (3346, 0))
>> Can't parse docstring in
>> build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322:
>> TokenError: ('EOF in multi-line statement', (2, 0))
>> ```
> While annoying, I think these are benign --- the 2to3 tool is tripping
> up on these docstrings.  Overtime, the docstrings will get rewritten in
> numpydoc format and we *might* see these go away.
>
>> 2) On Python 2.6 with distribute-0.6.45, the build fails during
>> packaging. See 
> Good catch.  Thanks.
>
> Mike
>> Christoph
>>
>>
>> On 5/29/2013 12:08 PM, Michael Droettboom wrote:
>>> It seems that in the setuptools way [TM] it is rather difficult to not
>>> include this folder.  Does it work if you only remove those hardcoded
>>> paths?  It should be easy for me to fix that by not having it search for
>>> system libraries when building a tarball.
>>>
>>> Mike
>>>
>>> On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
 Hi,

 minor issue: the tarball contains a lib\matplotlib.egg-info directory.
 The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
 therefore fails to build on my system. Deleting the
 lib\matplotlib.egg-info folder works.

 Does the release announcement mention that Windows binaries won't
 include required dependencies (pytz, dateutil, pyparsing, six) any
 longer?

 Christoph


 On 5/29/2013 11:41 AM, Michael Droettboom wrote:
> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>
> Once the binaries from Christoph and Russell have been uploaded, I'll
> make a broader announcement to get some testing of this in advance of
> the final release.
>
> The tarball is available here:
>
> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>
>
>
>
> The documentation for this version is viewable here:
>
> http://matplotlib.org/1.3.0
>
> Thanks everyone for their hard work getting this out the door!
>
> Mike
>
>
> --
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] A generous donation of $10, 000 from Simula/Hans Petter Langtangen via NumFOCUS

2013-05-29 Thread Fernando Perez 
Hi all,

I just wanted to let you all know that Hans Petter Langtangen,
well-known author of books on scientific Python and long-time champion
of these tools at the University of Oslo for many years, has arranged
for a donation of $10,000 to support matplotlib's development.

Hans Petter is the Director of the Center for Biomedical Computing at
Simula (http://home.simula.no/~hpl), where a number of projects use
Python as key elements of their research, the Fenics platform being
among the most well-known (http://fenicsproject.org).

We have now confirmed that these funds have been transferred to the
NumFOCUS donations account, where Michael and the rest of the team can
make use of them.

I wanted to publicly thank Hans Petter and Simula Labs for
persistently jumping through the necessary hoops to make this
possible, and to Leah, Travis and Anthony at NumFOCUS for managing the
receiving side of things.

--
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

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Christoph Gohlke 
Sorry, but that tarball does not include setup.py and other files. It is 
only ~25 MB.

Christoph


On 5/29/2013 12:48 PM, Michael Droettboom wrote:
> Ok, folks.  1.3.0rc2 is here:
>
> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc2/matplotlib-1.3.0rc2.tar.gz
>
>
> Mike
>
>
>
> On 05/29/2013 03:41 PM, Michael Droettboom wrote:
>> On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
>>> Removing the hardcoded paths works.
>>>
>>> I noticed two more build issues.
>>>
>>> 1) On Python 3.x I see the following errors/warnings, however the
>>> build succeeds.
>>>
>>> ```
>>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py
>>> line 1265: ParseError: bad token: type=55, value="'", context=('',
>>> (1265, 38))
>>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
>>> line 3344: TokenError: ('EOF in multi-line statement', (2, 0))
>>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
>>> line 3345: ParseError: bad input: type=5, value='  ',
>>> context=('\n\n\n\n', (3345, 0))
>>> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
>>> line 3346: ParseError: bad input: type=5, value='  ',
>>> context=('\n\n\n\n', (3346, 0))
>>> Can't parse docstring in
>>> build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322:
>>> TokenError: ('EOF in multi-line statement', (2, 0))
>>> ```
>> While annoying, I think these are benign --- the 2to3 tool is tripping
>> up on these docstrings.  Overtime, the docstrings will get rewritten in
>> numpydoc format and we *might* see these go away.
>>
>>> 2) On Python 2.6 with distribute-0.6.45, the build fails during
>>> packaging. See 
>> Good catch.  Thanks.
>>
>> Mike
>>> Christoph
>>>
>>>
>>> On 5/29/2013 12:08 PM, Michael Droettboom wrote:
 It seems that in the setuptools way [TM] it is rather difficult to not
 include this folder.  Does it work if you only remove those hardcoded
 paths?  It should be easy for me to fix that by not having it search for
 system libraries when building a tarball.

 Mike

 On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
> Hi,
>
> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
> therefore fails to build on my system. Deleting the
> lib\matplotlib.egg-info folder works.
>
> Does the release announcement mention that Windows binaries won't
> include required dependencies (pytz, dateutil, pyparsing, six) any
> longer?
>
> Christoph
>
>
> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>
>> Once the binaries from Christoph and Russell have been uploaded, I'll
>> make a broader announcement to get some testing of this in advance of
>> the final release.
>>
>> The tarball is available here:
>>
>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>>
>>
>>
>>
>> The documentation for this version is viewable here:
>>
>> http://matplotlib.org/1.3.0
>>
>> Thanks everyone for their hard work getting this out the door!
>>
>> Mike
>>
>>
>> --
>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>> Get 100% visibility into your production application - at no cost.
>> Code-level diagnostics for performance bottlenecks with <2% overhead
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap1
>> ___
>> Matplotlib-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
> --
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Russell E. Owen 
In article <[email protected]>,
 Michael Droettboom  
 wrote:

> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
> 
> Once the binaries from Christoph and Russell have been uploaded, I'll 
> make a broader announcement to get some testing of this in advance of 
> the final release.
> 
> The tarball is available here:
> 
> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3
> .0rc1/matplotlib-1.3.0rc1.tar.gz
> 
> The documentation for this version is viewable here:
> 
> http://matplotlib.org/1.3.0
> 
> Thanks everyone for their hard work getting this out the door!

It looks like the ability to include pytz and other dependencies in 
binary distributions has been removed?

Is this really what we want? In the past we always included them. 
Excluding them certainly makes sense if using pip or a similar installer 
that can handle dependencies, but that is not the case for binaries.

I guess we could serve the associated packages (pytz, dateutil and six), 
or if they can be installed by pip, ask users to install those. But 
users using binary installers may not even have pip available, so it's a 
big initial hurdle.

I'd personally be happier reverting to the old system. Sorry if I missed 
a discussion on this.

-- Russell


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Closing in on 1.3.0 release candidate

2013-05-29 Thread Russell E. Owen 
In article <[email protected]>,
 Michael Droettboom  
 wrote:

> I am going to hold off one more day on making the release candidate.  
> There are three blocker bugs that were discovered over the weekend and 
> I'd like to give them a chance for review first:...

Thanks for the update.

The Mac version built fine, but I saw several warnings. The only one I'm 
worried about is use of a deprecated Numpy API:

In file included from src/_backend_agg.cpp:12:
In file included from src/_backend_agg.h:43:
In file included from src/agg_py_path_iterator.h:7:
In file included from 
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/core/include/numpy/arrayobject.h:15:
In file included from 
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/core/include/numpy/ndarrayobject.h:17:
In file included from 
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/core/include/numpy/ndarraytypes.h:1728:
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: warning: "Using 
deprecated NumPy API, disable it by
  #defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-W#warnings]
#warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"


These look innocuous, but easy to fix:

./CXX/Python2/Objects.hxx:1133:23: warning: implicit conversion of NULL 
constant to 'int' [-Wnull-conversion]
, offset( NULL )
~ ^~~~

/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/core/include/numpy/npy_3kcompat.h:247:40: warning: conversion 
from string literal to 'char *' is
  deprecated [-Wdeprecated-writable-strings]
return PyObject_CallFunction(open, "Os", filename, mode);


/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/numpy/core/include/numpy/npy_3kcompat.h:255:37: warning: conversion 
from string literal to 'char *' is
  deprecated [-Wdeprecated-writable-strings]
ret = PyObject_CallMethod(file, "close", NULL);


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Chris Barker - NOAA Federal 
On Wed, May 29, 2013 at 2:19 PM, Russell E. Owen  wrote:

> I guess we could serve the associated packages (pytz, dateutil and six),
> or if they can be installed by pip, ask users to install those. But
> users using binary installers may not even have pip available, so it's a
> big initial hurdle.

If the binary installers are available (and easy to find), not such a
big deal -- this is teh case with Christoph's repository for Windows,
for instance.

Russell, have you been following the thread I started on the pythonmac
list? We really need a way to deal better with binaries on the Mac,
including dependency handling.

Note that supposedly the "wheel" format is coming (soon?), and after
that support for binary wheels by pip.

Of course, none of that helps right now...

-Chris



-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115   (206) 526-6317   main reception

[email protected]

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Russell Owen 
On May 29, 2013, at 4:01 PM, Chris Barker - NOAA Federal 
 wrote:

> On Wed, May 29, 2013 at 2:19 PM, Russell E. Owen  wrote:
> 
>> I guess we could serve the associated packages (pytz, dateutil and six),
>> or if they can be installed by pip, ask users to install those. But
>> users using binary installers may not even have pip available, so it's a
>> big initial hurdle.
> 
> If the binary installers are available (and easy to find), not such a
> big deal -- this is teh case with Christoph's repository for Windows,
> for instance.
> 
> Russell, have you been following the thread I started on the pythonmac
> list? We really need a way to deal better with binaries on the Mac,
> including dependency handling.
> 
> Note that supposedly the "wheel" format is coming (soon?), and after
> that support for binary wheels by pip.
> 
> Of course, none of that helps right now...

I have been following that thread with great interest. If such a repository 
becomes available I do intend to contribute to it.

For the record:
- I prefer static libraries
- The wheel format sounds very promising. But until we have it and until pip 
supports it, my suspicion is that it's not worth trying to automate dependency 
handling, and we should live with mpkg binary installers.


In the short term I'd be happier if matplotlib continued to support including 
dateutils, pytz and six. It is not ideal to include dependencies, but 
convenient and pragmatic. Failing that, i think we should ask users to install 
pip and use pip to install dateutils, pytz and six. I fear it would be too much 
work to provide binary installers for pytz, dateutils and six because we would 
need to make different packages for different versions of python (which feels 
silly for pure python packages!), keep them up to date, find somewhere to serve 
them...

In the long term, I hope wheel format will allow us to use pip to install 
matplotlib, in which case it will handle dependencies and we need not include 
them.

-- Russell
--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 
Must be a problem with the upload.  I'm reuploading it now.  I'm not 
going to bother upping the version -- it's just the result of a failed 
transfer apparently.

Mike

On 05/29/2013 04:12 PM, Christoph Gohlke wrote:
> Sorry, but that tarball does not include setup.py and other files. It is
> only ~25 MB.
>
> Christoph
>
>
> On 5/29/2013 12:48 PM, Michael Droettboom wrote:
>> Ok, folks.  1.3.0rc2 is here:
>>
>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc2/matplotlib-1.3.0rc2.tar.gz
>>
>>
>> Mike
>>
>>
>>
>> On 05/29/2013 03:41 PM, Michael Droettboom wrote:
>>> On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
 Removing the hardcoded paths works.

 I noticed two more build issues.

 1) On Python 3.x I see the following errors/warnings, however the
 build succeeds.

 ```
 Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py
 line 1265: ParseError: bad token: type=55, value="'", context=('',
 (1265, 38))
 Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
 line 3344: TokenError: ('EOF in multi-line statement', (2, 0))
 Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
 line 3345: ParseError: bad input: type=5, value='  ',
 context=('\n\n\n\n', (3345, 0))
 Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
 line 3346: ParseError: bad input: type=5, value='  ',
 context=('\n\n\n\n', (3346, 0))
 Can't parse docstring in
 build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322:
 TokenError: ('EOF in multi-line statement', (2, 0))
 ```
>>> While annoying, I think these are benign --- the 2to3 tool is tripping
>>> up on these docstrings.  Overtime, the docstrings will get rewritten in
>>> numpydoc format and we *might* see these go away.
>>>
 2) On Python 2.6 with distribute-0.6.45, the build fails during
 packaging. See 
>>> Good catch.  Thanks.
>>>
>>> Mike
 Christoph


 On 5/29/2013 12:08 PM, Michael Droettboom wrote:
> It seems that in the setuptools way [TM] it is rather difficult to not
> include this folder.  Does it work if you only remove those hardcoded
> paths?  It should be easy for me to fix that by not having it search for
> system libraries when building a tarball.
>
> Mike
>
> On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
>> Hi,
>>
>> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
>> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
>> therefore fails to build on my system. Deleting the
>> lib\matplotlib.egg-info folder works.
>>
>> Does the release announcement mention that Windows binaries won't
>> include required dependencies (pytz, dateutil, pyparsing, six) any
>> longer?
>>
>> Christoph
>>
>>
>> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
>>> I'm pleased to announce the tagging of matplotlib-1.3.0rc1.
>>>
>>> Once the binaries from Christoph and Russell have been uploaded, I'll
>>> make a broader announcement to get some testing of this in advance of
>>> the final release.
>>>
>>> The tarball is available here:
>>>
>>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz
>>>
>>>
>>>
>>>
>>> The documentation for this version is viewable here:
>>>
>>> http://matplotlib.org/1.3.0
>>>
>>> Thanks everyone for their hard work getting this out the door!
>>>
>>> Mike
>>>
>>> --
>>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>>> Get 100% visibility into your production application - at no cost.
>>> Code-level diagnostics for performance bottlenecks with <2% overhead
>>> Download for free and get started troubleshooting in minutes.
>>> http://p.sf.net/sfu/appdyn_d2d_ap1
>>> ___
>>> Matplotlib-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>> --
>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>> Get 100% visibility into your production application - at no cost.
>> Code-level diagnostics for performance bottlenecks with <2% overhead
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap1
>> ___
>> Matplotlib-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>>
> --
> Introducing

Re: [matplotlib-devel] A generous donation of $10, 000 from Simula/Hans Petter Langtangen via NumFOCUS

2013-05-29 Thread Michael Droettboom 
Great news!  Thank you Dr. Langtangen for arranging this, and Fernando 
and the rest of the NumFOCUS board for making it happen!

Cheers,
Mike

On 05/29/2013 04:02 PM, Fernando Perez wrote:
> Hi all,
>
> I just wanted to let you all know that Hans Petter Langtangen,
> well-known author of books on scientific Python and long-time champion
> of these tools at the University of Oslo for many years, has arranged
> for a donation of $10,000 to support matplotlib's development.
>
> Hans Petter is the Director of the Center for Biomedical Computing at
> Simula (http://home.simula.no/~hpl), where a number of projects use
> Python as key elements of their research, the Fenics platform being
> among the most well-known (http://fenicsproject.org).
>
> We have now confirmed that these funds have been transferred to the
> NumFOCUS donations account, where Michael and the rest of the team can
> make use of them.
>
> I wanted to publicly thank Hans Petter and Simula Labs for
> persistently jumping through the necessary hoops to make this
> possible, and to Leah, Travis and Anthony at NumFOCUS for managing the
> receiving side of things.
>
> --
> 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
>
> --
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Closing in on 1.3.0 release candidate

2013-05-29 Thread Michael Droettboom 
On 05/29/2013 05:23 PM, Russell E. Owen wrote:
> In article <[email protected]>,
>   Michael Droettboom 
>   wrote:
>
>> I am going to hold off one more day on making the release candidate.
>> There are three blocker bugs that were discovered over the weekend and
>> I'd like to give them a chance for review first:...
> Thanks for the update.
>
> The Mac version built fine, but I saw several warnings. The only one I'm
> worried about is use of a deprecated Numpy API:
>
> In file included from src/_backend_agg.cpp:12:
> In file included from src/_backend_agg.h:43:
> In file included from src/agg_py_path_iterator.h:7:
> In file included from
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/core/include/numpy/arrayobject.h:15:
> In file included from
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/core/include/numpy/ndarrayobject.h:17:
> In file included from
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/core/include/numpy/ndarraytypes.h:1728:
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: warning: "Using
> deprecated NumPy API, disable it by
>#defining NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-W#warnings]
> #warning "Using deprecated NumPy API, disable it by #defining
> NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
>
>
> These look innocuous, but easy to fix:
>
> ./CXX/Python2/Objects.hxx:1133:23: warning: implicit conversion of NULL
> constant to 'int' [-Wnull-conversion]
>  , offset( NULL )
>  ~ ^~~~
>
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/core/include/numpy/npy_3kcompat.h:247:40: warning: conversion
> from string literal to 'char *' is
>deprecated [-Wdeprecated-writable-strings]
>  return PyObject_CallFunction(open, "Os", filename, mode);
>
>
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
> ages/numpy/core/include/numpy/npy_3kcompat.h:255:37: warning: conversion
> from string literal to 'char *' is
>deprecated [-Wdeprecated-writable-strings]
>  ret = PyObject_CallMethod(file, "close", NULL);
>
These are tricky, as we want to continue to support earlier versions of 
Numpy.  (Officially, we support back to 1.4, though only 1.6 and later 
is getting regular testing).  Last time I looked, there wasn't a good 
way to do this without a lot of #ifdefs that would just make the 
maintenance more complicated.

However, perhaps for the next major release we should consider dropping 
Numpy < 1.5 and fixing up these deprecation warnings.

Mike

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Michael Droettboom 

On 05/29/2013 05:19 PM, Russell E. Owen wrote:

In article <[email protected]>,
  Michael Droettboom 
  wrote:


I'm pleased to announce the tagging of matplotlib-1.3.0rc1.

Once the binaries from Christoph and Russell have been uploaded, I'll
make a broader announcement to get some testing of this in advance of
the final release.

The tarball is available here:

https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3
.0rc1/matplotlib-1.3.0rc1.tar.gz

The documentation for this version is viewable here:

http://matplotlib.org/1.3.0

Thanks everyone for their hard work getting this out the door!

It looks like the ability to include pytz and other dependencies in
binary distributions has been removed?
It's really just that the matplotlib source no longer includes them.  
Binaries can be built however we want them to be.  Not knowing how the 
.dmg is put together, is it possible to add pytz, dateutil, pyparsing 
and six to the dmg during its creation?


Is this really what we want? In the past we always included them.
Excluding them certainly makes sense if using pip or a similar installer
that can handle dependencies, but that is not the case for binaries.
Right -- and we're not using pip (because we can't) to handle our C/C++ 
dependencies, many of which we continue to ship with matplotlib.




I guess we could serve the associated packages (pytz, dateutil and six),
or if they can be installed by pip, ask users to install those. But
users using binary installers may not even have pip available, so it's a
big initial hurdle.

I'd personally be happier reverting to the old system. Sorry if I missed
a discussion on this.

No worries.  I'm certainly guilty of not always being able to keep up 
with the firehose myself.  This work was done as part of MEP11 ( 
https://github.com/matplotlib/matplotlib/wiki/MEP11) 
, and searching 
the mailing list with "MEP11" as a key should help you find the rest of 
the discussion.  It was pretty unanimous to move to not including these 
dependencies -- I certainly understand that different communities and 
platforms have different expectations, though, and if we want to find a 
way to include the dependencies in the Mac installer, I'm not opposed to 
that, but I would like to find a way to do it that only affects that one 
particular use case and not all the others (i.e. something external to 
or at least optional within the current setup infrastructure).


Mike
--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] ANN: matplotlib-1.3.0rc1

2013-05-29 Thread Christoph Gohlke 
OK, that worked. I uploaded Windows binaries, which include all test files.

Christoph


On 5/29/2013 5:34 PM, Michael Droettboom wrote:
> Must be a problem with the upload.  I'm reuploading it now.  I'm not
> going to bother upping the version -- it's just the result of a failed
> transfer apparently.
>
> Mike
>
> On 05/29/2013 04:12 PM, Christoph Gohlke wrote:
>> Sorry, but that tarball does not include setup.py and other files. It is
>> only ~25 MB.
>>
>> Christoph
>>
>>
>> On 5/29/2013 12:48 PM, Michael Droettboom wrote:
>>> Ok, folks.  1.3.0rc2 is here:
>>>
>>> https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc2/matplotlib-1.3.0rc2.tar.gz
>>>
>>>
>>> Mike
>>>
>>>
>>>
>>> On 05/29/2013 03:41 PM, Michael Droettboom wrote:
 On 05/29/2013 03:30 PM, Christoph Gohlke wrote:
> Removing the hardcoded paths works.
>
> I noticed two more build issues.
>
> 1) On Python 3.x I see the following errors/warnings, however the
> build succeeds.
>
> ```
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\artist.py
> line 1265: ParseError: bad token: type=55, value="'", context=('',
> (1265, 38))
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
> line 3344: TokenError: ('EOF in multi-line statement', (2, 0))
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
> line 3345: ParseError: bad input: type=5, value='  ',
> context=('\n\n\n\n', (3345, 0))
> Can't parse docstring in build\lib.win-amd64-3.2\matplotlib\axes.py
> line 3346: ParseError: bad input: type=5, value='  ',
> context=('\n\n\n\n', (3346, 0))
> Can't parse docstring in
> build\lib.win-amd64-3.2\matplotlib\backends\backend_agg.py line 322:
> TokenError: ('EOF in multi-line statement', (2, 0))
> ```
 While annoying, I think these are benign --- the 2to3 tool is tripping
 up on these docstrings.  Overtime, the docstrings will get rewritten in
 numpydoc format and we *might* see these go away.

> 2) On Python 2.6 with distribute-0.6.45, the build fails during
> packaging. See 
 Good catch.  Thanks.

 Mike
> Christoph
>
>
> On 5/29/2013 12:08 PM, Michael Droettboom wrote:
>> It seems that in the setuptools way [TM] it is rather difficult to not
>> include this folder.  Does it work if you only remove those hardcoded
>> paths?  It should be easy for me to fix that by not having it search for
>> system libraries when building a tarball.
>>
>> Mike
>>
>> On 05/29/2013 02:55 PM, Christoph Gohlke wrote:
>>> Hi,
>>>
>>> minor issue: the tarball contains a lib\matplotlib.egg-info directory.
>>> The SOURCES.txt contains absolute paths (/usr/src/CXX/...) and
>>> therefore fails to build on my system. Deleting the
>>> lib\matplotlib.egg-info folder works.
>>>
>>> Does the release announcement mention that Windows binaries won't
>>> include required dependencies (pytz, dateutil, pyparsing, six) any
>>> longer?
>>>
>>> Christoph
>>>
>>>
>>> On 5/29/2013 11:41 AM, Michael Droettboom wrote:
 I'm pleased to announce the tagging of matplotlib-1.3.0rc1.

 Once the binaries from Christoph and Russell have been uploaded, I'll
 make a broader announcement to get some testing of this in advance of
 the final release.

 The tarball is available here:

 https://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.3.0rc1/matplotlib-1.3.0rc1.tar.gz




 The documentation for this version is viewable here:

 http://matplotlib.org/1.3.0

 Thanks everyone for their hard work getting this out the door!

 Mike

 --
 Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
 Get 100% visibility into your production application - at no cost.
 Code-level diagnostics for performance bottlenecks with <2% overhead
 Download for free and get started troubleshooting in minutes.
 http://p.sf.net/sfu/appdyn_d2d_ap1
 ___
 Matplotlib-devel mailing list
 [email protected]
 https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>> --
>>> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
>>> Get 100% visibility into your production application - at no cost.
>>> Code-level diagnostics for performance bottlenecks with <2% overhead
>>> Download for free and get started troubleshooting in minutes.
>>> http://p.sf.net/sfu/appdyn_d2d_ap1
>>> __