[matplotlib-devel] EPS export broken in HEAD?

2011-06-21 Thread Fernando Perez
Howdy,

a simple

plot(rand(100))
savefig('foo.eps')

is giving me the traceback below.  Is it something I'm doing wrong on my side?

Running on linux, ubuntu 10.10, python2.6.

Thanks for any tips...


f

---
TypeError Traceback (most recent call last)
/home/fperez/research/dif-tx/src/python/
in ()
> 1 savefig('foo.eps')

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/pyplot.pyc
in savefig(*args, **kwargs)
426 def savefig(*args, **kwargs):
427 fig = gcf()
--> 428 return fig.savefig(*args, **kwargs)
429
430 @docstring.copy_dedent(Figure.ginput)

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/figure.pyc
in savefig(self, *args, **kwargs)
   1160 kwargs.setdefault('edgecolor',
rcParams['savefig.edgecolor'])
   1161
-> 1162 self.canvas.print_figure(*args, **kwargs)
   1163
   1164 if transparent:

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_qt4agg.pyc
in print_figure(self, *args, **kwargs)
151
152 def print_figure(self, *args, **kwargs):
--> 153 FigureCanvasAgg.print_figure(self, *args, **kwargs)
154 self.draw()

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backend_bases.pyc
in print_figure(self, filename, dpi, facecolor, edgecolor,
orientation, format, **kwargs)
   1977 orientation=orientation,
   1978 bbox_inches_restore=_bbox_inches_restore,
-> 1979 **kwargs)
   1980 finally:
   1981 if bbox_inches and restore_bbox:

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backend_bases.pyc
in print_eps(self, *args, **kwargs)
   1744 from backends.backend_ps import FigureCanvasPS # lazy import
   1745 ps = self.switch_backends(FigureCanvasPS)
-> 1746 return ps.print_eps(*args, **kwargs)
   1747
   1748 def print_pdf(self, *args, **kwargs):

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_ps.pyc
in print_eps(self, outfile, *args, **kwargs)
933
934 def print_eps(self, outfile, *args, **kwargs):
--> 935 return self._print_ps(outfile, 'eps', *args, **kwargs)
936
937

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_ps.pyc
in _print_ps(self, outfile, format, *args, **kwargs)
966 self._print_figure(outfile, format, imagedpi,
facecolor, edgecolor,
967orientation, isLandscape, papertype,
--> 968**kwargs)
969
970 def _print_figure(self, outfile, format, dpi=72,
facecolor='w', edgecolor='w',

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_ps.pyc
in _print_figure(self, outfile, format, dpi, facecolor, edgecolor,
orientation, isLandscape, papertype, **kwargs)
   1059 bbox_inches_restore=_bbox_inches_restore)
   1060
-> 1061 self.figure.draw(renderer)
   1062
   1063 if dryrun: # return immediately if dryrun (tightbbox=True)

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/artist.pyc
in draw_wrapper(artist, renderer, *args, **kwargs)
 53 def draw_wrapper(artist, renderer, *args, **kwargs):
 54 before(artist, renderer)
---> 55 draw(artist, renderer, *args, **kwargs)
 56 after(artist, renderer)
 57

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/figure.pyc
in draw(self, renderer)
872 dsu.sort(key=itemgetter(0))
873 for zorder, func, args in dsu:
--> 874 func(*args)
875
876 renderer.close_group('figure')

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/artist.pyc
in draw_wrapper(artist, renderer, *args, **kwargs)
 53 def draw_wrapper(artist, renderer, *args, **kwargs):
 54 before(artist, renderer)
---> 55 draw(artist, renderer, *args, **kwargs)
 56 after(artist, renderer)
 57

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/axes.pyc
in draw(self, renderer, inframe)
   1981
   1982 for zorder, a in dsu:
-> 1983 a.draw(renderer)
   1984
   1985 renderer.close_group('axes')

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/artist.pyc
in draw_wrapper(artist, renderer, *args, **kwargs)
 53 def draw_wrapper(artist, renderer, *args, **kwargs):
 54 before(artist, renderer)
---> 55 draw(artist, renderer, *args, **kwargs)
 56 after(artist, renderer)
 57

/home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/axis.pyc
in draw(self, renderer, *args, **kwargs)
   1035
   1036 ticks_to_draw = self._update_ticks(renderer)
-> 1037 ticklabelBoxes, ticklabelBoxes2 =
self._get_tick_bboxes(ticks_to_draw, renderer)
   1038
   1039 for tick in ticks_to_draw

