Changes between Initial Version and Version 1 of Ticket #4529, comment 40


Ignore:
Timestamp:
05/27/12 03:45:31 (9 years ago)
Author:
ppurka
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4529, comment 40

    initial v1  
    99
    1010I had thought about it. My decision was to silently ignore this error because it is not fatal in any way and we handle it properly (i.e. we ignore it and do the right thing).
     11
     12'''Edit:''' This seems to be the same behavior as in matplotlib.
    1113
    1214>  * In `_matplotlib_tick_formatter`, should `base` and `scale` be next to each other in the function definition?  (This is a very minor critique, of course.)
     
    2426>  * kini says that the `[13:]` seems brittle if matplotlib's API changes; would it be possible to remove the specific string `\\mathdefault` instead?
    2527
    26 To remove it from matplotlib, we need to set rcParams['text.usetex']=True. But this makes matplotlib try to compile latex on its own and use dvipng to convert from dvi to png, etc. Moreover, this parameter seems to be persistent and remains throughout the current session. So, simply editing the string seemed a more viable option to me.
     28To remove it from matplotlib, we need to set `rcParams['text.usetex']=True`. But this makes matplotlib try to compile latex on its own and use dvipng to convert from dvi to png, etc. Moreover, this parameter seems to be persistent and remains throughout the current session. So, simply editing the string seemed a more viable option to me.
    2729
    2830If the API changes (which seems unlikely to me), then the fix will be very easy too.