matplotlib-devel Mailing List for matplotlib

On May 29, 2013, at 4:01 PM, Chris Barker - NOAA Federal <chr...@no...> wrote:

> On Wed, May 29, 2013 at 2:19 PM, Russell E. Owen <ro...@uw...> 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

On Wed, May 29, 2013 at 2:19 PM, Russell E. Owen <ro...@uw...> 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

Chr...@no...

In article <51A...@st...>,
 Michael Droettboom <md...@st...> 
 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);

In article <51A...@st...>,
 Michael Droettboom <md...@st...> 
 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

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<snip>\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<snip>\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 <https://github.com/matplotlib/matplotlib/pull/2085>
>> 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
>> Mat...@li...
>> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

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

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<snip>\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<snip>\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 <https://github.com/matplotlib/matplotlib/pull/2085>
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

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<snip>\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<snip>\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 <https://github.com/matplotlib/matplotlib/pull/2085>

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

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<snip>\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<snip>\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 <https://github.com/matplotlib/matplotlib/pull/2085>

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

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

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

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
>

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