[matplotlib-devel] More precise instructions about installing from git

2011-06-21 Thread Dieter Weber
Hi everybody,
just now I noticed that I was still running the old SVN version of
matplotlib and not the most recent one from git. Apparently the files
installed to (in my
case) /usr/local/lib/python2.6/dist-packages/matplotlib from SVN with
"python setup.py install" took precedence over the installation with
"python setupegg.py develop". I therefore suggest to modify
http://matplotlib.sourceforge.net/faq/installing_faq.html#install-from-git by 
replacing

"If you want to be able to follow the development branch as it changes
just replace the last step with (make sure you have setuptools
installed):"

with 

"If you want to be able to follow the development branch as it changes
just uninstall any existing copy of matplotlib and replace the last step
with (make sure you have setuptools installed):"

Best wishes,
Dieter


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] [Matplotlib-users] Plan to merge the matplotlib-py3 branch?

2011-06-21 Thread Darren Dale
On Mon, Jun 20, 2011 at 6:18 PM, Eric Firing  wrote:
> On 06/20/2011 11:29 AM, Darren Dale wrote:
>
>> Ok, I've migrated the issues over to github.
>>
>> Darren
>
> Darren,
>
> Thank you.  Now I see another possible problem with the issue tracker:
> it doesn't seem to have a way to select issues that do *not* have a
> particular label.

I just filed a support request and asked if this feature could be added.

> Well, at least that gives us extra incentive to plow
> through the sourceforge imports and try to close as many as possible.
> Also to figure out a good standard set of labels.

Since github thinks I am the original reporter of all of the migrated
issues, I'm getting notifications on all the sourceforge issues
activity. Impressive progress! I think we closed over 80 issues since
yesterday, and you handled a big majority of them.

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] SVG export mangled

2011-06-21 Thread Michael Droettboom
I see what is happening here...  The SVG backend was recently re-written 
to write some of the path data in C -- unfortunately the numbers being 
written there are locale-aware, and in your locale it appears to be 
using ',' as a decimal point.


I put up a fix for this here:

https://github.com/matplotlib/matplotlib/pull/369

In the meantime, you may have some luck by setting your locale before 
running python, i.e.:


  LANG=en_US.UTF-8 python svg_export2.py

Cheers,
Mike

On 06/21/2011 06:47 AM, Dieter Weber wrote:

Hi folks,
when I tried to export figures as SVG, the result was completely messed
up. Export in other formats works.

Appended you find:
* Script to reproduce error
* Broken SVG
* Working EPS
* Broken SVG rendered by Gnome image viewer (eog)
* Broken SVG rendered by Inkscape

Setup:
Ubuntu 10.04 LTS
Python 2.6.5 (stock)
Matplotlib current version from git, installed with "python setupegg.py
develop"

Can you reproduce the problem on your machine?

Greetings,
Dieter



--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev


___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



--
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] EPS export broken in HEAD?

2011-06-21 Thread Michael Droettboom
It looks like something fishy in your font cache -- "None" has been 
entered in the table as a filename.

Can you move away your ~/.matplotlib/fontList.cache file (to force a 
regeneration) and see if that resolves the problem?  If so, I'd like to 
see the original broken fontList.cache file to see if I can get to the 
bottom of what's wrong with it.

Have you set any font-related rcParams to anything non-standard that 
might be causing the lookup to fail?

Cheers,
Mike

