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
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
