matplotlib-users Mailing List for matplotlib

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:

    Fernando> OK, it seems that Nicholas tested it and it works.  Is
    Fernando> there anything you want me to do on the ipython side of
    Fernando> things to help along for the future?

Nothing special -- just let me know when you have applied the patch I
sent you a few days ago and I will update and test it out.

Thanks,
JDH

John Hunter wrote:
>>>>>>"Fernando" == Fernando Perez <Fer...@co...> writes:
> 
> 
>     Fernando> John Hunter wrote:
>     >> The goal is for backends.draw_if_interactive and
>     >> pylab.draw_if_interactive to be the same symbol (so Shell.py
>     >> will not fail) But it is clear that they are not the same
>     >> function
> 
>     Fernando> Strange.  Sorry that I can't work with CVS today, I have
>     Fernando> a few urgent things to take care of here.  Just some
>     Fernando> suggestions:
> 
> 
> It appears that the problem was ipython Shell.py calling 
> 
>   backend.draw_if_interactive = flag_calls(backend.draw_if_interactive)
> 
> which defeated my cache.  I think I have a working workaround in CVS
> now.
> 
> Nicholas can you test?
> 
> I can roll out a bug fix release next week if these changes work.
> Currently they affect all ipython users who use "run
> somepylabscript.py" under 0.83.

OK, it seems that Nicholas tested it and it works.  Is there anything you want 
me to do on the ipython side of things to help along for the future?

Cheers,

f

John Hunter wrote:
> Hi José,

  Hi John,

> I have thought this over a bit more after talking with Fernando Perez,
> a FC user, and wanted to add that in regards to the pytz and dateutils
> packages, I think it is fine to package them separately.  My main
> motivation for including them in the distro was to keep the list of
> dependencies small, and because these packages did not have win32
> friendly installers; neither issue should concern the FC4 packagers.

  I understand your motives and I agree with them. While packaging projects
for a distribution I am sure that you also understand our reasons for not
having multiple copies of the same code all over. Not just for space but
also for the ease that comes from doing the same work once, from having
bugs solved with one release instead of having to it multiple times. Also
if no code changes in a package there is no need to package it again,
increasing bandwidth consumption unnecessarily. (It is always good to be
able of dropping a green argument in the middle of an unrelated
discussion. ;-)