On 06/21/2011 04:24 AM, Fernando Perez wrote:
> Howdy,
>
> a simple
>
> plot(rand(100))
> savefig('foo.eps')
>
> is giving me the traceback below.  Is it something I'm doing wrong on my side?
>
> Running on linux, ubuntu 10.10, python2.6.
>
> Thanks for any tips...
>
>
> f
>
> ---
> TypeError Traceback (most recent call last)
> /home/fperez/research/dif-tx/src/python/
> in()
> >  1 savefig('foo.eps')
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/pyplot.pyc
> in savefig(*args, **kwargs)
>  426 def savefig(*args, **kwargs):
>  427 fig = gcf()
> -->  428 return fig.savefig(*args, **kwargs)
>  429
>  430 @docstring.copy_dedent(Figure.ginput)
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/figure.pyc
> in savefig(self, *args, **kwargs)
> 1160 kwargs.setdefault('edgecolor',
> rcParams['savefig.edgecolor'])
> 1161
> ->  1162 self.canvas.print_figure(*args, **kwargs)
> 1163
> 1164 if transparent:
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_qt4agg.pyc
> in print_figure(self, *args, **kwargs)
>  151
>  152 def print_figure(self, *args, **kwargs):
> -->  153 FigureCanvasAgg.print_figure(self, *args, **kwargs)
>  154 self.draw()
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backend_bases.pyc
> in print_figure(self, filename, dpi, facecolor, edgecolor,
> orientation, format, **kwargs)
> 1977 orientation=orientation,
> 1978 bbox_inches_restore=_bbox_inches_restore,
> ->  1979 **kwargs)
> 1980 finally:
> 1981 if bbox_inches and restore_bbox:
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backend_bases.pyc
> in print_eps(self, *args, **kwargs)
> 1744 from backends.backend_ps import FigureCanvasPS # lazy import
> 1745 ps = self.switch_backends(FigureCanvasPS)
> ->  1746 return ps.print_eps(*args, **kwargs)
> 1747
> 1748 def print_pdf(self, *args, **kwargs):
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_ps.pyc
> in print_eps(self, outfile, *args, **kwargs)
>  933
>  934 def print_eps(self, outfile, *args, **kwargs):
> -->  935 return self._print_ps(outfile, 'eps', *args, **kwargs)
>  936
>  937
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_ps.pyc
> in _print_ps(self, outfile, format, *args, **kwargs)
>  966 self._print_figure(outfile, format, imagedpi,
> facecolor, edgecolor,
>  967orientation, isLandscape, papertype,
> -->  968**kwargs)
>  969
>  970 def _print_figure(self, outfile, format, dpi=72,
> facecolor='w', edgecolor='w',
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/backends/backend_ps.pyc
> in _print_figure(self, outfile, format, dpi, facecolor, edgecolor,
> orientation, isLandscape, papertype, **kwargs)
> 1059 bbox_inches_restore=_bbox_inches_restore)
> 1060
> ->  1061 self.figure.draw(renderer)
> 1062
> 1063 if dryrun: # return immediately if dryrun (tightbbox=True)
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/artist.pyc
> in draw_wrapper(artist, renderer, *args, **kwargs)
>   53 def draw_wrapper(artist, renderer, *args, **kwargs):
>   54 before(artist, renderer)
> --->  55 draw(artist, renderer, *args, **kwargs)
>   56 after(artist, renderer)
>   57
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/figure.pyc
> in draw(self, renderer)
>  872 dsu.sort(key=itemgetter(0))
>  873 for zorder, func, args in dsu:
> -->  874 func(*args)
>  875
>  876 renderer.close_group('figure')
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/artist.pyc
> in draw_wrapper(artist, renderer, *args, **kwargs)
>   53 def draw_wrapper(artist, renderer, *args, **kwargs):
>   54 before(artist, renderer)
> --->  55 draw(artist, renderer, *args, **kwargs)
>   56 after(artist, renderer)
>   57
>
> /home/fperez/usr/opt/lib/python2.6/site-packages/matplotlib/axes.pyc
> in draw(self, renderer, inframe)
> 1

Re: [matplotlib-devel] improved source code for radar chart example in matplotlib docs

2011-06-21 Thread Josh Hemann

Hi Dan,

Is 
http://matplotlib.sourceforge.net/examples/api/radar_chart.html?highlight=radar
this the example  you are referring to? If so, this is the one I submitted
to the gallery a couple of years ago and I would be happy to see the
underlying methodology improved.

Josh

texas_ranger wrote:
> 
> Hello dev people,
> 
> I had an app where I needed the radar chart (aka Kiviat diagrams) source
> code out of matplotlib. Turns out the example source code is very limited
> the way it is currently written. Not good.
> 
> I re-wrote parts of the source code to make it much more flexible and
> easier
> to include in an app. For example, if run in stand-alone mode, the user
> can
> specify upto 25 different radar charts in one window. Titles and labels
> are
> much more general as well. The legend can have multiple columns, etc.
> 
> If anyone is interested, I will be happy to send you my source code,
> hoping
> you might consider replacing the current version in the docs with the one
> I'll send.
> 
> Just reply and I'll send the code. You can decide from there whether to
> use
> it to replace current version.
> 
> I did not want to attach the code if no one is interested.
> 
> Daniel Barnette
> 
> --
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 


-
Josh Hemann
Group Manager - Advanced Analytics 
Sports Authority
jhemann at sportsauthority com 

