Michael Droettboom wrote:
> Unfortunately, the EMF backend is no longer maintained.  We had 
> discussed removing it well over a year ago, and I actually thought it 
> had been removed, but obviously it wasn't.
> 
> It needs someone to port it to the new backend API introduced in 0.98.x 
> and to maintain that code.  When quite some time ago, there really 
> wasn't much interest in doing that.  I would be happy to help someone 
> with the details involved, but don't have the time myself at the moment.
> 
> Sorry for the confusion -- what do other developers think?  Should we 
> remove the backend and document the change, at least for the time being?

Mike,

Yes, like you I thought we had included it on the to-be-removed list, 
but evidently I remembered incorrectly.

Here is the history of the file:

10 months       jdh2358         removed pre py2.4 compatability code and some 
other dead code
10 months       mdboom  Merged revisions 5106-5108 via svnmerge from
18 months       mdboom  Refactoring of FigureCanvas*.print_figure so that 
each backend does
19 months       efiring         Use pickle to cache entire fontManager instance.
21 months       nnemec  remove trailing spaces
2 years         cmoad   added rotation arg to draw_arc method everywhere it was 
missing
2 years         jdh2358         added custom figure class hook
2 years         jdh2358         fixed figimage bug
3 years         jdh2358         added Aarre linestyle fix for emf backend
3 years         dsdale  added **kwargs to all backend_*.print_figure
3 years         jdh2358         made the rc warnings a bit more readable
3 years         jdh2358         added pyemf

I think it should be removed now.  If someone comes forward with a 
strong commitment to update and maintain it, it can be reinstated 
easily--after that person has done the updating required to make it work 
in the trunk.

Eric


> 
> Mike
> 
> Torsten Bronger wrote:
>> Hallöchen!
>>
>> I use pyemf 2.0 and Matplotlib 0.98.5.  If I try to save a trivial
>> plot into an EMF file, I get
>>
>> Traceback (most recent call last):
>>   File "./make_plots.py", line 23, in <module>
>>     figure.savefig(sample_name + "_pds.emf")
>>   File "/usr/lib/python2.5/[...]/matplotlib/figure.py", line 990, in savefig
>>     self.canvas.print_figure(*args, **kwargs)
>>   File "/usr/lib/python2.5/[...]/matplotlib/backend_bases.py", line 1419, in 
>> print_figure
>>     **kwargs)
>>   File "/usr/lib/python2.5/[...]/matplotlib/backends/backend_emf.py", line 
>> 604, in print_emf
>>     self.figure.draw(renderer)
>>   File "/usr/lib/python2.5/[...]/matplotlib/figure.py", line 738, in draw
>>     if self.frameon: self.patch.draw(renderer)
>>   File "/usr/lib/python2.5/[...]/matplotlib/patches.py", line 301, in draw
>>     renderer.draw_path(gc, tpath, affine, rgbFace)
>>   File "/usr/lib/python2.5/[...]/matplotlib/backend_bases.py", line 74, in 
>> draw_path
>>     raise NotImplementedError
>> NotImplementedError
>>
>> Is this a bug or a mal-configuration?  The Python code was
>>
>>             figure = pyplot.figure()
>>             axes = figure.add_subplot(111)
>>             x, y = numpy.loadtxt("data.dat", comments="#", usecols=(0, 1), 
>> unpack=True)
>>             axes.semilogy(x, y)
>>             figure.savefig("test.emf")
>>
>> Tschö,
>> Torsten.
>>
>>   
> 



------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Reply via email to