[Matplotlib-users] bug report

; >1. Re: bug report (Christoph Gohlke) >2. Re: bug report (Bobby Wilkins) > > > -- > > Message: 1 > Date: Thu, 17 Sep 2015 10:30:30 -0700 > From: Christoph Gohlke > Subject: Re: [Matp

Re: [Matplotlib-users] bug report

One more note: changing the plot type from loglog to just plot, the errors also go away. On Thu, Sep 17, 2015 at 11:23 PM, Bobby Wilkins wrote: > I installed CPython 2.7.10, and the appropriate versions of the same > packages, and I still get the same error: > ---

Re: [Matplotlib-users] bug report

I installed CPython 2.7.10, and the appropriate versions of the same packages, and I still get the same error: [c:\python\dev\homework1] pip list backports.ssl-match-hostname (3.4.0.2) certifi (2015.9.6.2) decorator (4.0.2) functools32 (3.2.3.post2) ipykernel (4.0.3) ipyparallel (4.0.2) ipython (4

Re: [Matplotlib-users] bug report

I can reproduce the AttributeError on all Python versions and the crash (in Python's _tkinter.pyd extension) on Python 3.4. As a workaround you might try to upgrade to matplotlib 1.5, which seems to work for me. Christoph On 9/17/2015 6:46 AM, Bobby Wilkins wrote: > Thank you all. > > I am us

Re: [Matplotlib-users] bug report

Thank you all. I am using Python 3.4.3. I meant to include a pip list: Assimulo (2.8) decorator (4.0.2) gmpy2 (2.0.7) ipykernel (4.0.3) ipython (4.0.0) ipython-genutils (0.1.0) ipywidgets (4.0.2) Jinja2 (2.8) jsonschema (2.5.1) jupyter-client (4.0.0) jupyter-core (4.0.4) MarkupSafe (0.23) matplo

Re: [Matplotlib-users] bug report

Works fine for {{{ : python Python 2.7.10 (default, Sep 15 2015, 11:26:42) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. /Users/smithsp/.pyhistory >>> import matplotlib >>> matplotlib.__version__ '1.4.3' >

Re: [Matplotlib-users] bug in zorder example

It is doing it every where. Also look at the tick above the 2 on the bottom it is slightly clipped. It is definitely seems worse on the top, which might be showing a fence-post issue in the clipping/Agg rendering. As the OP points out zooming in on http://matplotlib.org/mpl_examples/pylab_exampl

Re: [Matplotlib-users] bug in zorder example

But, why is it doing that only along the top edge and not the other edges (or are my eyes that bad)? On Thu, May 7, 2015 at 11:30 AM, Thomas Caswell wrote: > zorder can be negative, if you want to ensure that all of your lines are > always below all of the standard axis components simple decreas

Re: [Matplotlib-users] bug in zorder example

zorder can be negative, if you want to ensure that all of your lines are always below all of the standard axis components simple decrease the zorder of the elements you want behind rather than increasing the zorder of the elements you want in front. @ben look at the top left of http://matplotlib.

Re: [Matplotlib-users] bug in zorder example

you can always change the zorder of the frame using set_zorder(). Are you talking about the frame of the legend or the plotting area? On Mon, Apr 6, 2015 at 11:23 AM, plotter wrote: > The second example on > http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to > expose a bug,

[Matplotlib-users] bug in zorder example

The second example on http://matplotlib.org/examples/pylab_examples/zorder_demo.html seems to expose a bug, which is clearly visible in the vector version: The blue curve with zorder=2 is plotted below the frame and all others with zorder >= 3 are plotted above the frame. This is because the frame

Re: [Matplotlib-users] Bug in matplotlib 1.4.2

On 2015/02/09 8:19 AM, Thomas Caswell wrote: > Can you test with 1.4.3rc1? I believe this has been fixed. Oops! Of course--I never use ',', and I was forgetting that it *is* just one pixel. Eric > > On Mon Feb 09 2015 at 1:07:28 PM Alex Böhnert > wrote: > >

Re: [Matplotlib-users] Bug in matplotlib 1.4.2

Thomas Caswell wrote > Can you test with 1.4.3rc1? I believe this has been fixed. I just built 1.4.3-rc1 (from the Download page->other Downloads -> Older/mics) from source. It seems to indeed be fixed there. Thanks a lot! -- View this message in context: http://matplotlib.1069221.n5.nabble

Re: [Matplotlib-users] Bug in matplotlib 1.4.2

On 2015/02/09 8:19 AM, Thomas Caswell wrote: > Can you test with 1.4.3rc1? I believe this has been fixed. I don't think so. I can reproduce it on master. Regardless of the "ms" kwarg, I see only a pixel. Eric > > On Mon Feb 09 2015 at 1:07:28 PM Alex Böhnert

Re: [Matplotlib-users] Bug in matplotlib 1.4.2

Can you test with 1.4.3rc1? I believe this has been fixed. On Mon Feb 09 2015 at 1:07:28 PM Alex Böhnert wrote: > Dear all, > > when plotting scattered data with the "," marker, the data points do not > show up either on screen (Qt4Agg backend) or in saved bitmap images (tested > with png); the

[Matplotlib-users] Bug in matplotlib 1.4.2

Dear all, when plotting scattered data with the "," marker, the data points do not show up either on screen (Qt4Agg backend) or in saved bitmap images (tested with png); they do show up if the plot is exported as pdf. Example code (run in "ipython --pylab" for simplicity): import numpy as np a =

Re: [Matplotlib-users] Bug in contourf or BoundaryNorm?

Hi Ian Thanks for your reply and help. I see your point. I guess it is only the BoundaryNorm where it would make sense to have contourf use the boundary levels from the norm. In my real problem described by the above example I have long forgotten the levs variable when I arrive at the contourf poi

Re: [Matplotlib-users] Bug in contourf or BoundaryNorm?

On 28 March 2014 12:56, Jesper Larsen wrote: > I believe the normalization behaviour is wrong for contourf at least when > using a BoundaryNorm. In the script below I am using the same norm to plot > the same data using contourf and pcolormesh. The color should change around > an x value of 0.15

[Matplotlib-users] Bug in contourf or BoundaryNorm?

Hi matplotlib users, I believe the normalization behaviour is wrong for contourf at least when using a BoundaryNorm. In the script below I am using the same norm to plot the same data using contourf and pcolormesh. The color should change around an x value of 0.15 but it is shifted somewhat for co

Re: [Matplotlib-users] Bug in Custom Dash List

I think the function should be np.all(dash_list <= 0.0) instead of np.any? This works 100% fine on my machine so I think it just hangs if all values are less than or equal to zero. That hangs on my machine as you stated. >From digging into that I also realized I could have put (None, None) to get

Re: [Matplotlib-users] Bug in Custom Dash List

The problem is that a 0-length dash or space is undefined. In Agg, it causes an infinite loop (presumably because the line cursor never moves). Saving it to a PDF file and opening it in Acrobat Reader reveals a blank page (presumably because it's doing something smarter, but also basically th

Re: [Matplotlib-users] Bug in Custom Dash List

@mdboom, from git blame, this looks to be specifically introduced by you via 7e7b5320on May 15th, and you even added some tests for handling path clipping. Perhaps the choice of "<=" should have been just "<"

[Matplotlib-users] Bug in Custom Dash List

I have old scripts I had made that I was rerunning in newer versions of matplotlib. They now fail because the function requires dashes to be greater than 0. I have them set to zero as below and it still throws the error. I had to set the zero in the middle to 1e-12 to get around this but is this th

Re: [Matplotlib-users] bug (annoyance) and fix in DraggableAnnotation.finalize_offset()

Šand this afternoon, shortly after I sent this email, my test cases for this approach abruptly stopped functioning. Whoops. So y'all may want to hold off on this. (I thought it looked too easyŠ) Been that kind of day. :) -jo On 7/2/13 11:57 AM, "Valentine Cooper, Jo" wrote: >Ran into a bug this

[Matplotlib-users] bug (annoyance) and fix in DraggableAnnotation.finalize_offset()

Ran into a bug this morning with draggable annotations. It would seem that finalize_offset() forcibly overrides the annotation's textcoords status to "axes fraction" so it can set the coordinates properly. That's all well and good, but if you were using some text coordinates system other than "axes

Re: [Matplotlib-users] Bug in twiny()

On Tue, Jun 4, 2013 at 3:58 AM, trendelkamp wrote: > Hi, > > there is a minor bug in the axes.twiny() function. Apparently the > parent axes xlim() values are not copied. > Example: > > from numpy import * > import matplotlib.pyplot as plt > > x=linspace(-2.0, 2.0, 100) > y=x**2 > > fig=plt.figur

[Matplotlib-users] Bug in twiny()

Hi, there is a minor bug in the axes.twiny() function. Apparently the parent axes xlim() values are not copied. Example: from numpy import * import matplotlib.pyplot as plt x=linspace(-2.0, 2.0, 100) y=x**2 fig=plt.figure() ax1=fig.add_subplot(111) ax1.plot(x, y) ax2=ax1.twiny() ax1.get_xlim

Re: [Matplotlib-users] Bug in cbook.exception_to_str() (mpl 1.2)

> Would you mind opening up an issue on github - this is definitely > a bug (http://matplotlib.org/faq/troubleshooting_faq.html). Done: https://github.com/matplotlib/matplotlib/issues/2104 Skip -- Get 100% visibility int

Re: [Matplotlib-users] Bug in cbook.exception_to_str() (mpl 1.2)

Agreed. I've seen this a couple of times but never reproduced it so elegantly. Would you mind opening up an issue on github - this is definitely a bug (http://matplotlib.org/faq/troubleshooting_faq.html). Thanks! P.S. Welcome to the mailinglist :-) On 31 May 2013 16:02, Skip Montanaro wrote:

[Matplotlib-users] Bug in cbook.exception_to_str() (mpl 1.2)

I'm not sure of the correct protocol (I just subscribed to report this problem), but the documentation said to report bugs here, and I saw no mention of this in Google searches of the list archives. The exception_to_str() function was changed between mpl 1.1 and 1.2. In my installation I show it g

Re: [Matplotlib-users] BUG: RuntimeError: dictionary changed size during iteration

Does this pull request: https://github.com/matplotlib/matplotlib/pull/1697 fix your issue? I have no way of knowing without a test case... Mike On 01/22/2013 08:33 AM, Massimiliano Costacurta wrote: Hello everyone, in my program I'm encountering an error when calling the function axes.set_

[Matplotlib-users] BUG: RuntimeError: dictionary changed size during iteration

Hello everyone, in my program I'm encountering an error when calling the function axes.set_xticks (Matplotlib 1.2.0 on python 2.7-64 bit). It is really difficult for me to build a test case, because my program is really complex. Here is the error traceback: File "C:\Python27\Lib\site-packages

Re: [Matplotlib-users] bug with empty values & dates

2012/11/22 Jeffrey Melloy : > I'm graphing data from a web service, and seem to have stumbled upon a > bug when dates are graphed without any values. > > Here's a minimum repro: > > import datetime > import matplotlib.pyplot as plt > > fig = plt.figure() > ax = fig.add_subplot(111) > > x = [] > st

[Matplotlib-users] bug with empty values & dates

I'm graphing data from a web service, and seem to have stumbled upon a bug when dates are graphed without any values. Here's a minimum repro: import datetime import matplotlib.pyplot as plt fig = plt.figure() ax = fig.add_subplot(111) x = [] st = datetime.datetime(2012,11,21) while st < datetim

Re: [Matplotlib-users] Bug when zooming on multiple lines separated by None

On 2012/10/03 8:11 AM, Charleux Ludovic wrote: > Thanks for your multiple answers. I'll try the same manipulation with > the 1.2 version as soon as possible. Concerning the debate between the > use of None and numpy.nan, I tryed both methods before posting and they > both lead to the same bug on my

Re: [Matplotlib-users] Bug when zooming on multiple lines separated by None

Thanks for your multiple answers. I'll try the same manipulation with the 1.2 version as soon as possible. Concerning the debate between the use of None and numpy.nan, I tryed both methods before posting and they both lead to the same bug on my version. I'm using the None/numpy.nan trick to plot fi

Re: [Matplotlib-users] Bug when zooming on multiple lines separated by None

On Wed, Oct 3, 2012 at 1:02 PM, Phil Elson wrote: > I don't get this on matplotlib/master (and therefore probably not on > 1.2rc2). > > I'm pretty sure masked array line plotting was fixed at some point this > release cycle (I cannot find the appropriate github issue to link to), so I > suggest t

Re: [Matplotlib-users] Bug when zooming on multiple lines separated by None

I don't get this on matplotlib/master (and therefore probably not on 1.2rc2). I'm pretty sure masked array line plotting was fixed at some point this release cycle (I cannot find the appropriate github issue to link to), so I suggest this is a known bug with 1.1.1 and fixed in 1.2. Just to be clea

Re: [Matplotlib-users] Bug when zooming on multiple lines separated by None

On 2012/10/03 4:24 AM, Charleux Ludovic wrote: > Hello, > > I want to plot multiple lines using matplotlib.pyplot.plot using the > None separator: when i zoom or plot lines that go far away from the axis > limits, they their direction is changed. I encounter a bug shown by the > folowing code: > >

Re: [Matplotlib-users] Bug when zooming on multiple lines separated by None

This works for me with 1.2 (not tested before that): import matplotlib.pyplot as plt import numpy as np x = np.array([0, 1, None, 1, 0]) y = np.array([0, 1, None, 0, 1]) plt.plot(x, y) plt.show() I get two distinct lines crossing each other at (0.5, 0.5) HTH, ---

Re: [Matplotlib-users] bug with bar graph when plotting zero values?

On Thu, Sep 27, 2012 at 1:07 PM, Benjamin Root wrote: > > > On Thursday, September 27, 2012, Pierre Haessig wrote: >> >> Hi Paul, >> >> Le 26/09/2012 18:14, Paul Tremblay a écrit : >> > I noticed today that when I create a bar graph with zero values that >> > the labels don't align correctly: >> >

Re: [Matplotlib-users] bug with bar graph when plotting zero values?

On Thursday, September 27, 2012, Pierre Haessig wrote: > Hi Paul, > > Le 26/09/2012 18:14, Paul Tremblay a écrit : > > I noticed today that when I create a bar graph with zero values that > > the labels don't align correctly: > > When I run your code with defects = [0, 0, 0, 5, 6, 7], I don't noti

[Matplotlib-users] bug with bar graph when plotting zero values?

I noticed today that when I create a bar graph with zero values that the labels don't align correctly: import matplotlib.pyplot as plt import numpy as np fig = plt.figure() names = ['name a', 'name b', 'name c', 'named', 'name e', 'name f'] defects = [0, 0, 0, 5, 6, 7] ax = fig.add_subplot(111) w

Re: [Matplotlib-users] Bug in colorbar()

On 2012/07/30 1:17 AM, Jeffrey Spencer wrote: > I'd agree as then it would work as pcolormesh or imshow does which when > passed in the same norm will only set vmin or vmax that wasn't > previously set. > > Assume this would be a really easy fix but I can have a look at > submitting a patch if some

Re: [Matplotlib-users] Bug in colorbar()

I'd agree as then it would work as pcolormesh or imshow does which when passed in the same norm will only set vmin or vmax that wasn't previously set. Assume this would be a really easy fix but I can have a look at submitting a patch if someone else isn't going to do so just let me know. Cheers,

[Matplotlib-users] Bug in contour plotting on 'cyl' basemap

When using an equidistant cylindrical projection over a selected subregion of the globe, e.g. map = Basemap(llcrnrlon=50,llcrnrlat=-80,urcrnrlon=300,urcrnrlat=70,projection='cyl'), any contour plot that I try and generate (i.e. any plot generated using the map.contour() function) cannot plot a

Re: [Matplotlib-users] Bug in colorbar()

On 2012/07/29 5:13 AM, Jeffrey Spencer wrote: > Eric, > > Normalize appears to be working correctly and as you stated above but > when passed into contourf appears to have inconsistent results not > following the docstring by allowing the value to change. > > Quick examples: > > X, Y = meshgrid(ara

Re: [Matplotlib-users] Bug in colorbar()

Eric, Normalize appears to be working correctly and as you stated above but when passed into contourf appears to have inconsistent results not following the docstring by allowing the value to change. Quick examples: X, Y = meshgrid(arange(20),arange(20)) Z = arange(20*20) Z = Z.reshape(20,20) no

Re: [Matplotlib-users] Bug in colorbar()

On 2012/07/28 10:17 PM, Jeffrey Spencer wrote: > Think I figured out an actual bug in the function: colors.Normalize(). > > The behavior states that if vmin or vmax is passed in as None it should > take the minimum or maximum value respectively. > > If only one value is passed into the function, bo

Re: [Matplotlib-users] Bug in colorbar()

Think I figured out an actual bug in the function: colors.Normalize(). The behavior states that if vmin or vmax is passed in as None it should take the minimum or maximum value respectively. If only one value is passed into the function, both values are overwritten to the min and max instead of j

Re: [Matplotlib-users] Bug in colorbar()

I figured out you can pass in the rasterized keyword to all of those to change the rasterization in the output. Also the docs say for pcolormesh it defaults to the backend if not set. Therefore, in the case of a vector based it would output vectors if not set to rasterize. Haven't tested but curi

Re: [Matplotlib-users] Bug in colorbar()

On 2012/07/26 10:26 PM, Jeffrey Spencer wrote: > Thanks, that is all good info to know. I change my data to log and > normalize it so the logNorm is just linear actually so specifying only > levels is fine. I'll let you know if that doesn't work properly for some > reason. > > Ok, yeah I looked at

Re: [Matplotlib-users] Bug in colorbar()

On 2012/07/26 9:20 PM, Jeffrey Spencer wrote: > import numpy as np > import matplotlib as mpl > X, Y = np.meshgrid(arange(20),arange(20)) > Z = np.arange(20*20) > Z = Z.reshape(20,20) > logNorm = mpl.colors.Normalize(vmin=0,vmax=200) > fig = mpl.pyplot.figure(10) > ax = fig.add_subplot(111) > surf

Re: [Matplotlib-users] Bug in colorbar()

I am using 1.2.X and here is a minimalist example to see what happens: Link to figure of output: https://dl.dropbox.com/u/13534143/example.png Example: import numpy as np import matplotlib as mpl X, Y = np.meshgrid(arange(20),arange(20)) Z = np.arange(20*20) Z = Z.reshape(20,20) logNorm = mpl.c

Re: [Matplotlib-users] Bug in colorbar()

Further after doing a little digging the code in matplotlib.colorbar.Colorbar looks correct to me but doesn't work correctly. It essentially ignores the norm value because always sets the norm to the norm for the contour plot (eg. mappable.norm) which this is the same norm with vmin and vmax value

Re: [Matplotlib-users] Bug in colorbar()

On 2012/07/26 7:52 PM, Jeffrey Spencer wrote: > I am trying to make a plot with a colorbar that has a reduced axis over > which the colorbar is executed. > > This is set via passing in a norm to contourf: > logNorm = colors.Normalize(vmax=0,vmin=-100) > surf = ax.contourf(X,Y,logZ

[Matplotlib-users] Bug in colorbar()

I am trying to make a plot with a colorbar that has a reduced axis over which the colorbar is executed. This is set via passing in a norm to contourf: logNorm = colors.Normalize(vmax=0,vmin=-100) surf = ax.contourf(X,Y,logZ, map_scale, cmap=cm.jet, norm=logNorm) The output of this

Re: [Matplotlib-users] [Bug] : yaxis presentation going wrong if ymin/ymax < .000x (x~ 5)

Hello 2012/4/24 Eric Firing : > On Tue, Apr 24, 2012 at 12:21 AM, Tony Yu wrote: >> On Mon, Apr 23, 2012 at 5:09 AM, jul tayon wrote: >>> Hello list >>> Exected Result : >>> https://github.com/jul/pypi-stat/blob/master/why.png >>> >> Sorry, I'm not clear on what the bug is. Is the picture you li

Re: [Matplotlib-users] [Bug] : yaxis presentation going wrong if ymin/ymax < .000x (x~ 5)

On Tue, Apr 24, 2012 at 12:21 AM, Tony Yu wrote: > > > On Mon, Apr 23, 2012 at 5:09 AM, jul tayon wrote: >> >> Hello list >> >> matplotlib website says this mailing  is the prefered way to report >> bug, so here I am : >> >> System : >> python ; 2.7.2+ >> matplotlib 1.1.0 >> ubuntu TLS amd64 >> m

Re: [Matplotlib-users] [Bug] : yaxis presentation going wrong if ymin/ymax < .000x (x~ 5)

On Mon, Apr 23, 2012 at 5:09 AM, jul tayon wrote: > Hello list > > matplotlib website says this mailing is the prefered way to report > bug, so here I am : > > System : > python ; 2.7.2+ > matplotlib 1.1.0 > ubuntu TLS amd64 > matplotlib Backend : TkAgg > > > How to reproduce (on my pf) > Code S

Re: [Matplotlib-users] [Bug] : yaxis presentation going wrong if ymin/ymax < .000x (x~ 5)

Sorry, I thougt I used the wrong address for mailing and resent. :'( -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it

[Matplotlib-users] [Bug] : yaxis presentation going wrong if ymin/ymax < .000x (x~ 5)

Hello list matplotlib website says this mailing is the prefered way to report bug, so here I am : System : python ; 2.7.2+ matplotlib 1.1.0 ubuntu TLS amd64 matplotlib Backend : TkAgg How to reproduce (on my pf) Code Snippet : ##CODE import matplotlib import matplotlib.pyplot as p import

[Matplotlib-users] [bug] triggering a quite unreadable yaxis labelling

Hello list matplotlib website says this mailing is the prefered way to report bug, so here I am : System : python ; 2.7.2+ matplotlib 1.1.0 ubuntu TLS amd64 matplotlib Backend : TkAgg How to reproduce (on my pf) Code Snippet : ##CODE import matplotlib import matplotlib.pyplot as p import

Re: [Matplotlib-users] Bug in legend?

Handling alpha can become very tricky with matplotlib. The problem is not specific for legend thing, but how attribute of patches are updated when the update_from method is called. Here is an example. from matplotlib.patches import Patch pa1 = Patch(alpha=None, fc='none', ec='b') pb1 = Pat

Re: [Matplotlib-users] Bug in Triangulation causes infinite loop if 4 or more duplicate points are used in tricontour()

On Monday, 16 April 2012 at 16:34, Kacper Kowalik wrote: > > On 16 Apr 2012 22:31, "Damon McDougall" (mailto:d.mcdoug...@warwick.ac.uk)> wrote: > > > > Hi Kacper, > > > > Just to be clear, is it tri.Triangulation(x, y) that hangs, or is it > > plt.tricontour(…)? > It's plt.tricontour that han

Re: [Matplotlib-users] Bug in Triangulation causes infinite loop if 4 or more duplicate points are used in tricontour()

On 16 Apr 2012 22:31, "Damon McDougall" wrote: > > Hi Kacper, > > Just to be clear, is it tri.Triangulation(x, y) that hangs, or is it plt.tricontour(…)? It's plt.tricontour that hangs, tri.Triangulation properly issues warning about duplicates. Cheers, Kacper > -- > Damon McDougall > d.mcdoug..

Re: [Matplotlib-users] Bug in Triangulation causes infinite loop if 4 or more duplicate points are used in tricontour()

Hi Kacper, Just to be clear, is it tri.Triangulation(x, y) that hangs, or is it plt.tricontour(…)? -- Damon McDougall d.mcdoug...@warwick.ac.uk (mailto:d.mcdoug...@warwick.ac.uk) http://damon.is-a-geek.com B2.39 Mathematics Institute University of Warwick Coventry West Midlands CV4 7AL United

[Matplotlib-users] Bug in Triangulation causes infinite loop if 4 or more duplicate points are used in tricontour()

Hi, I haven't been able to pin point it exactly but following script: import matplotlib.pyplot as plt import matplotlib.tri as tri import numpy as np from numpy.random import uniform, seed seed(0) npts = 200 x = uniform(-2,2,npts) y = uniform(-2,2,npts) z = x*np.exp(-x**2-y**2) y[1:3] = x[0] #

Re: [Matplotlib-users] Bug in legend?

On Mon, Apr 16, 2012 at 4:58 AM, Yannick Copin wrote: > Hi List, > > I think I found a bug in legend of a fill command (see attached code and > figure) when the facecolor is 'none' but the alpha is not None (I'm using > latest matplotlib 1.1.0). If confirmed, should I fill in a but report? I see

Re: [Matplotlib-users] Bug (?) in version 1.1.0 (Can't set Attribute)

On 03/07/2012 04:51 AM, Giovanni Plantageneto wrote: > Dear all, > after upgrading to 1.1.0 on my linux machine (from debian-backports), I > get an error (Can't set Attribute) with code looking like this: > > from pylab import figure > F=figure() > F.axes=[] > > Why is this so? Incidentally, going

[Matplotlib-users] Bug (?) in version 1.1.0 (Can't set Attribute)

Dear all, after upgrading to 1.1.0 on my linux machine (from debian-backports), I get an error (Can't set Attribute) with code looking like this: from pylab import figure F=figure() F.axes=[] Why is this so? Incidentally, going back to the previous available version (0.99.3) solves the problem. C

[Matplotlib-users] Bug in basemap allskymap example

Hi, the Basemap allskymap example (examples/allskymap.py in current git and basemap rev 1.0.2) plots buggy tissots if they cross the zero meridian and/or the poles (see http://web.physik.rwth- aachen.de/~winchen/unfixed_polarRegions_llskymap.png ). The attached patch fixes this issue (see http:

Re: [Matplotlib-users] [Bug] Bar plot with log scale on y axes

On Monday, January 23, 2012, Álvaro Justen [Turicas] wrote: > Hello, > I'm using version 1.0.1 and I think this code snippet and the images > attached are enough to explain the bug: > https://gist.github.com/1667300 > > Images 'bar-log-bug.png' and 'bar-log-ok.png' must be the same since > it is t

[Matplotlib-users] [Bug] Bar plot with log scale on y axes

Hello, I'm using version 1.0.1 and I think this code snippet and the images attached are enough to explain the bug: https://gist.github.com/1667300 Images 'bar-log-bug.png' and 'bar-log-ok.png' must be the same since it is the same data and same configuration - the bug occurs when we call set_ysca

Re: [Matplotlib-users] Bug in griddata

Thanks for the report, Ethan, Ethan Swint, on 2012-01-10 16:34, wrote: > Can anyone else reproduce? Confirming, this is a bug. We need to change the matplotlib code, but I'm not sure how to proceed. I've filed it as the ominously numbered matplotlib issue #666 https://github.com/matplotlib/matp

[Matplotlib-users] Bug in griddata

Hi- I was working off of the example listed at http://matplotlib.sourceforge.net/examples/pylab_examples/griddata_demo.html, adapting it to my own data, and encountered the following error on MLAB 1.1.0, Python 2.7.2: from numpy.random import uniform, seed from matplotlib.mlab import griddata

Re: [Matplotlib-users] [BUG] autofmt_xdate = graph cropped wrongly

Done! https://github.com/matplotlib/matplotlib/issues/654 Thanks for the support. On Mon, Jan 2, 2012 at 16:28, Benjamin Root wrote: > On Mon, Jan 2, 2012 at 11:25 AM, Álvaro Justen [Turicas] > wrote: >> >> Hello, >> When I use Figure.autofmt_xdate (it uses rotation by default) the >> graph is

Re: [Matplotlib-users] [BUG] autofmt_xdate = graph cropped wrongly

On Mon, Jan 2, 2012 at 11:25 AM, Álvaro Justen [Turicas] < alvarojus...@gmail.com> wrote: > Hello, > When I use Figure.autofmt_xdate (it uses rotation by default) the > graph is not moved/scaled so it is cropped in the image. > I noticed this problem when I was trying to crop white border in > ima

Re: [Matplotlib-users] bug in fcontour with v1.1.0 ?

On 12/06/2011 12:43 AM, Arnaud wrote: > Hello, and thank you for this answer. > > I do not care that much of the colorbar, i added it to make sure the > range actually started at 0. > I used the contour function to that purpose too i.e. to show that my > function actally ranged from 0 to 100. > >

Re: [Matplotlib-users] bug in fcontour with v1.1.0 ?

Hello, and thank you for this answer. I do not care that much of the colorbar, i added it to make sure the range actually started at 0. I used the contour function to that purpose too i.e. to show that my function actally ranged from 0 to 100. Removing both colorbar and contour, i have the same

Re: [Matplotlib-users] bug in fcontour with v1.1.0 ?

On 12/05/2011 10:00 AM, Arnaud wrote: > Hello, > > I am new to this list, but not totally to matplotlib. > I installed v1.1.0 lately, and i noticed that something went wrong (or, > not as before) with fcontour(). > It looks like the range of colors used to fill in, is not set correctly. > Sorry, i

[Matplotlib-users] bug in fcontour with v1.1.0 ?

Hello, I am new to this list, but not totally to matplotlib. I installed v1.1.0 lately, and i noticed that something went wrong (or, not as before) with fcontour(). It looks like the range of colors used to fill in, is not set correctly. Sorry, i cannot really tel it better, but i have a piece of

[Matplotlib-users] Bug or feature: bbox of maps

The original message with attachments are still being held because of file size, so I am reposting here without the attachments... -- Forwarded message -- From: Arlindo da Silva Date: Mon, Nov 21, 2011 at 10:45 PM Subject: Bug or feature: bbox of maps To: Matplotlib-users@lists.so

Re: [Matplotlib-users] Bug or feature: bbox of maps

On 11/21/11 8:45 PM, Arlindo da Silva wrote: Hi, (A similar issue was reported back in 7/4/11 without a definite solution, so I am reposting with some additional diagnostics. ) Up to Matplotlib 0.99 (EPD 6.3) the code snippet below produced a plot with an aligned colorbar as in the attache

Re: [Matplotlib-users] bug in set_autoscalez_on in mplot3d 1.1.0

On 11/6/2011 11:18 AM, krastanov.ste...@gmail.com wrote: > /usr/lib/pymodules/python2.7/mpl_toolkits/mplot3d/axes3d.pyc in > set_autoscale_on(self, b) > 252 """ > 253 Axes.set_autoscale_on(self, b) > --> 254 self.set_autoscalez_on(self, b) > 255 > 256 def s

[Matplotlib-users] bug in set_autoscalez_on in mplot3d 1.1.0

/usr/lib/pymodules/python2.7/mpl_toolkits/mplot3d/axes3d.pyc in set_autoscale_on(self, b) 252 """ 253 Axes.set_autoscale_on(self, b) --> 254 self.set_autoscalez_on(self, b) 255 256 def set_autoscalez_on(self, b) : TypeError: set_autoscalez_on() takes exa

[Matplotlib-users] Bug/error when zooming

[Reposting this because it has been "pending" for 2 days] With the Mac OS X backend (at least…), when zooming (with the rubberband rectangle), error messages are repeatedly printed when the mouse leaves (goes outside) the axes rectangle: Traceback (most recent call last): File "/opt/local/Li

Re: [Matplotlib-users] bug report and fix for bracket arrow (annotations)

Thanks for reporting this. This is now fixed in the v1.0.x-maint branch and the master branch. Regards, -JJ On Sat, Sep 17, 2011 at 10:33 AM, Daniel Hyams wrote: > In  http://matplotlib.sourceforge.net/users/annotations_guide.html , > about 1/3 of the way down, there is a little demonstrator f

[Matplotlib-users] bug report and fix for bracket arrow (annotations)

In http://matplotlib.sourceforge.net/users/annotations_guide.html , about 1/3 of the way down, there is a little demonstrator for the different arrowstyles ->, <-, ]-, etc. Looking at the figure closely, there is no difference between the "-[" and "]-" styles. The fix for this is in patches.py,

Re: [Matplotlib-users] Bug in scatter

On 08/19/2011 09:19 AM, Andre' Walker-Loud wrote: >> >> I agree that this is a bug. (I suspect it is a malign side-effect of >> some attempt to make bar plots work with a log scale, but I haven't >> tracked it down.) What is less clear is the desired behavior. Raise an >> exception? Silently dele

Re: [Matplotlib-users] Bug in scatter

> > I agree that this is a bug. (I suspect it is a malign side-effect of > some attempt to make bar plots work with a log scale, but I haven't > tracked it down.) What is less clear is the desired behavior. Raise an > exception? Silently delete the points that are invalid with a log scale? >

Re: [Matplotlib-users] Bug in scatter

On 08/18/2011 10:03 PM, Richard Neher wrote: > Hi folks, > > it seems to me that there is a bug in scatter when using log scale. Have > a look at the output of the following script: > > frompylab import* > > print matplotlib.__version__ > x=arange(10) > plot(x, exp(-x)) > ax=gca() > ax.set_yscale('

Re: [Matplotlib-users] Bug in scatter

Hi Richard, I've submitted this a while ago to the mailing list [1] as well, but nobody answered. :-( Hopefully, somebody knows an answer this time. - Marcel [1] http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/msg20684.html Am 19

[Matplotlib-users] Bug in scatter

Hi folks,it seems to me that there is a bug in scatter when using log scale. Have a look at the output of the following script:from pylab import *print matplotlib.__version__x=arange(10)plot(x, exp(-x))ax=gca()ax.set_yscale('log')scatter(x, exp(-x), label= 'works fine')scatter(x, zeros(10), marker=

Re: [Matplotlib-users] Bug in errorbar

On Fri, Aug 5, 2011 at 2:41 PM, Amir Jahanshahi wrote: > Hi , > > The code for image-windows and image-linx comes from here: > > http://matplotlib.sourceforge.net/examples/pylab_examples/errorbar_limits.html > > That is why I think the problem is in linux. And the pdf which is attached > along wi

Re: [Matplotlib-users] Bug in errorbar

Hi , The code for image-windows and image-linx comes from here: http://matplotlib.sourceforge.net/examples/pylab_examples/errorbar_limits.html That is why I think the problem is in linux. And the pdf which is attached along with the png image named flow-rate are executed in linux which are differ

Re: [Matplotlib-users] Bug in errorbar

On Fri, Aug 5, 2011 at 9:29 AM, Amir Jahanshahi wrote: > Dear folks, > > I have this problem consistently in 0.99 installed via package > respiratory and also 1.0.1 from source. This only occurs in linux. > Windows is OK. see attachments please. If I run flow-rate.py the output > of plt.show() is

Re: [Matplotlib-users] bug in matplotlib.text.Text

Great. Thank you. I will check the master branch before reporting next time. Andrea > On Wed, Jul 27, 2011 at 10:07 AM, Andrea Pierleoni > wrote: > >> Hi all, >> >> I found that a matplotlib.text.Text istance reports wrong coordinates >> when >> converted to str >> I'm using version 1.0.1 >> >> t

Re: [Matplotlib-users] bug in matplotlib.text.Text

On Wed, Jul 27, 2011 at 10:07 AM, Andrea Pierleoni wrote: > Hi all, > > I found that a matplotlib.text.Text istance reports wrong coordinates when > converted to str > I'm using version 1.0.1 > > this is the code in Text class: > > def __str__(self): >return "Text(%g,%g,%s)"%(self._y,self.

[Matplotlib-users] bug in matplotlib.text.Text

Hi all, I found that a matplotlib.text.Text istance reports wrong coordinates when converted to str I'm using version 1.0.1 this is the code in Text class: def __str__(self): return "Text(%g,%g,%s)"%(self._y,self._y,repr(self._text)) it is clearly reporting two times the y coordinates,

  1   2   3   4   >