-- 
View this message in context: 
http://old.nabble.com/improved-source-code-for-radar-chart-example-in-matplotlib-docs-tp31351398p31894586.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] [Python-modules-team] Bug#608932: python-matplotlib-doc: "Exception occurred rendering plot"

2011-06-21 Thread Josh Hemann

Sandro, did you ever figure anything out with this behavior? I see the same
thing (example scripts for which the docs contain the Exception error yet
run just fine from the command line). 


Sandro Tosi-4 wrote:
> 
> Hi,
> 
> On Tue, Jan 4, 2011 at 19:11, Jakub Wilk  wrote:
>> Package: python-matplotlib-doc
>> Version: 0.99.3-1
>> Severity: minor
>>
>> There are several "Exception occurred rendering plot" warnings in the
>> generated documentation:
>>
>> $ cd /usr/share/doc/python-matplotlib-doc/html/ && grep -r 'Exception
>> occurred' .
>> ./users/screenshots.html:[ 
>> href="../plot_directive/mpl_examples/pylab_examples/scatter_demo2.py">source
>> code ]Exception occurred rendering plot.
>> ./users/screenshots.html:[ 
>> href="../plot_directive/mpl_examples/api/date_demo.py">source
>> code ]Exception occurred rendering plot.
>> ./users/screenshots.html:[ 
>> href="../plot_directive/mpl_examples/pylab_examples/finance_work2.py">source
>> code ]Exception occurred rendering plot.
>> ./users/screenshots.html:[ 
>> href="../plot_directive/pyplots/plotmap.py">source code ]Exception
>> occurred rendering plot.
>> ./examples/units/date_support.html:[ 
>> href="../../plot_directive/mpl_examples/units/date_support.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/units/basic_units.html:[ 
>> href="../../plot_directive/mpl_examples/units/basic_units.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/units/artist_tests.html:[ 
>> href="../../plot_directive/mpl_examples/units/artist_tests.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/axes_grid/demo_image.html:[ 
>> href="../../plot_directive/mpl_examples/axes_grid/demo_image.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/data_helper.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/data_helper.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/date_demo2.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/date_demo2.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/geo_demo.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/geo_demo.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/centered_ticklabels.html:[  external"
>> href="../../plot_directive/mpl_examples/pylab_examples/centered_ticklabels.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/finance_demo.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/finance_demo.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/date_demo1.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/date_demo1.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/finance_work2.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/finance_work2.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/loadrec.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/loadrec.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/scatter_demo2.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/scatter_demo2.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/pylab_examples/multipage_pdf.html:[ 
>> href="../../plot_directive/mpl_examples/pylab_examples/multipage_pdf.py">source
>> code ]Exception occurred rendering plot.
>> ./examples/api/date_demo.html:[ 
>> href="../../plot_directive/mpl_examples/api/date_demo.py">source
>> code ]Exception occurred rendering plot.
> 
> The updated list is:
> 
> api/axes_api.html
> api/pyplot_api.html
> examples/api/hinton_demo.html
> examples/api/radar_chart.html
> examples/api/sankey_demo.html
> examples/pylab_examples/anchored_artists.html
> examples/pylab_examples/arrow_demo.html
> examples/pylab_examples/axes_zoom_effect.html
> examples/pylab_examples/data_helper.html
> examples/pylab_examples/demo_bboximage.html
> examples/pylab_examples/geo_demo.html
> examples/pylab_examples/image_demo2.html
> examples/pylab_examples/legend_auto.html
> examples/pylab_examples/multipage_pdf.html
> examples/units/artist_tests.html
> examples/units/basic_units.html
> users/annotations_guide.html
> users/screenshots.html
> 
> But I have some problems debugging these issues, since when I run the
> code by-hand, it works fine but in the html file it's not shown. How
> can I debug that? in the log there's nothing about these problems (but
> other error, I'll follow them up in another mail).
> 
> Thanks in advance,
> -- 
> Sandro Tosi (aka morph, morpheus, matrixhasu)
> My website: http://matrixhasu.altervista.org/
> Me at Debian: http://wiki.debian.org/SandroTosi
> 
> --
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid

Re: [matplotlib-devel] SVG export mangled

2011-06-21 Thread Dieter Weber
Hi Mike,
your changes in the pull request fixed the problem for me, thanks a lot!

Greetings,
Dieter

