gmane.comp.python.matplotlib.devel

"Live Security Virtual Conference" ad

Jason Grout — 2012-05-26T05:11:15

I just noticed at the bottom of each message in a dozen or so that I 
checked from the last few days, I see an ad entitled "Live Security 
Virtual Conference".  I don't see these ads on messages in the 
sourceforge archive [1], but I do see them on the gmane mirror [2].  I 
also see the ad in a reply on the sourceforge archive [3].

I'm curious: Is this ad being put into outgoing messages by sourceforge, 
but not included in the archive (except when explicitly quoted in a 
reply)?  Or is there some other source for the ad?

Thanks,

Jason

[1] http://sourceforge.net/mailarchive/message.php?msg_id=29253604

[2] http://thread.gmane.org/gmane.comp.python.matplotlib.devel/11060

[3] http://sourceforge.net/mailarchive/message.php?msg_id=29253751

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endp

'NoneType' object has no attribute 'endswith'when running tests in a chroot

Sandro Tosi — 2012-05-20T16:51:44

Hello,
I've been trying to fix this problem for hours, and it's getting me
mad but to no conclusion, so I'm asking here.

In Debian we build our packges in a chroot, with all the minimum
dependecies needed to build the package (to guarantee reproducibility
and avoid weird effect of local installed packages), and so also the
unittests are runt here. While enabling the matplotlib unittest in
that chroot, I'm getting this error:

======================================================================
ERROR: matplotlib.tests.test_axes.test_arc_ellipse.test
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
line 36, in failer
    result = f(*args, **kwargs)
  File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",

Plans for matplotlib py3k/final release (andimpact on Debian)

Sandro Tosi — 2012-05-12T09:56:13

Hello,
as you may be aware of, in 1 month (more or less) Debian will freeze,
that means that no new upstream releases will be allowed in the
upcoming release, only fixex for important bugs.

Currently in Debian archive we have 1.1.1rc1 . Recent mails have
mentioned that the next release will be py3k enabled. Well, what are
you're plans to release such version? :)

It would be really awesome to have a python3 matplotlib in Debian, and
i'd be happy to test any new RC you'd like to release.

Cheers,

switching rc files (and discussion of styles)

Paul Ivanov — 2012-05-11T20:17:48

Hey everyone,

I wanted to highlight Matthew Emmett's (memmett) PR in progress [1] that
brings the ability to switch between rcParams.

Matthew's implementation started with just being able to read in and use
an rcParam file, and I suggested the idea of having a context manager,
that would allow you to do something like:

  with rc_context(fname):
      plt.plot()
      ...

and have the rcParams restored outside of the context.

I know there have been a few threads (can't find links now for some
reason) and in-person discussions in the past about having this kind of
ability in matplotlib, and having an idea of "styles", and Tony Yu
implemented a variant of this on top of matplotlib in mpltools [2], but
I wanted to ping the list here for other ideas and feelings about such
functionality (if anyone can find pointers to previous discussions, that
would be very welcome).

1. https://github.com/matplotlib/matplotlib/pull/861
2. https://github.com/tonysyu/mpltools

best,
--
Paul Ivanov
314 address only used for l

Inconsistency between JPEG and PNG images by matplotlib.image.imread()

kasper — 2012-05-10T08:15:03

Hello list,

In working with matplotlib in a Python course we discovered an inconsistency in importing various image files. When importing a JPEG file a numpy array containing ints (0-255) is returned, but when a PNG is imported an array containing floats (0-1) is returned.
The obvious solution is checking for filetype during read and then dividing by 255, but this seems awkward to do outside the library. Also, as discussed at [1] there is the matter of 16 (or 8+) bit images, which might complicate things.
Is there a consensus on how to handle this in code using matplotlib?

Kind regards,

Kasper Loopstra.


[1]: https://github.com/matplotlib/matplotlib/pull/616
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.acc

code review: Adding angle offset to start of apie chart