> I would emphasize vis-a-vis these dependencies that the packager
> should make sure the following examples run:
> 
>     peds-pc311:~/python/projects/matplotlib> ls examples/*date*
>     examples/date_demo1.py  examples/date_demo_convert.py
>     examples/date_demo2.py  examples/date_demo_rrule.py
> 
> and in general that the script examples/backend_driver.py, which runs
> a suite of examples over several image backends, should not generate
> errors.

  I will be aware of this issues, but a note on documentation would not
hurt. ;-) _ And yes, I know I am asking too much. :-)

  Also as far as I know both dateutils and pytz seem to have a slower pace
than matplotlib, so it should not be too difficult to synchronise the
packages. (Another variant of the famous last words... ;-)

> As I mentioned in a previous response, I hope to factor some of these
> dependencies into a separate, optional matplotlib-deps package to ease
> the installation burden on the users while making the setup as clean
> as possible for package maintainers.

  Thank you for your concern, to me as a packager it helps a lot to have the
collaboration of the package authors to solve the issues that show. As
users I am even more satisfied as I have an easy to update, and having a
close to upstream, of my favourites modules for python. I am serious here.

> Let me know if I can offer any more help, and thanks for your work
> promoting matplotlib!

 It is a fine piece of software and the interest from other projects is not
a random event. :-)

> JDH

-- 
José Abílio

I confirm it's working very fine for me now with the cvs matplotlib 
version, I'm not using the cvs ipython so that will work with th version 
0.6.15.

Thank you very much John.


    N.

John Hunter wrote:

>>>>>>"Fernando" == Fernando Perez <Fer...@co...> writes:
>>>>>>            
>>>>>>
>
>    Fernando> John Hunter wrote:
>    >> The goal is for backends.draw_if_interactive and
>    >> pylab.draw_if_interactive to be the same symbol (so Shell.py
>    >> will not fail) But it is clear that they are not the same
>    >> function
>
>    Fernando> Strange.  Sorry that I can't work with CVS today, I have
>    Fernando> a few urgent things to take care of here.  Just some
>    Fernando> suggestions:
>
>
>It appears that the problem was ipython Shell.py calling 
>
>  backend.draw_if_interactive = flag_calls(backend.draw_if_interactive)
>
>which defeated my cache.  I think I have a working workaround in CVS
>now.
>
>Nicholas can you test?
>
>I can roll out a bug fix release next week if these changes work.
>Currently they affect all ipython users who use "run
>somepylabscript.py" under 0.83.
>
>JDH
>
>  
>

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:

    Fernando> John Hunter wrote:
    >> The goal is for backends.draw_if_interactive and
    >> pylab.draw_if_interactive to be the same symbol (so Shell.py
    >> will not fail) But it is clear that they are not the same
    >> function

    Fernando> Strange.  Sorry that I can't work with CVS today, I have
    Fernando> a few urgent things to take care of here.  Just some
    Fernando> suggestions:


It appears that the problem was ipython Shell.py calling 

  backend.draw_if_interactive = flag_calls(backend.draw_if_interactive)

which defeated my cache.  I think I have a working workaround in CVS
now.

Nicholas can you test?

I can roll out a bug fix release next week if these changes work.
Currently they affect all ipython users who use "run
somepylabscript.py" under 0.83.

JDH

John Hunter wrote:

> The goal is for backends.draw_if_interactive and
> pylab.draw_if_interactive to be the same symbol (so Shell.py will not
> fail)
> 
> But it is clear that they are not the same function

Strange.  Sorry that I can't work with CVS today, I have a few urgent things 
to take care of here.  Just some suggestions:

start sprinkling

print '*** object id for draw_if_interactive:',id(draw_if_interactive)

calls everywhere across that chain call.  That id() call should always give 
the exact same value, if the draw_if_interactive name is pointing to the same 
object.  At some point, this should show where a new object is being created 
(with a new id).

Sorry not to be of more help right now,

f

>>>>> "John" == John Hunter <jdh...@ac...> writes:

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:
    Fernando> John, is this due to the recent __init__ patch in
    Fernando> matplotlib?  I haven't committed any of that, as I am in
    Fernando> the middle of the cvs->svn transition at ipython's site,
    Fernando> and without net access at home (moving), so I'm sort of
    Fernando> crippled right now.

    John> I tried to fix backends/__init__.py to work with existing
    John> ipython distributions.  But I only tested calling plot
    John> commands from ipython and not run.  The latter exposes the
    John> bug.  I think this should be fixed on the matplotlib end,
    John> since I don't want to require everyone to always have the
    John> latest ipython.  I'll take a look and see if I can figure
    John> out a workaround.


The problem appears to be that the draw_if_interactive function pylab
gets by calling pylab_setup is not the same as the
backends.draw_if_interactive.  Thus the "called" flag you set in
Shell.py

        backend.draw_if_interactive = flag_calls(backend.draw_if_interactive)

is not set on the pylab.draw_if_interactive.  I tried to fix this by
modifying backends_init.py as follows, so that both functions would be
the same (in CVS).

  def pylab_setup():
      'return new_figure_manager, draw_if_interactive and show for pylab'
      # Import the requested backend into a generic module object
      if pylabcache is not None: return pylabcache
      backend_name = 'backend_'+backend.lower()
      backend_mod = __import__('matplotlib.backends.'+backend_name,
      ..snip..
      return new_figure_manager, draw_if_interactive, show

  # a hack to keep old versions of ipython working with mpl after bug
  # fix #1209354
  pylabcache = None
  if 'IPython.Shell' in  sys.modules:
      pylabcache = pylab_setup()
      new_figure_manager, draw_if_interactive, show = pylabcache

Thus the symbols new_figure_manager, draw_if_interactive, show are
still defined at module level when pylab is imported from ipython.


pylab gets it draw_if_interactive symbol with


  from backends import pylab_setup
  new_figure_manager, draw_if_interactive, show = pylab_setup()

The goal is for backends.draw_if_interactive and
pylab.draw_if_interactive to be the same symbol (so Shell.py will not
fail)

But it is clear that they are not the same function

In [1]: import matplotlib.backends

In [2]: matplotlib.backends.draw_if_interactive.jdh = 'test'

In [3]: draw_if_interactive.jdh
------------------------------------------------------------
Traceback (most recent call last):
  File "<console>", line 1, in ?
AttributeError: 'function' object has no attribute 'jdh'



What am I missing?  I verified that pylab_setup is returning
pylabcache when run from ipython, and yet the draw_if_interactive
function is not shared??

JDH

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:

    Fernando> John, is this due to the recent __init__ patch in
    Fernando> matplotlib?  I haven't committed any of that, as I am in
    Fernando> the middle of the cvs->svn transition at ipython's site,
    Fernando> and without net access at home (moving), so I'm sort of
    Fernando> crippled right now.

I tried to fix backends/__init__.py to work with existing ipython
distributions.  But I only tested calling plot commands from ipython
and not run.  The latter exposes the bug.  I think this should be
fixed on the matplotlib end, since I don't want to require everyone to
always have the latest ipython.  I'll take a look and see if I can
figure out a workaround.

JDH

John Hunter wrote:
>>>>>>"Humufr" == Humufr  <hu...@ya...> writes:
> 
> 
>     Humufr> I have a problem with ipython and the new version of
>     Humufr> matplotlib (I'm using a cvs version but there are no
>     Humufr> change since yesterday so I suppose that is the version
>     Humufr> 0.83).  When I did a:
> 
> I assume you are working with ipython CVS?  Try replacing this code block
> in IPython/Shell.py
> 
>         # We need to detect at runtime whether show() is called by the user.
>         # For this, we wrap it into a decorator which adds a 'called' flag.
>         backend.draw_if_interactive = flag_calls(backend.draw_if_interactive)
> 
>         # This must be imported last in the matplotlib series, after
>         # backend/interactivity choices have been made
>         try:
>             import matplotlib.pylab as pylab
>             self.pylab = pylab
>             self.pylab_name = 'pylab'
>         except ImportError:
>             import matplotlib.matlab as matlab            
>             self.pylab = matlab
>             self.pylab_name = 'matlab'
> 
> 
> with this
> 
>         # This must be imported last in the matplotlib series, after
>         # backend/interactivity choices have been made
>         try:
>             import matplotlib.pylab as pylab
>             self.pylab = pylab
>             self.pylab_name = 'pylab'
>         except ImportError:
>             import matplotlib.matlab as matlab            
>             self.pylab = matlab
>             self.pylab_name = 'matlab'
> 
>         # We need to detect at runtime whether show() is called by the user.
>         # For this, we wrap it into a decorator which adds a 'called' flag.
>         self.pylab.draw_if_interactive = flag_calls(self.pylab.draw_if_interactive)
> 
> 
> Does that help?

John, is this due to the recent __init__ patch in matplotlib?  I haven't 
committed any of that, as I am in the middle of the cvs->svn transition at 
ipython's site, and without net access at home (moving), so I'm sort of 
crippled right now.

If this is going to become a real problem for mpl users, I'll do my best to 
push out an update soon, but it may take me a few days.

Cheers,

f

>>>>> "Humufr" == Humufr  <hu...@ya...> writes:

    Humufr> I have a problem with ipython and the new version of
    Humufr> matplotlib (I'm using a cvs version but there are no
    Humufr> change since yesterday so I suppose that is the version
    Humufr> 0.83).  When I did a:

I assume you are working with ipython CVS?  Try replacing this code block
in IPython/Shell.py

        # We need to detect at runtime whether show() is called by the user.
        # For this, we wrap it into a decorator which adds a 'called' flag.
        backend.draw_if_interactive = flag_calls(backend.draw_if_interactive)

        # This must be imported last in the matplotlib series, after
        # backend/interactivity choices have been made
        try:
            import matplotlib.pylab as pylab
            self.pylab = pylab
            self.pylab_name = 'pylab'
        except ImportError:
            import matplotlib.matlab as matlab            
            self.pylab = matlab
            self.pylab_name = 'matlab'


with this

        # This must be imported last in the matplotlib series, after
        # backend/interactivity choices have been made
        try:
            import matplotlib.pylab as pylab
            self.pylab = pylab
            self.pylab_name = 'pylab'
        except ImportError:
            import matplotlib.matlab as matlab            
            self.pylab = matlab
            self.pylab_name = 'matlab'

        # We need to detect at runtime whether show() is called by the user.
        # For this, we wrap it into a decorator which adds a 'called' flag.
        self.pylab.draw_if_interactive = flag_calls(self.pylab.draw_if_interactive)


Does that help?

JDH

I have a problem with ipython and the new version of matplotlib (I'm 
using a cvs version but there are no change since yesterday so I suppose 
that is the version 0.83).
When I did a:

run simple_plot.py

it's working but I have this message (not very nice):


---------------------------------------------------------------------------
exceptions.AttributeError                            Traceback (most 
recent call last)

matplotlib/examples/<console>

/usr/local/lib/python2.4/site-packages/IPython/iplib.py in ipmagic(arg_s)
    140     else:
    141         magic_args = __IPYTHON__.var_expand(magic_args)
--> 142         return fn(magic_args)
    143
    144 def ipalias(arg_s):

/usr/local/lib/python2.4/site-packages/IPython/Shell.py in 
magic_run(self, parameter_s)
    474
    475     def magic_run(self,parameter_s=''):
--> 476         Magic.magic_run(self,parameter_s,runner=self.mplot_exec)
    477
    478     # Fix the docstring so users see the original as well

/usr/local/lib/python2.4/site-packages/IPython/Magic.py in 
magic_run(self, parameter_s, runner)
   1373
   1374                     else:
-> 1375                         
runner(filename,prog_ns,prog_ns,exit_ignore=exit_ignore)
   1376                 if opts.has_key('i'):
   1377                     self.shell.user_ns['__name__'] = __name__save

/usr/local/lib/python2.4/site-packages/IPython/Shell.py in 
mplot_exec(self, fname, *where, **kw)
    465         self.matplotlib.interactive(isInteractive)
    466         # make rendering call now, if the user tried to do it
--> 467         if self.pylab.draw_if_interactive.called:
    468             self.pylab.draw()
    469             self.pylab.draw_if_interactive.called = False

AttributeError: 'function' object has no attribute 'called'

Thanks for matplotlib and ipython.

N.

John Hunter wrote:

>Normally, this would have been a bugfix release, but I reorganized the
>matplotlib configuration files so thought it best to tick the version
>number.  All of the configuration files and dirs (matplotlibrc,
>tex.cache, ttffont.cache ) now reside in $HOME/.matplotlib (on windows
>C:\Documents and Settings\youracct\.matplotlib).  Please rename your
>.matplotlibrc file to matplotlibrc and put it there.
>
>Other changes are 
>
>
>2005-07-07 Added Eric's MA set_xdata Line2D fix - JDH
>
>2005-07-06 Made HOME/.matplotlib the new config dir where the
>           matplotlibrc file, the ttf.cache, and the tex.cache live.
>           The new default filenames in .matplotlib have no leading
>           dot and are not hidden.  Eg, the new names are matplotlibrc
>           tex.cache ttffont.cache.  This is how ipython does it so it
>           must be right.  If old files are found, a warning is issued
>           and they are moved to the new location.  Also fixed
>           texmanager to put all files, including temp files in
>           ~/.matplotlib/tex.cache, which allows you to usetex in
>           non-writable dirs.
>
>
>2005-07-05 Fixed bug #1231611 in subplots adjust layout.  The problem
>           was that the text cacheing mechanism was not using the
>           transformation affine in the key. - JDH
>
>2005-07-05 Fixed default backend import problem when using API (SF bug
>           # 1209354 -  see API_CHANGES for more info - JDH
>
>2005-07-04 backend_gtk.py: require PyGTK version 2.0.0 or higher - SC
>
>2005-06-30 setupext.py: added numarray_inc_dirs for building against
>           numarray when not installed in standard location - ADS
>
>
>2005-06-27 backend_svg.py: write figure width, height as int, not float.
>           Update to fix some of the pychecker warnings - SC
>  
>2005-06-23 Updated examples/agg_test.py to demonstrate curved paths
>           and fills - JDH
>
>2005-06-21 Moved some texmanager and backend_agg tex caching to class
>           level rather than instance level - JDH
>
>2005-06-20 setupext.py: fix problem where _nc_backend_gdk is installed to the
>           wrong directory - SC
>
>2005-06-19 Added 10.4 support for CocoaAgg. - CM
>
>2005-06-18 Move Figure.get_width_height() to FigureCanvasBase and return
>           int instead of float. - SC
>
>2005-06-18 Applied Ted Drain's QtAgg patch: 1) Changed the toolbar to
>           be a horizontal bar of push buttons instead of a QToolbar
>           and updated the layout algorithms in the main window
>           accordingly.  This eliminates the ability to drag and drop
>           the toolbar and detach it from the window.  2) Updated the
>           resize algorithm in the main window to show the correct
>           size for the plot widget as requested.  This works almost
>           correctly right now.  It looks to me like the final size of
>           the widget is off by the border of the main window but I
>           haven't figured out a way to get that information yet.  We
>           could just add a small margin to the new size but that
>           seems a little hacky.  3) Changed the x/y location label to
>           be in the toolbar like the Tk backend instead of as a
>           status line at the bottom of the widget.  4) Changed the
>           toolbar pixmaps to use the ppm files instead of the png
>           files.  I noticed that the Tk backend buttons looked much
>           nicer and it uses the ppm files so I switched them.
>
>
>2005-06-17 Modified the gtk backend to not queue mouse motion events.
>           This allows for live updates when dragging a slider. - CM
>
>2005-06-17 Added starter CocoaAgg backend.  Only works on OS 10.3 for
>           now and requires PyObjC.  (10.4 is high priority) - CM
>
>2005-06-17 Upgraded pyparsing and applied Paul McGuire's suggestions
>           for speeding things up.  This more than doubles the speed
>           of mathtext in my simple tests. JDH
>
>2005-06-16 Applied David Cooke's subplot make_key patch
>
>
>Downloads at http://matplotlib.sf.net
>
>Enjoy!
>JDH
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
>July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
>core and dual graphics technology at this free one hour event hosted by HP,
>AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
>_______________________________________________
>Matplotlib-users mailing list
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>  
>

Hi,

I am making the following transformation inside a function:

...
transform = agg.trans_affine(*tm)
curve = agg.conv_curve_path(path)
transcurve = agg.conv_transform_curve(curve, transform)
stroke = agg.conv_stroke_transcurve(transcurve)
stroke.width(strokeWidth)
...

I am getting the strokeWidth* *and* *tm parameters outside the function. 
Is there any way the strokeWidth also to be affected by the 
transformation made?
For example if I scale a curve, its countour to be scaled also.

Thank you in advance!
Regards
Z.Danevska

Normally, this would have been a bugfix release, but I reorganized the
matplotlib configuration files so thought it best to tick the version
number.  All of the configuration files and dirs (matplotlibrc,
tex.cache, ttffont.cache ) now reside in $HOME/.matplotlib (on windows
C:\Documents and Settings\youracct\.matplotlib).  Please rename your
.matplotlibrc file to matplotlibrc and put it there.

Other changes are 


2005-07-07 Added Eric's MA set_xdata Line2D fix - JDH

2005-07-06 Made HOME/.matplotlib the new config dir where the
           matplotlibrc file, the ttf.cache, and the tex.cache live.
           The new default filenames in .matplotlib have no leading
           dot and are not hidden.  Eg, the new names are matplotlibrc
           tex.cache ttffont.cache.  This is how ipython does it so it
           must be right.  If old files are found, a warning is issued
           and they are moved to the new location.  Also fixed
           texmanager to put all files, including temp files in
           ~/.matplotlib/tex.cache, which allows you to usetex in
           non-writable dirs.


2005-07-05 Fixed bug #1231611 in subplots adjust layout.  The problem
           was that the text cacheing mechanism was not using the
           transformation affine in the key. - JDH

2005-07-05 Fixed default backend import problem when using API (SF bug
           # 1209354 -  see API_CHANGES for more info - JDH

2005-07-04 backend_gtk.py: require PyGTK version 2.0.0 or higher - SC

2005-06-30 setupext.py: added numarray_inc_dirs for building against
           numarray when not installed in standard location - ADS


2005-06-27 backend_svg.py: write figure width, height as int, not float.
           Update to fix some of the pychecker warnings - SC
  
2005-06-23 Updated examples/agg_test.py to demonstrate curved paths
           and fills - JDH

2005-06-21 Moved some texmanager and backend_agg tex caching to class
           level rather than instance level - JDH

2005-06-20 setupext.py: fix problem where _nc_backend_gdk is installed to the
           wrong directory - SC

2005-06-19 Added 10.4 support for CocoaAgg. - CM

2005-06-18 Move Figure.get_width_height() to FigureCanvasBase and return
           int instead of float. - SC

2005-06-18 Applied Ted Drain's QtAgg patch: 1) Changed the toolbar to
           be a horizontal bar of push buttons instead of a QToolbar
           and updated the layout algorithms in the main window
           accordingly.  This eliminates the ability to drag and drop
           the toolbar and detach it from the window.  2) Updated the
           resize algorithm in the main window to show the correct
           size for the plot widget as requested.  This works almost
           correctly right now.  It looks to me like the final size of
           the widget is off by the border of the main window but I
           haven't figured out a way to get that information yet.  We
           could just add a small margin to the new size but that
           seems a little hacky.  3) Changed the x/y location label to
           be in the toolbar like the Tk backend instead of as a
           status line at the bottom of the widget.  4) Changed the
           toolbar pixmaps to use the ppm files instead of the png
           files.  I noticed that the Tk backend buttons looked much
           nicer and it uses the ppm files so I switched them.


2005-06-17 Modified the gtk backend to not queue mouse motion events.
           This allows for live updates when dragging a slider. - CM

2005-06-17 Added starter CocoaAgg backend.  Only works on OS 10.3 for
           now and requires PyObjC.  (10.4 is high priority) - CM

2005-06-17 Upgraded pyparsing and applied Paul McGuire's suggestions
           for speeding things up.  This more than doubles the speed
           of mathtext in my simple tests. JDH

2005-06-16 Applied David Cooke's subplot make_key patch


Downloads at http://matplotlib.sf.net

Enjoy!
JDH

Alan G Isaac wrote:
> On Fri, 08 Jul 2005, Christian Kristukat apparently wrote: 
> 
>>Another problems concerns matplotlib on windows when 
>>starting scripts from IDLE that use the pylab interface. 
>>After calling show() the python shell never returns and 
>>has to be killed. 
> 
> 
> Even after you close the plot window?

yes. I start the script pressing F5 and it never returns.

Regards, Christian

On Fri, 08 Jul 2005, Christian Kristukat apparently wrote:=20
> Another problems concerns matplotlib on windows when=20
> starting scripts from IDLE that use the pylab interface.=20
> After calling show() the python shell never returns and=20
> has to be killed.=20

Even after you close the plot window?

Cheers,
Alan Isaac

Hi all,

when using matplotlib through the pylab interface arrays are not any longer 
printed on the screen if they are rather large, instead some message appears 
telling the size and type of the array. How can I avoid that and get all the output?
Another problems concerns matplotlib on windows when starting scripts from IDLE 
that use the pylab interface. After calling show() the python shell never 
returns and has to be killed. I'm not using any special backend choice.
Regards, Christian

Hi,

the values of the data I'd like to plot varies in a very small region. Th=
erefore all yticks are labelled the same (e.g. all 2.785e-5).
Is there a possibility to increase the number of digits?

Thanks,
Sascha

Hi,

the values of the data I'd like to plot varies in a very small region. Th=
erefore all yticks are labelled the same (e.g. all 2.785e-5). Is there a =
possibility to increase the number of digits?

Thanks,
Sascha