Am Dienstag, den 21.06.2011, 09:01 -0400 schrieb Michael Droettboom:
> I see what is happening here...  The SVG backend was recently
> re-written to write some of the path data in C -- unfortunately the
> numbers being written there are locale-aware, and in your locale it
> appears to be using ',' as a decimal point.
> 
> I put up a fix for this here:
> 
> https://github.com/matplotlib/matplotlib/pull/369
> 
> In the meantime, you may have some luck by setting your locale before
> running python, i.e.:
> 
>   LANG=en_US.UTF-8 python svg_export2.py
> 
> Cheers,
> Mike
> 
> On 06/21/2011 06:47 AM, Dieter Weber wrote: 
> > Hi folks,
> > when I tried to export figures as SVG, the result was completely messed
> > up. Export in other formats works. 
> > 
> > Appended you find:
> > * Script to reproduce error
> > * Broken SVG
> > * Working EPS
> > * Broken SVG rendered by Gnome image viewer (eog)
> > * Broken SVG rendered by Inkscape
> > 
> > Setup:
> > Ubuntu 10.04 LTS
> > Python 2.6.5 (stock)
> > Matplotlib current version from git, installed with "python setupegg.py
> > develop"
> > 
> > Can you reproduce the problem on your machine?
> > 
> > Greetings,
> > Dieter
> > 
> > 
> > --
> > EditLive Enterprise is the world's most technically advanced content
> > authoring tool. Experience the power of Track Changes, Inline Image
> > Editing and ensure content is compliant with Accessibility Checking.
> > http://p.sf.net/sfu/ephox-dev2dev
> > 
> > ___
> > Matplotlib-devel mailing list
> > Matplotlib-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
> 
> -- 
> Michael Droettboom
> Science Software Branch
> Space Telescope Science Institute
> Baltimore, Maryland, USA
> --
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> ___ Matplotlib-devel mailing list 
> Matplotlib-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel



--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] EPS export broken in HEAD?

2011-06-21 Thread Fernando Perez
Hi Mike,

On Tue, Jun 21, 2011 at 6:07 AM, Michael Droettboom  wrote:
> It looks like something fishy in your font cache -- "None" has been
> entered in the table as a filename.
>
> Can you move away your ~/.matplotlib/fontList.cache file (to force a
> regeneration) and see if that resolves the problem?  If so, I'd like to
> see the original broken fontList.cache file to see if I can get to the
> bottom of what's wrong with it.

I think you're right, because now at my office I can't even reproduce
the problem.

The machine where I saw it is at home, so tonight I'll fish out the
font cache file and send it to you so you can investigate, along with
my matplotlibrc file, just in case.

Thanks, and sorry for the semi-false alarm!

Cheers,

f

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


[matplotlib-devel] github issue labels

2011-06-21 Thread Eric Firing
Suggestion: let's try to keep the labels short.  I think that will make 
it easier to see what we have as the number of labels increases, and 
will make the labels a bit less visually overwhelming.  (It looks like 
existing labels can be edited in the Manage Labels function, but I was 
afraid to try for fear I would mess something up.)

e.g.,
mac-osx -> OSX or Mac
ms-windows -> Win or MS
sourceforge-import -> SF


I have been marking feature requests from the old SF as "wishlist"; I 
hope that is consistent with the intentions of whoever made the label.

Eric

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


Re: [matplotlib-devel] github issue labels

2011-06-21 Thread Benjamin Root
On Tuesday, June 21, 2011, Eric Firing  wrote:
> Suggestion: let's try to keep the labels short.  I think that will make
> it easier to see what we have as the number of labels increases, and
> will make the labels a bit less visually overwhelming.  (It looks like
> existing labels can be edited in the Manage Labels function, but I was
> afraid to try for fear I would mess something up.)
>
> e.g.,
> mac-osx -> OSX or Mac
> ms-windows -> Win or MS
> sourceforge-import -> SF
>
>
> I have been marking feature requests from the old SF as "wishlist"; I
> hope that is consistent with the intentions of whoever made the label.
>
> Eric
>

I am fine with shortening them.  I have also interpreated wishlist to mean that.

I also want to bring in lessons I learned when participating in
Ubuntu's BugSquad.  For the "triaging" process, the report needs to be
confirmed.  Whenever we confirm a bug, we can tag it as such.  If more
information is needed or if you don't have time to confirm, you can
tag it as "need_confirm".  The tags are updated as progress is made.
There is also "ongoing" which I take to mean that the report has been
assigned and actively worked on.

Any others we want (or changes to the idea)?

Ben Root

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel