matplotlib-devel Mailing List for matplotlib

2008年8月4日 Michael Droettboom <md...@st...>:
> The graphviz failing is my bad. I failed to test the latex doc build (since
> it never works for me anyway due to a too-old version of latex). This is
> fixed in SVN r5962, and a patch against doc/sphinxext/inheritance_diagram.py
> is attached.
Err... the attached patch is empty :D Anyhow, I'm subscribed to commit
ml, so I got it:
--- trunk/matplotlib/doc/sphinxext/inheritance_diagram.py
2008年08月04日 12:20:25 UTC (rev 5961)
+++ trunk/matplotlib/doc/sphinxext/inheritance_diagram.py
2008年08月04日 13:09:02 UTC (rev 5962)
@@ -346,7 +346,7 @@
 parts = node['parts']
 graph_hash = get_graph_hash(node)
- name = "inheritance%s"
+ name = "inheritance%s" % graph_hash
 pdf_path = os.path.join('_static', name + ".pdf")
 graph.run_dot(['-Tpdf', '-o%s' % pdf_path],
(sorry if gmail wraps it).
I'll apply it once at home and test if works in Debian: Thanks for the
prompt reply!!
Sandro
-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

The graphviz failing is my bad. I failed to test the latex doc build 
(since it never works for me anyway due to a too-old version of latex). 
This is fixed in SVN r5962, and a patch against 
doc/sphinxext/inheritance_diagram.py is attached.
Cheers,
Mike
Sandro Tosi wrote:
> On Sun, Aug 3, 2008 at 20:29, Sandro Tosi <mat...@gm...> wrote:
> 
>> On Sun, Aug 3, 2008 at 20:19, Charlie Moad <cw...@gm...> wrote:
>> 
>>> I was going to wait on John about the docs, but I went ahead and cut the
>>> 0.98.3 release. The sdist including the docs was 34MB, so I decided not to
>>> include them. This would also cause the binaries to be huge if we included
>>> them there as well. The source release is up/tagged and I will post
>>> binaries asap.
>>> 
>> Thanks a lot, Charlie!! I'm downloading the brand new tarball and I'll
>> upgrade the Debian package short after.
>> 
>
> While building (in a clean chroot) the package to upload in Debian, I
> noticed some errors at doc creation (I attach the complete log, it
> might help you to track the issue), something like:
>
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/axes.py:docstring
> of matplotlib.axes.Axes.acorr:35: (ERROR/3) Unexpected indentation.
> WARNING: <autodoc>:0: (ERROR/3) Unexpected indentation.
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/backend_bases.py:docstring
> of matplotlib.backend_bases.FigureCanvasBase.stop_event_loop_default:8:
> (WARNING/2) Literal block expected; none found.
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/api/backend_qt4agg_api.rst:5:
> (WARNING/2) autodoc can't import/find module
> 'matplotlib.backends.backend_qt4agg', it reported error: "cannot
> import name QtCore",please check your spelling and sys.path
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/api/cbook_api.rst:9:
> (WARNING/2) error while formatting signature for
> matplotlib.cbook.Xlator: arg is not a Python function
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/pyplot.py:docstring
> of matplotlib.pyplot.acorr:55: (ERROR/3) Unexpected indentation.
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/pyplot.py:docstring
> of matplotlib.pyplot.annotate:17: (ERROR/3) Unexpected indentation.
> [...]
> resolving references...
> writing... Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
> WARNING: unusable reference target found:
> https://sourceforge.net/project/admin/?group_id=80706
> Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
> Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
> Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
>
> I don't know if something bad has happened in mpl code or something in
> Debian is broken right now (graphviz?), but it would help me if
> someone can confirm this is not happening only on my box.
>
> Thanks,
> 
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Eric Firing wrote:
> Jeff,
>
> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534
>
> Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think 
> they are ill-advised. They are based on the assumption that input to 
> rotate_vector, which must be called before m_quiver, should be 
> describing a rectangular array of points; but this is not the case for a 
> typical oceanographic use-case, plotting current vectors as measured 
> along a ship track. In that case one naturally has 4 1-D vectors of the 
> same shape for U, V, X, and Y, and one does not want meshgrid to be 
> called on X and Y. If you want automatic meshgrid, it should be called 
> only if X and Y are 1-D *and* their lengths match the 2-D shape of U and V.
>
> Eric
> 
Eric: Sorry about that. For some reason, I was thinking that 
rotate_vector only made sense for gridded data, which is obviously 
wrong. Fixed in r5960.
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328

Eric Firing wrote:
> Jeff,
> 
> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534
> 
> Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think 
Oops! I meant 5534; 5520 was the predecessor.
Eric

Jeff,
http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534
Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think 
they are ill-advised. They are based on the assumption that input to 
rotate_vector, which must be called before m_quiver, should be 
describing a rectangular array of points; but this is not the case for a 
typical oceanographic use-case, plotting current vectors as measured 
along a ship track. In that case one naturally has 4 1-D vectors of the 
same shape for U, V, X, and Y, and one does not want meshgrid to be 
called on X and Y. If you want automatic meshgrid, it should be called 
only if X and Y are 1-D *and* their lengths match the 2-D shape of U and V.
Eric