Ezra Peisach — 2012-05-08T10:51:23

After being fed up with no easy way to adjust the start angle of a pie
chart, I have added an optional argument to axes.pie called startangle
that allows one to specify the start angle of a pie chart.

I have updated the documentation - but would a new sample file showing a
side by side output comparison be warranted as well?
I had to regenerate a portion of pyplot.py using biolerplate.py - and
that is why the pctdistance changed very slightly....

Feedback welcome.

The url on github is:

https://github.com/epeisach/matplotlib/compare/master...pie_angle


Ezra


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Qt close bug revisited

Tony Yu — 2012-05-05T19:44:02

I'm getting a strange error when multiple figures are created *without a
call to show*. Here's the traceback:

Traceback (most recent call last):
  File
"/Users/Tony/python/devel/mpl/lib/matplotlib/backends/backend_qt4.py", line
151, in <lambda>
    lambda: self.close_event())
  File "/Users/Tony/python/devel/mpl/lib/matplotlib/backend_bases.py", line
1564, in close_event
    self.callbacks.process(s, event)
AttributeError: 'FigureCanvasQTAgg' object has no attribute 'callbacks'


Here's a simple test case:

import matplotlib.pyplot as plt
fig = plt.figure()
plt.plot([0, 1])
fig = plt.figure()
plt.plot([0, 1])


This issue appears in versions after the PR to fix the Qt4 close
bug<https://github.com/matplotlib/matplotlib/pull/716>.
The error occurs even without the `plot` calls, but the failures aren't as
consistent (the error will randomly disappear).

Note that sticking a call to `plt.show()` at the end and then manually
closing the figures does not seem to produce this error. I'm having a
difficult time lo

wxMPL patch

Chris Barker — 2012-04-30T18:16:07

Hi Folks,

I can't seem to find Ken McIvor -- Ken are you here?

Anyway, here's a tiny patch of wxMPL to make it work with wxPython 2.9

bug in font display using png backend

Detlef Maurel — 2012-04-23T14:33:15

Hi all,

there is a problem in the font display in the newest trunk version of 
matplotlib (git rev. 76665d059523cf)

I ran a clean installation and the test script. You can see in the 
attachment that the fonts are somehow screwed up. It seems to depend on 
the graphics backend. In the screenshot, the title is broken. In the png 
output, only the axis labels are broken. In the pdf, everything looks fine.

It looks like this bug has been introduced after tag v1.1.0 (I switched 
back to the tag and the fonts look fine there).

If you want me to run further tests, please let me know.


Detlef
basedirlist is: ['/usr/local', '/usr']
============================================================================
BUILDING MATPLOTLIB
            matplotlib: 1.2.x
                python: 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)  [GCC
                        4.5.2]
              platform: linux2

