matplotlib-users Mailing List for matplotlib

Hi All,

Too many people in the Python community think the only way to work with
Excel files in Python is using COM on Windows.

To try and correct this, I'm giving a tutorial at this year's PyCon in 
Chicago on Wednesday, 25th March that will cover working with Excel 
files in Python using the pure-python libraries xlrd, xlwt and xlutils.

I'll be looking to cover:

- Reading Excel Files

   Including formatting, unicode dates and formulae.

- Writing Excel Files

   Including formatting with easyxf and things like freeze pains, print
   areas, etc

- Filtering Excel Files

   A run through on the structure of xlutils.filter and some examples to
   show you how it works.

- Workshop for your problems

   I'm hoping anyone who attends will get a lot out of this! If you're
   planning on attending and have a particular problem you'd like to work
   on in this part of the tutorial, please drop me an email and I'll try
   and make sure I come prepared!

All you need for the tutorial is a working knowledge of Excel and 
Python, with a laptop as an added benefit, and to be at PyCon this year:

http://us.pycon.org

I look forward to seeing you all there!

Chris

-- 
Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk

Maybe a backend problem, since your soft is based on wx and the user
uses Tk :
...
> Using fontManager instance from /Users/nick/.matplotlib/fontManager.cache
> backend TkAgg version 8.4
> Traceback (most recent call last):
>  File "Croizat.py", line 71, in <module>
>    Croizat = Application(0)
...
-- 
Lionel Roubeyrie
chargé d'études
LIMAIR - La Surveillance de l'Air en Limousin
http://www.limair.asso.fr

On Wed, Jan 21, 2009 at 21:09, John Hunter <jd...@gm...> wrote:

> This looks like a simple bug in which FigureCanvasBase is not
> imported.  Try replacing line 31 in
> matplotlib/backends/backend_cocoaagg.py with this::
>
>    from matplotlib.backend_bases import FigureManagerBase, FigureCanvasBase
>
> I've fixed the bug on the svn branch and trunk.

Thanks, that fixes the backtrace.

> In a somewhat unrelated note, this style of "pylab animation" is no
> longer encouraged or supported (and your example does not work with
> cocoaagg, even with the fix, on my osx box).  Rather, you should use
> the GUI timeout or idle loop for your backend to support animation, as
> in the examples in
> http://matplotlib.sourceforge.net/examples/animation/index.html.
> While there are no cocoa specific examples (feel free to contribute
> one) the pattern should be fairly clear across the UIs we have
> examples for.

Thanks, I'll pass that onto the user who reported this problem to me.

Cheers

Adam

On Wed, Jan 21, 2009 at 8:31 PM, Adam Mercer <ram...@gm...> wrote:
> Anyone?
>
> Cheers
>
> Adam
>
> On Sat, Jan 17, 2009 at 17:19, Adam Mercer <ram...@gm...> wrote:
>> Hi
>>
>> I'm trying to track down an issue with the CocoaAgg backend on Mac OS
>> X using MacPorts, when run with the CocoaAgg backend the following
>> code:
>>
>> from pylab import *
>> import time
>>
>> ion()
>>
>> tstart = time.time()
>> x = arange(0,2*pi,0.01)
>> line, = plot(x,sin(x))
>> for i in arange(1,200):
>>    line.set_ydata(sin(x+i/10.0))
>>    draw()
>>
>> print 'FPS:' , 200/(time.time()-tstart)
>>
>> fails with the backtrace:
>>
>> $ python temp.py -dCocoaAgg
>> Traceback (most recent call last):
>>  File "temp.py", line 2, in <module>
>>    from pylab import *
>>  File "/opt/local/lib/python2.5/site-packages/pylab.py", line 1, in <module>
>>    from matplotlib.pylab import *
>>  File "/opt/local/lib/python2.5/site-packages/matplotlib/pylab.py",
>> line 253, in <module>
>>    from matplotlib.pyplot import *
>>  File "/opt/local/lib/python2.5/site-packages/matplotlib/pyplot.py",
>> line 75, in <module>
>>    new_figure_manager, draw_if_interactive, show = pylab_setup()
>>  File "/opt/local/lib/python2.5/site-packages/matplotlib/backends/__init__.py",
>> line 25, in pylab_setup
>>    globals(),locals(),[backend_name])
>>  File "/opt/local/lib/python2.5/site-packages/matplotlib/backends/backend_cocoaagg.py",
>> line 54, in <module>
>>    class FigureCanvasCocoaAgg(FigureCanvasAgg):
>>  File "/opt/local/lib/python2.5/site-packages/matplotlib/backends/backend_cocoaagg.py",
>> line 63, in FigureCanvasCocoaAgg
>>    start_event_loop.__doc__=FigureCanvasBase.start_event_loop_default.__doc__
>> NameError: name 'FigureCanvasBase' is not defined\

This looks like a simple bug in which FigureCanvasBase is not
imported.  Try replacing line 31 in
matplotlib/backends/backend_cocoaagg.py with this::

    from matplotlib.backend_bases import FigureManagerBase, FigureCanvasBase

I've fixed the bug on the svn branch and trunk.

In a somewhat unrelated note, this style of "pylab animation" is no
longer encouraged or supported (and your example does not work with
cocoaagg, even with the fix, on my osx box).  Rather, you should use
the GUI timeout or idle loop for your backend to support animation, as
in the examples in
http://matplotlib.sourceforge.net/examples/animation/index.html.
While there are no cocoa specific examples (feel free to contribute
one) the pattern should be fairly clear across the UIs we have
examples for.

JDH

Anyone?

Cheers

Adam

On Sat, Jan 17, 2009 at 17:19, Adam Mercer <ram...@gm...> wrote:
> Hi
>
> I'm trying to track down an issue with the CocoaAgg backend on Mac OS
> X using MacPorts, when run with the CocoaAgg backend the following
> code:
>
> from pylab import *
> import time
>
> ion()
>
> tstart = time.time()
> x = arange(0,2*pi,0.01)
> line, = plot(x,sin(x))
> for i in arange(1,200):
>    line.set_ydata(sin(x+i/10.0))
>    draw()
>
> print 'FPS:' , 200/(time.time()-tstart)
>
> fails with the backtrace:
>
> $ python temp.py -dCocoaAgg
> Traceback (most recent call last):
>  File "temp.py", line 2, in <module>
>    from pylab import *
>  File "/opt/local/lib/python2.5/site-packages/pylab.py", line 1, in <module>
>    from matplotlib.pylab import *
>  File "/opt/local/lib/python2.5/site-packages/matplotlib/pylab.py",
> line 253, in <module>
>    from matplotlib.pyplot import *
>  File "/opt/local/lib/python2.5/site-packages/matplotlib/pyplot.py",
> line 75, in <module>
>    new_figure_manager, draw_if_interactive, show = pylab_setup()
>  File "/opt/local/lib/python2.5/site-packages/matplotlib/backends/__init__.py",
> line 25, in pylab_setup
>    globals(),locals(),[backend_name])
>  File "/opt/local/lib/python2.5/site-packages/matplotlib/backends/backend_cocoaagg.py",
> line 54, in <module>
>    class FigureCanvasCocoaAgg(FigureCanvasAgg):
>  File "/opt/local/lib/python2.5/site-packages/matplotlib/backends/backend_cocoaagg.py",
> line 63, in FigureCanvasCocoaAgg
>    start_event_loop.__doc__=FigureCanvasBase.start_event_loop_default.__doc__
> NameError: name 'FigureCanvasBase' is not defined
>
> However this runs without issue using the MacOSX backend:
>
> $ python temp.py -dMacOSX
> FPS: 20.1183278689
>
> Is there some missing dependency that could cause this?
>
> Cheers
>
> Adam
>

On 1/21/2009 4:52 PM ramirodsl apparently wrote:
> Hi,
> 
> I'm experiencing a weird problem with the bounding box of my eps files.
> I have a script that produces my plots and saves them as eps files.
> For some reason the x coordinate of the bounding box is negative.
> 
> The bounding box of the files are: %%BoundingBox: -54 36 666 756
> 
> Then, when I try to print or show these files with gv they are clipped at
> the left side.


That seems just right: they should be clipped at the
page boundary.  This shoud *not* affect their inclusion
in a document, however, for correctly behaving applications.

Perhaps this is useful:
http://osdir.com/ml/python.pyx.users/2006-03/msg00022.html


> I found the translate command on the EPS file format specification, so I
> added: 54 0 translate to the eps header.
> Everything looked ok until I tried to include these files in a tex/ps
> document. Now they get clipped on the right side!

You would need to change the bounding box too!

I think eps2eps will do all this for you if you really want to.

Alan Isaac