REQUIRED DEPENDENCIES
                 numpy: 1.7.0.dev-dafb2dd
             freetype2: found, but unknown version (no pkg-

imsave() and cmap

Benjamin Root — 2012-04-16T21:10:31

Thanks to a patch a bit while back for ListedColormap that allowed for
alphas to be given, I should now be able to use imshow() and imsave() with
colormaps.  However, I find that the results are not correct. Particularly,
the alpha values seem to be assigned incorrectly.  I am still working on
making a stand-alone version to demonstrate the problem, but has anyone
else noticed this?

Note,

plt.imshow(d, cmap=cm)

produces an incorrect result while

plt.imshow(cm(d))

produces a correct result.  However, due to a bug in imsave, I can't do the
latter as a work-around.

Thanks,
Ben Root
------------------------------------------------------------------------------
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 FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.

Saving animations

Tony Yu — 2012-04-07T17:34:12

I've been using the animations subpackage since it was introduced, but I
only recently tried to save an animation using the `save` method.
Unfortnately, I get a RuntimeError whenever I try to use it:

...
  File
"/Users/Tony/python/devel/mpl/lib/matplotlib/backends/backend_agg.py", line
4
52, in print_raw
    renderer._renderer.write_rgba(filename_or_obj)
RuntimeError: Error writing to file


This can be reproduced with any animation example, e.g.
simple_anim.py<http://matplotlib.sourceforge.net/examples/animation/simple_anim.html>,
by
replacing `plt.show()` with `ani.save('simple_anim.avi')`. The actual error
is from a shell call to ffmpeg, which roughly boils down to:

#~~~~
    import subprocess
    import matplotlib.pyplot as plt

    fig, ax = plt.subplots()
    ax.plot([0, 1])
    command = ['ffmpeg', '-f', 'rawvideo', '-vcodec', 'rawvideo',
               '-s', '800x600', '-pix_fmt', 'rgba', '-r', '5.0',
               '-i', 'pipe:', '-vcodec', 'mpeg4', '-y', 'test.avi']
    proc= subprocess.Popen(com

PATCH: Accept color/alpha in imsave

Jostein Bø Fløystad — 2012-04-07T15:25:55

I've had problems saving MxNx3 (RGB) numpy arrays as images using
imsave. It fails with an exception, and the problem seems to be line
1243 in image.py:

figsize = [x / float(dpi) for x in arr.shape[::-1]]

The purpose of arr.shape[::-1] seems to be to reorder the height and
width dimensions. It works as intended for MxN arrays, but not NxMx3
arrays -- they cause a function to complain about an argument too
many.

I have modified the above line to use (arr.shape[1], arr.shape[0])
instead of arr.shape[::-1], and that solves the problem for me, and I
get the output I expect (and the code still passes all tests it should
pass). However, there could very well be subtleties in the codebase
that I don't know about.

The attached patches add a simple test case, the above mentioned
change and a few updates to the documentation of imsave.

Best,

Jostein.
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tel

Unavoidable gridlines in pcolor pdf output

Michael Gilbert — 2012-04-06T18:04:01

Hi,

It seems that savig a pcolor plot to a pdf format always includes
gridlines, which isn't true for other output formats like png.  The
attached example demonstrates this problem.  I've only tested this on
version 1.1.1rc1.

Thanks,
Mike
------------------------------------------------------------------------------
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 FREE!
http://p.sf.net/sfu/Boundary-d2dvs2_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Drawing arbitrary Axis on a plot

Phil Elson — 2012-04-03T15:52:18

Before I dive too far down a rabbit hole, I wanted to sound out a few
questions related to adding custom Axis & associated gridlines to a
plot.


I want to be able to put an arbitrary axis on top of a plot in some
other projection (a simple, but not necessarily useful example, is a
pair Cartesian axes at the centre of a polar plot).
Some of my requirements are:

 * The Axis should represent a known transform, without the transform
necessarily being transData (a non-affine transformation from the
former to the latter is known).

 * The Axis is likely to be curved, and gridlines will not always
reach the edges of the background patch (I appreciate that the fact
that the gridlines not always crossing the background patch makes it
harder to identify the domain of the required Axis and accept that it
may be necessary to provide some additional information to help this
case).

 * The API should be consistent with standard mpl Axis objects (i.e.
Locators, Formatters, and all the expected control of
colour/visibilit

Inconsistent naming of legend points

Pim Schellart — 2012-03-30T14:39:27

Dear all,

there is an inconsistency in the naming of the variable that describes
the number of points to display in the legend.
For `plt.plot` and `plt.errorbar` it is called "numpoints" but for
`plt.scatter` it is called "scatterpoints".
It would be less confusing if both could be set with a simple
"numpoints" in the legend function.
Please let me know what you think.

Kind regards,

Pim Schellart

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

soliciting feedback on proposed user survey

Paul Ivanov — 2012-03-29T00:22:11

Hey everyone,

with 1.1.1 just around the corner, I thought it'd be nice to put
together an MPL user survey, similar to what Thomas Kluyver
organized for IPython last year [1].

Here's what I've got so far [2], and here's the response one gets
upon filling out the form:

-----
Thanks for your feedback.

As promised, here are the details of how to do various things:

the official documentation is at: 
    http://matplotlib.sourceforge.net/

to run the test suite:
    python -c "import matplotlib; matplotlib.test()"

file bug reports and submit pull requests here: 
    https://github.com/matplotlib/matplotlib

to post to the matplotlib-users list, subscribe here:
    https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-----

with an additional link at the bottom to look at the summary of previous
respondents, which looks like [3].

How does this look to everyone? Any changes before I distribute
this more widely? (Preferably not just via list, but also add a
link to it on the main page, which is what

1.1.1rc RuntimeError: underlying C/C++ objecthas been deleted

Neal Becker — 2012-03-28T12:34:13

I'm getting these messages, which did not occur with 1.1:

Traceback (most recent call last):
  File "/home/nbecker/.local/lib/python2.7/site-
packages/matplotlib/backends/backend_qt4.py", line 151, in <lambda>
    lambda: self.close_event())
  File "/home/nbecker/.local/lib/python2.7/site-
packages/matplotlib/backend_bases.py", line 1564, in close_event
    self.callbacks.process(s, event)
RuntimeError: underlying C/C++ object has been deleted


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

1.1.1rc does not fix tight_layout for figtext?

Neal Becker — 2012-03-28T12:17:11

I just tried 1.1.1rc to see if it fixed the tight_layout for figtext.  

I have a semilogy plot, and add  some lines of text on the bottom (and top):

        plt.figtext (0, 0, res['carriers'].values, horizontalalignment='left', 
verticalalignment='bottom', size=5)
        plt.figtext (0.5, 1, self.pageno, horizontalalignment='left', 
verticalalignment='top', size='x-small')
        ##plt.tight_layout(pad=1.0)
        plt.tight_layout()

The text on the bottom is overprinting the x axis - the same as happened  with 
the previous release.


------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

Using `hexbin` with `edgecolors = 'none'`

Tony Yu — 2012-03-26T23:42:20

I'm drawing hexbins with alpha < 1 and get dark lines at the bin edges. It
turns out that setting `edgecolors = 'none'` sets the edge color to be the
same as the face color, as mentioned in the docstring:

           If ``'none'``, draws the edges in the same color as the fill
color.
           This is the default, as it avoids unsightly unpainted pixels
           between the hexagons.

This behavior is a bit weird, since setting colors to 'none' usually makes
the element invisible. Wouldn't it be more consistent to let 'none' be
passed to the PolyCollection (which draws the hexbins), such that edges
aren't drawn. Then, to maintain the current behavior, change the default to
'face'. (Of course, this wouldn't really maintain current behavior for code
that explicitly passes `edgecolors='none'`.)

Also, if I let 'none' get passed to the PolyCollection, I don't see the
"unsightly unpainted pixels between the hexagons". Is this just a
system-dependent artifact, or is it an outdated docstring?

Thanks,
-Tony
----

matplotlib v1.1.1 (bugfix) rc1 on Thursday

John Hunter — 2012-03-19T17:58:02

I think we are pretty close to cleaning up issues and PRs related to
v1.1.x, so I'd like to cut the release candidate this Thursday.  Let's
continue to hammer on closing open issues and pull requests, and flag
anything that needs to be addressed before the release as
"release_critical" in the issue tracker.  If there are show stoppers I am
not aware of, chime in.

Thanks,
JDH
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Is snapping still right?

Benjamin Root — 2012-03-17T19:49:56

I know this has been addressed so many times, but as I was testing out
mplot3d in v1.1.x, I swear the axes lines were aliasing like crazy at some
viewing angles.  If it is just mplot3d, then probably should not hold up
the bugfixes release, but maybe we should get some eyes on the test results
before releasing???

Ben Root
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel