[matplotlib-devel] navigation toolbar keyboard shortcuts patch
Hi, I'm a big fan of keyboard shortcuts, so I decided to add these guys to lib/matplotlib/backend_bases.py I'm not sure if this is too much, and maybe these should be configurable down the line, but here's my first stab at it, what do you all think? in the same order as they appear in the toolbar: 'h' or 'r' for Home/Reset left arrow or 'z' or backspace for Back right arrow and 'x' for Forward 'p' for pan axes with right, zoom with left mode toggle 'o' for z*o*om to rectangle mode toggle 's' for save 'z' and 'x' I borrowed from the Opera browser, very handy to for righties who can have their left hand on the keyboard while using the mouse. I decided to use 'o' for zoom to rect since it's located right next to the 'p' for panning, and both are modes. There was also a message on the matplotlib-users list in July that this patch would be useful for Subj: [Matplotlib-users] tool bar help / feature request From: Ben Axelrod <[EMAIL PROTECTED]> - 2008-07-31 16:08 (but I don't know how to reply to that message as I was not on the the users list at that time) cheers, Paul Ivanov Index: matplotlib/lib/matplotlib/backend_bases.py === --- matplotlib/lib/matplotlib/backend_bases.py (revision 6232) +++ matplotlib/lib/matplotlib/backend_bases.py (working copy) @@ -1513,6 +1513,23 @@ if event.key == 'f': self.full_screen_toggle() + +# *h*ome or *r*eset mnemonic +elif event.key == 'h' or event.key == 'r' or event.key == "home": +self.canvas.toolbar.home() +# z and x to enable left handed quick navigation +elif event.key == 'left' or event.key == 'z' or event.key == 'backspace': +self.canvas.toolbar.back() +elif event.key == 'right' or event.key == 'x': +self.canvas.toolbar.forward() +# *p*an mnemonic +elif event.key == 'p': +self.canvas.toolbar.pan() +# z*o*om mnemonic +elif event.key == 'o': +self.canvas.toolbar.zoom() +elif event.key == 's': +self.canvas.toolbar.save_figure(self.canvas.toolbar) if event.inaxes is None: return - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] navigation toolbar keyboard shortcuts patch
Here's an updated patch:
I decided to go with 'c' and 'v' for Back and Forward since these keys
are in the same place on most localized keyboard layouts (sorry, dvorak
users) (as JDH pointed out, I could not use 'z' and 'x' because 'x' is
used as a modifier in Pan/Zoom mode)
I've added a ReST table detailing all of the key bindings as per JDH's
suggestion.
I included 'g' and 'l' for toggling grid and y scale under the heading
of "In axes only" though there's probably a better way of saying that.
Not sure if those belong there, but they seem to have not been
documented elsewhere ( same with 'f' for fullscreen)
navigation_toolbar.rst compiled and looked fine with rst2html.py and
rst2newlatex.py. The bullets ('- ') created extra vertical whitespace in
the table when I ran latex on the rst2latex.py output. If that's a
problem, those can be replaced with '-- '
looking forward to your feedback,
Paul Ivanov
John Hunter, on 2008-10-17 04:02, wrote:
> On Thu, Oct 16, 2008 at 9:18 PM, Paul Ivanov <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> I'm a big fan of keyboard shortcuts, so I decided to add these guys to
>> lib/matplotlib/backend_bases.py
>>
>> I'm not sure if this is too much, and maybe these should be configurable
>> down the line, but here's my first stab at it, what do you all think?
>>
>> in the same order as they appear in the toolbar:
>> 'h' or 'r' for Home/Reset
>> left arrow or 'z' or backspace for Back
>> right arrow and 'x' for Forward
>> 'p' for pan axes with right, zoom with left mode toggle
>> 'o' for z*o*om to rectangle mode toggle
>> 's' for save
>
>> 'z' and 'x' I borrowed from the Opera browser, very handy to for
>> righties who can have their left hand on the keyboard while using the mouse.
>
> Hi Paul,
>
> I'm amenable to additional keys, but check out
> http://matplotlib.sourceforge.net/users/navigation_toolbar.html which
> details which keys are already in play. Also, with your patch, please
> submit a patch against the navigation toolbar doc
> doc/users/navigation_toolbar.rst . Maybe a ReST table that details all
> of the key bindings?
>
> Thanks,
> JDH
Index: doc/users/navigation_toolbar.rst
===
--- doc/users/navigation_toolbar.rst (revision 6289)
+++ doc/users/navigation_toolbar.rst (working copy)
@@ -76,6 +76,30 @@
``svg`` and ``pdf``.
+Navigation Keyboard Shortcuts
+-
+
+== =
+CommandKeyboard Shortcut(s)
+== =
+Home/Reset **h** or **r** or **home**
+Back **c** or **left arrow** or **backspace**
+Forward**v** or **right arrow**
+Pan/Zoom **p**
+Zoom-to-rect **o**
+Save **s**
+Toggle fullscreen **f**
+-- -
+**Pan/Zoom mode only**
+- constrain pan/zoom to x axis hold **x**
+- constrain pan/zoom to y axis hold **y**
+- preserve aspect ratiohold **CONTROL**
+-- -
+**In axes only**
+- Toggle grid **g**
+- Toggle y axis scale (log/linear) **l**
+== =
+
If you are using :mod:`matplotlib.pyplot` the toolbar will be created
automatically for every figure. If you are writing your own user
interface code, you can add the toolbar as a widget. The exact syntax
Index: lib/matplotlib/backend_bases.py
===
--- lib/matplotlib/backend_bases.py (revision 6289)
+++ lib/matplotlib/backend_bases.py (working copy)
@@ -1513,6 +1513,23 @@
if event.key == 'f':
self.full_screen_toggle()
+
+# *h*ome or *r*eset mnemonic
+elif event.key == 'h' or event.key == 'r' or event.key == "home":
+self.canvas.toolbar.home()
+# c and v to enable left handed quick navigation
+elif event.key == 'left' or event.key == 'c' or event.key == 'backspace':
+self.canvas.toolbar.back()
+elif event.key == 'right' or event.key == 'v':
+self.canvas.toolbar.forward()
+# *p*an mnem
Re: [matplotlib-devel] [Matplotlib-users] create ListedColormap with different alpha values
Hey John and the rest of the MPL gang: I've made the changes you suggested, but the problem is looking to be deeper than it seemed. I'm also moving this conversation to matplotlib-devel, since that's probably the more appropriate place for it. This updated patch allows for the creation of colormaps with various alphas, but there is likely more work to be done so that mpl can consistently make use of it (because it seems like all built-in cmaps are RGB, not RGBA). In trying to come up with an example that exercises the new capabilities, I found out that methods like scatter and countourf modify the colormap you give them and reset all of the alpha values to 1. I think this is because inside collections, we pass self._alpha, which is the Artist._alpha, and 1.0 by default, when making calls such as: _colors.colorConverter.to_rgba_array(c, self._alpha) ...Thus resetting all of alpha values. I was able to get around this by allowing collections to take on an alpha value of None, and then passing alpha=None to scatter and countourf, for example. There are probably other places where such a change should be done, unless someone has a better idea for how do do this. I updated examples/pylab/plot_scatter.py to show off the new capability. Another thing that I was unable to get around is that if you now make a plot using the same colormap but omit the alpha=None parameter, or set it to something other than None, it will reset the alpha values on the previous plot: figure(2) c = scatter(theta, r, c=colors, s=area,cmap=myColormap,alpha=None) will do the right thing, but calling scatter without alpha=None figure(3) d = scatter(theta, r, c=colors, s=area,cmap=myColormap) or d = scatter(theta, r, c=colors, s=area,cmap=myColormap, alpha=.5) will reset all of the alpha values in myColormap to 1 or .5. You can do c.cmap._init() to reset its original alpha values, and if you force a redraw on figure(2) (by panning or zooming on it, for example), it will look right again. However, if you go and fiddle with figure(3) (pan/zoom), and come back to figure(2), panning or zooming will cause all of the alpha values will be reset again. I'm not sure if it would be worth it to make a copy of the colormap to prevent this from happening. Anyone have thoughts on this? (the full example of this is commented with FIXME: in polar_scatter.py) best, Paul Ivanov John Hunter, on 2008-11-23 07:36, wrote: > On Sun, Nov 23, 2008 at 2:01 AM, Paul Ivanov <[EMAIL PROTECTED]> wrote: >> I took a stab at it, how does this look? >> >> I also took the liberty of adding alpha to LinearSegmentedColormap and >> updated its docstring changing two somewhat ambiguous uses of the word >> 'entry' with 'key' and 'value'. > > Hey Paul, > > Thanks for taking this on. I haven't tested this but I read the patch > and have some inline comments below. Some additional comments: > > * the patch should include a section in the CHANGELOG and > API_CHANGES letting people know what is different. > > * you should run examples/tests/backend_driver.py and make sure all > the examples still run, checking the output of some of the mappable > types (images, scaltter, pcolor...) > > * it would be nice to have an example in the examples dir which > exercises the new capabilities. > > See also, in case you haven't, > http://matplotlib.sourceforge.net/devel/coding_guide.html, which > covers some of this in more detail. > > Thanks again! Comments below: > > Index: lib/matplotlib/colors.py > === > --- lib/matplotlib/colors.py (revision 6431) > +++ lib/matplotlib/colors.py (working copy) > @@ -452,7 +452,7 @@ > self._isinit = False > > > -def __call__(self, X, alpha=1.0, bytes=False): > +def __call__(self, X, alpha=None, bytes=False): > """ > *X* is either a scalar or an array (of any dimension). > If scalar, a tuple of rgba values is returned, otherwise > @@ -466,9 +466,10 @@ > """ > You need to document what alpha can be here: what does None mean, can > it be an array, scalar, etc... > > if not self._isinit: self._init() > -alpha = min(alpha, 1.0) # alpha must be between 0 and 1 > -alpha = max(alpha, 0.0) > -self._lut[:-3, -1] = alpha > +if alpha: > > I prefer to explicitly use "if alpha is None", since there are other > things that would test False (0, [], '') that you probably don't mean. > > +alpha = min(alpha, 1.0) # alpha must be between 0 and 1 > +
[matplotlib-devel] patch: bug with twinx and scientific style
I sent this to the -users list a little over a week ago - now
resending to -devel list against the latest svn.
best,
--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
Paul Ivanov, on 2010-12-23 09:47, wrote:
> Václav Šmilauer, on 2010-12-23 14:51, wrote:
> > Hi there,
> >
> > when I use twinx() to have y1 and y2 axes and set ticklabel_format
> > style to 'sci' on the y2 axis, ticks on the y2 are properly numbered,
> > but the "1e-5" that is supposed to be atop y2 appears on the top of
> > y1 instead. When both y1 and y2 use the exponents, they overwrite
> > each other -- a minimal example (result attached in pdf):
> >
> > import pylab
> >
> > pylab.plot([0,1e-2,2e-2,3e-2],[1e3,5e3,6.1e3,1e3],'g-')
> >
> > pylab.ticklabel_format(style='sci',scilimits=(0,0),axis='both') # this is
> > not necessary to show the bug
> >
> > pylab.twinx()
> >
> > pylab.plot([1e-2,2e-2,3e-2,4e-2],[2e-5,3e-5,0,-1e-5],'r-')
> >
> > pylab.ticklabel_format(style='sci',scilimits=(0,0),axis='both') # makes
> > 1e-5 appear on the left instead of on the right
> >
> > pylab.show()
> >
> Hi Václav,
>
> thanks for the bug report. As a temporary workaround - use
>
> plt.gca().yaxis.set_offset_position('right')
>
> Committers: the patch attached fixes this problem. I thought that
> there might be a similar problem for twiny() - but ax.xaxis does
> not appear to have .set_offset_position() method.
>
> > I've had this issue with versions .99, 1.0.0, running on Linux
> > (Ubuntu, versions 9.04 through to 10.10).
>
> me too, and I kept forgetting to report it.
>
> > PS. what's wrong with the sf.net bugzilla? I was not able to post the
> > issue there --
>
> this I do not know.
>
Index: CHANGELOG
===
--- CHANGELOG (revision 8871)
+++ CHANGELOG (working copy)
@@ -1,3 +1,5 @@
+2011-01-02 Fixed twinx scientific notation offset being misplaced.
+
2010-12-29 Implment axes_divider.HBox and VBox. -JJL
2010-11-22 Fixed error with Hammer projection. - BVR
Index: lib/matplotlib/axes.py
===
--- lib/matplotlib/axes.py (revision 8871)
+++ lib/matplotlib/axes.py (working copy)
@@ -7391,6 +7391,7 @@
frameon=False)
ax2.yaxis.tick_right()
ax2.yaxis.set_label_position('right')
+ax2.yaxis.set_offset_position('right')
self.yaxis.tick_left()
ax2.xaxis.set_visible(False)
return ax2
signature.asc
Description: Digital signature
--
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] A quesstion with matplotlib
余亮罡, on 2011-01-03 13:31, wrote:
> I just do not know how to change the font size,could you tell
> me that? Thank you !
Here's a small example. You can either keep around the ylabel
from when you first create it:
import matplotlib.pyplot as plt
lbl = plt.ylabel("foo")
lbl.set_size(25)
If you already have the labels on an axes:
ax = plt.gca()
lbl = ax.yaxis.get_label()
lbl.set_size('x-small')
Note that ax.get_ylabel() only gets you the string of the
label, which is why you have to use ax.yaxis.get_label() to get
an instance of the matplotlib.text.Text object in order to change
its size.
hope that helps,
--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
signature.asc
Description: Digital signature
--
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] two gridspec patches (fix getitem bug and docs)
Hi matplotlib developers,
I was answering a question on the -users list and came across a
gridspec __getitem__ bug which causes an infinite loop if the
user tries to iterate over it, because getitem never did a
sanity-check when given an integer key.
from matplotlib import gridspec
gs = gridspec.GridSpec(1,2)
gs[100] # no error is given, a SubplotSpec is returned
[x for x in gs] # causes infinite loop before applying patch
# after applying the patch - which is just lines 171-172 in the
# traceback below
In [9]: gs[100]
--
IndexError Traceback (most recent call last)
./matplotlib/ in ()
./matplotlib/gridspec.pyc
in __getitem__(self, key)
170key += total
171if key >= total or key < 0:
--> 172raise IndexError("index out of range")
173num1, num2 = key, None
174
IndexError: index out of range
In [10]: [x for x in gs]
Out[10]:
[,
]
I'm also including a patch for the gridspec docs which create a
grid-of-grids using gridspec in a colorful manner. Note that
there, I explicitly create indexes in the right range, like so:
outer_grid = GridSpec(4, 4)
for i in xrange(16):
inner_grid = GridSpecFromSubplotSpec(3, 3, subplot_spec=outer_grid[i])
for j in xrange(9):
ax = plt.Subplot(f, inner_grid[j])
...
because before applying the getitem patch described above, one
*can't* currently iterate over the spec itself like this:
outer_grid = GridSpec(4, 4)
for cell in outer_grid:
inner_grid = GridSpecFromSubplotSpec(3, 3, subplot_spec=cell)
for subcell in inner_grid:
ax = plt.Subplot(f, subcell)
...
The doc patch also fixes the currently broken .. _gridspec-guide:
anchor name which can be seen peeking out at the top of:
http://matplotlib.sourceforge.net/users/gridspec.html
because there was previously a misplaced leading \ on line 1 of
doc/users/gridspec.rst
best,
--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
Index: doc/users/plotting/examples/demo_gridspec06.py
===
--- doc/users/plotting/examples/demo_gridspec06.py (revision 0)
+++ doc/users/plotting/examples/demo_gridspec06.py (revision 0)
@@ -0,0 +1,41 @@
+import matplotlib.pyplot as plt
+import matplotlib.gridspec as gridspec
+import numpy as np
+from itertools import product
+
+def squiggle_xy(a, b, c, d, i=np.arange(0.0, 2*np.pi, 0.05)):
+return np.sin(i*a)*np.cos(i*b), np.sin(i*c)*np.cos(i*d)
+
+f = plt.figure(figsize=(8, 8))
+
+# gridspec inside gridspec
+outer_grid = gridspec.GridSpec(4, 4, wspace=0.0, hspace=0.0)
+
+for i in xrange(16):
+inner_grid = gridspec.GridSpecFromSubplotSpec(3, 3,
+subplot_spec=outer_grid[i], wspace=0.0, hspace=0.0)
+a, b = int(i/4)+1,i%4+1
+for j, (c, d) in enumerate(product(range(1, 4), repeat=2)):
+ax = plt.Subplot(f, inner_grid[j])
+ax.plot(*squiggle_xy(a, b, c, d))
+ax.set_xticks([])
+ax.set_yticks([])
+f.add_subplot(ax)
+
+all_axes = f.get_axes()
+
+#show only the outside spines
+for ax in all_axes:
+for sp in ax.spines.values():
+sp.set_visible(False)
+if ax.is_first_row():
+ax.spines['top'].set_visible(True)
+if ax.is_last_row():
+ax.spines['bottom'].set_visible(True)
+if ax.is_first_col():
+ax.spines['left'].set_visible(True)
+if ax.is_last_col():
+ax.spines['right'].set_visible(True)
+
+plt.show()
+
Index: doc/users/gridspec.rst
===
--- doc/users/gridspec.rst (revision 8885)
+++ doc/users/gridspec.rst (working copy)
@@ -1,4 +1,4 @@
-\.. _gridspec-guide:
+.. _gridspec-guide:
@@ -129,6 +129,16 @@
.. plot:: users/plotting/examples/demo_gridspec04.py
+A Complex Nested GridSpec using SubplotSpec
+===
+
+Here's a more sophisticated example of nested gridspec where we put
+a box around each cell of the outer 4x4 grid, by hiding appropriate
+spines in each of the inner 3x3 grids. ::
+
+.. plot:: users/plotting/examples/demo_gridspec06.py
+
+
GridSpec with Varying Cell Sizes
Index: lib/matplotlib/gridspec.py
===
--- lib/matplotlib/gridspec.py (revision 8885)
+++ lib/matplotlib/gridspec.py (working copy)
@@ -167,6 +167,8 @@
else:
if key < 0:
key += total
+if key >= total or key < 0:
+raise IndexError("index out of range"
Re: [matplotlib-devel] two gridspec patches (fix getitem bug and docs)
Benjamin Root, on 2011-01-04 19:48, wrote:
> 2011/1/4 Paul Ivanov
>
> > Hi matplotlib developers,
> >
> > I was answering a question on the -users list and came across a
> > gridspec __getitem__ bug which causes an infinite loop if the
> > user tries to iterate over it, because getitem never did a
> > sanity-check when given an integer key.
> >
> > from matplotlib import gridspec
> > gs = gridspec.GridSpec(1,2)
> > gs[100] # no error is given, a SubplotSpec is returned
> > [x for x in gs] # causes infinite loop before applying patch
> Does this patch prevent the use of negative indexes? If so, then we might
> want to rethink that in order to be more consistent with numpy arrays and
> python lists...
No, it does not prevent the use of negative indexes, and ensures
that the negative index is within the allowed bounds, so we do
the right thing. Here's the full patch for context:
lib/matplotlib/gridspec.py
169 else:
170 if key < 0:
171 key += total
172+if key >= total or key < 0:
173+raise IndexError("index out of range")
174 num1, num2 = key, None
As you can see, the reason line 172 has the key < 0 check is
because the allowed range of negative indexes gets dealt with on
the two preceding lines. So for gs=gridspec.GridSpec(1,2);
Both gs[-1] and gs[-2] are legal, but gs[-3] will raise an
IndexError.
--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
signature.asc
Description: Digital signature
--
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] documentation oddities
Benjamin Root, on 2011-01-11 14:55, wrote: > I am on the online version of the matplotlib documentation, and I am finding > some artifacts of the Sphinx build. > > For example there is ".. _gridspec-guide:" at the top of the page on > http://matplotlib.sourceforge.net/users/gridspec.html Hi Ben, I sent a fix for the gridspec-guide anchor in a patch that included a new gridspec example before I got commit rights, but Jae-Joon wanted to examine it further before committing. I just checked in the trivial fix for this in r8903. > There is also a " `AxesGrid`_" in the last paragraph of this section: > http://matplotlib.sourceforge.net/mpl_toolkits/axes_grid/users/overview.html#what-is-axesgrid-toolkit using svn log doc/mpl_toolkits/axes_grid/users/overview.rst to track down when this file changed, I saw that r8010 svn diff -r 8010 doc/mpl_toolkits/axes_grid/users/overview.rst made a few changes of the instance AxesGrid to ImageGrid, including a section title that went from being "Axes Grid" to "Image Grid", so that's probably how the broken link happened. I took care of it in r8094 just now. Also, to preempt potential race condition on improving the docs - I have a substantial fix-up of a bunch of typos in the docstrings of mpl_toolkits/axes_grid1/ files that I'll check in later on tonight or tomorrow. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] backporting typo fixes?
Hi everyone, I just committed a big typos fix to trunk (r8925), should changes like this be backported to the maintenance branch? best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] A new KNOWNFAIL, pcolormesh.png ?
Sandro Tosi, on 2011-01-18 19:29, wrote: > Hi, > > On Tue, Jan 18, 2011 at 15:00, Michael Droettboom wrote: > > I'm not sure PIL enters into it -- there shouldn't be any code path > > involving PIL in that case. > > > > I think this a case where the image comparison tolerance needs to be > > increased. You would do this be passing a "tol" parameter to the > > image_comparison decorator on the pcolormesh test. The default is 1e-3, > > but it should be conservatively increased until the test passes. You > > can perform this experiment yourself, or attach the result image for the > > test to this list and I can experiment to find a correct value. > > I'm attaching the images, just for reference; as you can see, the > difference is very tiny and with a tolerance of 0.02 I was able to > pass the test (RMS Value: 0.0116511801977). I just wanted to chime in that there *is* structure in the differences between the images - which don't show up on screens which don't have linearized gamma (the difference between 0 and 1 are much smaller in brightness than the difference between 127 and 128, for example). A quick way to get around this is to just invert the colors. in X11, I do this with 'xcalib -a -i' which toggles back to normal if you run the command twice (Compiz also has it's own version of this via some keyboard shortcut, IIRC, but I don't use it). ImageMagick's convert can do this with the -negate flag. On OS X, there's something like command-F8 to do this. For completeness, if you're interested in doing this in matplotlib, ;) just subtract your (floating point 0.0-1.0) color from (1.,1.,1.) to get the new color. I'm attaching the difference image, with its colors inverted. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 <> signature.asc Description: Digital signature -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Automatic subplot_params for fitting label text (was Re: [Matplotlib-users] Suggestions for auto scaling fonts ,
etc for producing images at various scales)
Reply-To:
In-Reply-To: <20110121232036.GA26739@ykcyc>
X-PGP-Key: http://pirsquared.org/PaulIvanov0F3E28F7.asc
Paul Ivanov, on 2011-01-21 15:20, wrote:
> I'm almost certain that one *can* write a function to do this
> pro grammatically (without having to hand tweak anything), by
> looking at say, the .get_window_extent() but I haven't found the
> time to scratch that itch, yet.
>
> If someone wants to beat me to it, here's the sort of thing that
> you can do:
>
> def show_labels_by_shrinking(ax):
> " adjust subplot parameters to fit the yaxis label"
> f = ax.figure
> textwidth = ax.yaxis.get_label().get_window_extent().width
> labelwidth = max([lab.get_window_extent().width for lab in
> ax.get_yticklabels()])
>
> plt.subplots_adjust(left=(textwidth+labelwidth+3*ax.yaxis.labelpad)/f.get_window_extent().width)
> # the 3 *ax.yaxis.labelpad is just a fudge factor for now, need
> # to look into the sourcecode to figure out what the
> # appropriate placement is normally, to know how to adjust
> # properly
>
>
> ax.set_ylabel('foo')
> show_labels_by_shrinking(ax)
> ax.set_ylabel("a\nmulti\nline\nexample")
> show_labels_by_shrinking(ax)
I should add that along with doing a similar thing for the xaxis,
this would need to be extended for the multiple subplot case, to
also adjust the wspace and hspace parameters accordingly.
this is important functionality currently missing from matplotlib
out-of-the-box at the moment, so I'll try my crack at it this out
this weekend.
CCing the devel list in case someone has more opinions.
best,
--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
signature.asc
Description: Digital signature
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] sourceforge 'latest' still points to 1.0.0
I'm guessing only the admins can change this (or at least I didn't find a way to do it myself on the sourceforge site) but the link at the top of the download page still points to 1.0.0 "Loking for the latest version? Download matplotlib-1.0.0.tar.gz" This actually affects all of the direct download links that are scattered about (the one on the project summary page, for example) Can someone with the privileges points it to 1.0.1? best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Possibility for internationalized sphinx docs?
> On Tue, Feb 22, 2011 at 2:45 PM, Benjamin Root wrote: > > Hello all, > > > > Given some recent -- ahem -- difficulties with matplotlib users where > > English is not their native language, it has dawned on me that maybe we > > ought to consider making available translated versions of our > > documentation. I have absolutely no experience with such efforts, but I did > > see that Sphinx does support internationalization: > > > > http://sphinx.pocoo.org/latest/intl.html Hi Ben, a soft on this -1 from me. At this time, I feel that matplotlib has neither the user base need, nor the developer / i18n expert bandwidth to make this happen. As a point of reference, even the Python docs aren't internationalized, at the moment. > > > > and I do believe we have some bilingual developers on this list (or at least > > are active on the users list). While I don't think it would be possible to > > translate the API docs effectively, at the very least we should be able to > > provide translations of other parts. which parts? Tutorials? It seems like these sorts of things self-organize around individuals who write about the software in their language of choice. Folks searching the web for something like "python publication quality graphics" in Esperanto or Klingon will find one another, if there are enough of them, and if there aren't enough of them, we'd have a very hard time helping them. > > > > What does everyone think? Could someone who has done internationalization > > (particularly using sphinx) comment? What languages would we like the docs > > to be in? I think the fact that there isn't a language that automatically pops into our heads suggests to me that we could expand a lot of effort to do this without users that actually need it. Darren Dale, on 2011-02-22 14:52, wrote: > If anyone is looking for me, I'll be cowering under my desk. English being lingua franca ;) is fairly typical in the software world, but that doesn't mean we should feel free to sprinkle idioms and confusing cultural references everywhere. I'm guilty of both of these, as I sometimes try to add "color" to my comments, which might produce a chuckle for the folks who understood, but be a source of unneeded confusion for others. So may I propose an alternative, which I've seen in somewhere else, but completely blanking on where: add to our FAQ (or some similar place) comment requesting feedback along these lines: All of the documentation is in English: is there a translation of matplotlib documentation? We strive to make matplotlib accessible to everyone, but lack the resource to translate and maintain the documentation in several languages. Please help us identify and reword confusing portions of the documentation (in particular, idiomatic or otherwise untranslatable usage of English in docstrings is considered a bug which you should report). best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] What's the status of the py3k branch?
Fernando Garcia Bermudez, on 2011-02-03 09:14, wrote: > On Thu, Feb 3, 2011 at 06:05, Michael Droettboom wrote: > > On 02/03/2011 07:48 AM, Darren Dale wrote: > >> On Thu, Feb 3, 2011 at 12:12 AM, Fernando Garcia Bermudez > >> wrote: > >> > >>> Before continuing the debug process, though, I wanted to check with > >>> someone knowledgeable of this branch regarding its current status. Is > >>> it possible to compile matplotlib on python3? > >>> > >> Mike D. did some initial work for py3 support a while back. I don't > >> know what platform he was working on, but he was able to produce a > >> simple plot, maybe running the simple_plot demo. > >> > > I was working on Linux (RHEL5), and never got past that platform. > > I'll stay on the lookout for the github py3k branch and will do as > suggested. Thanks for the update. > By the way, there was a recent poll on python.org for packages where users desire Python 3 support. Here are the top 10: Votes | Package --+ 837 | Django 454 | wxPython 406 | scipy 364 | matplotlib 327 | PIL 266 | py2exe 185 | Twisted 179 | PyGTK 135 | Pygame 94 | web2py http://python.org/3kpoll best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] What's the status of the py3k branch?
Benjamin Root, on 2011-02-25 18:03, wrote: > On Fri, Feb 25, 2011 at 5:11 PM, Paul Ivanov wrote: > > By the way, there was a recent poll on python.org for packages > > where users desire Python 3 support. > > > > Here are the top 10: > > > > Votes | Package > > --+ > > 837 | Django > > 454 | wxPython > > 406 | scipy > > 364 | matplotlib > > 327 | PIL > > 266 | py2exe > > 185 | Twisted > > 179 | PyGTK > > 135 | Pygame > > 94 | web2py > > > > http://python.org/3kpoll > > Which just goes to show that some people don't understand dependencies... > (PIL and PyGTK are needed by matplotllib to be fully py3k compatible). > Hopefully this will light a fire for them as well. Well, this was a user poll - users shouldn't have to know or express all of the dependencies for a given package that they use - that's for us package developers to figure out. To quote from the poll conclusions: What does this poll mean? Off-hand, nothing: nominating a package will not mean that its authors now start porting it to Python 3. However, we still hope that this still has some effect on the Python community: * Volunteers trying to help now see where help is most wanted * Package authors now see that there really is (or is not) demand for getting their package ported. It's that last point that I was trying to highlight for us, as matplotlib was the fourth most nominated package for py3k support. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] behaviour of clf()
Hey everyone, Michael D and I are working on reducing the memory footprint of our test suite here at Sage days (we've made very good progress!), and came across a behavior of plt.clf() that we wanted feedback on. At the moment, plt.clf (i.e. fig.clf) do not clear all of the state variable associated with a figure. I think the most consistent thing to do is to have a clf() change the figure to be the same as a freshly created plt.figure(), but this is not the case. For example: In [5]: f = plt.figure() In [6]: f.subplotpars.left Out[6]: 0.055 In [7]: f.subplotpars.left = .20 In [8]: f.clf() In [9]: f.subplotpars.left Out[9]: 0.20001 I propose making clf revert all variables back to their rcParams defaults (i.e. make it so that Out[9]: 0.055), and possibly creating a new rcParam to allow individuals to preserve the old behavior (in case people have code which relies on it, and prefer it to stay the same). Additionally, we could have an optional bolean parameter to clf, called 'scrub' or 'fresh' or something like that, which would implement the rcParam specified behavior by default, but allow users to scrub or not scrub on a call by call basis. Does anyone have any thoughts about this? -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] I screwed up matplotlib/master on github
I offer my sincerest apologies, I royally screwed up and thought that I was pushing out to one of my own branches and somehow ended up pushing a 2 day old copy of master out to matplotlib/master with 'git push -f'. Assuming Mike's work from today is also in his own master branch, I think the damage can be undone by just pulling from https://github.com/mdboom/matplotlib/master and pushing that to https://matplotlib/matplotlib/master, but at this point I don't trust myself and just want to not cause any more damage than I've already done. I realize that people get their commit right revoked for such careless shenanigans, but I will be grateful if you'd all allow me the opportunity always run any push commands with the --dry-run flag from now on. very sorry, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] I screwed up matplotlib/master on github
Paul Ivanov, on 2011-03-24 01:30, wrote: > I offer my sincerest apologies, I royally screwed up and thought > that I was pushing out to one of my own branches and somehow > ended up pushing a 2 day old copy of master out to > matplotlib/master with 'git push -f'. Assuming Mike's work from > today is also in his own master branch, I think the damage can be > undone by just pulling from > https://github.com/mdboom/matplotlib/master and pushing that to > https://matplotlib/matplotlib/master, but at this point I don't > trust myself and just want to not cause any more damage than I've > already done. > > I realize that people get their commit right revoked for such > careless shenanigans, but I will be grateful if you'd all allow > me the opportunity always run any push commands with the > --dry-run flag from now on. I can't figure out a way to pull it from there, but I think Eric was the last to commit to trunk before I (destructively) pushed my stale copy. Eric's last commit hash was: 8506c33c811e970c6aa73a446d3ed223ac48f989 At least that's what I see on https://github.com/organizations/matplotlib hopefully this will help someone who get git better than I do. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] I screwed up matplotlib/master on github
Matthew Brett, on 2011-03-24 16:37, wrote: > Welcome to the wonderful world of git and DVCS! Thanks, I wish I could claim that I only started using git recently, but I've just sort of been uncomfortably trying my best to not cause too much trouble for the past year and a half... > > I think you could have solved this one by: > > git reset --hard 8506c33c811e970c6aa73a446d3ed223ac48f989 > > and pushing that. Assuming you had that commit, which I guess you would have. This actually wasn't the case - I hadn't pulled from matplotlib/master for a few days, hence the stale commit become a head after my push. > The way I try and avoid doing that very easy thing is > > 1) Having a moderately frightening name for the upstream remote like > 'upstream-rw'. > 2) Having a moderately frightening name for the tracking branch like: > > git co -b main-master --track upstream-rw/master good tips, thanks. > > 3) Making sure I've got the git-completion bash command line > completion tools working, so I can always see my branch name This was actually the case for me - I wasn't working on master, but a seperate branch called 'one-figure' which didn't have a remote branch affiliated with it (or a wrong one). I had previously pushed it using 'git push ivanov one-figure', and *wrongly* assumed that this state was preserved somewhere 16:46@matplotlib(one-figure)$ > 4) Never working on main-master, always branching, and merging when I'm sure. > 5) Deleting my own master branch to avoid confusion. This involves: > > Going to your github fork, choosing Admin, set default branch to be > something other than 'master' > > git co that-other-branch > git branch -D master # delete locally > git push origin :master # delete on github > > Every error, is a jewel. Wise words, but if that were true, De Beers and Tiffany's couldn't hope to compete with me. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Bug: plot numpy.nans vs. datetime objects
Gerrit Kuhlmann, on 2011-03-25 14:26, wrote: > Hi all, > > I get a ValueError, if I try to plot a list of numpy.nans against > datetime objects. I'm using Python 2.6.5 and Matplotlib 1.0.1 on Ubuntu > Linux 10.04. Code and traceback are below. > > Best regards, > Gerrit > > > > Code > """" > import matplotlib.pyplot as plt > import numpy as np > from datetime import datetime as DateTime > > t = [DateTime(2011,1,day) for day in xrange(1,20)] > x = [np.nan for i in xrange(1,20)] > > plt.plot(t,x) > plt.show() Hi Gerrit, Thanks for the report, though I'm not sure what you expect to happen here? Changing at least one of the elements of x to be something other than nan does not cause the error. There is an inconsistency, though, in that plt.plot(x,x) when x is full of nans does not cause any errors. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] [Matplotlib-users] matplotlib.test() no errors, but $nosetest matplotlib.tests -> errors and failure?
Blast from the past! I just ran into this and it comes from the fact that 'matplotlib.tests.test_text' is not in the default_test_modules variable inside matplotlib's __init__.py Here's the necessary diff: index 82633a5..649e4d8 100644 --- a/lib/matplotlib/__init__.py +++ b/lib/matplotlib/__init__.py @@ -968,7 +968,8 @@ default_test_modules =3D [ 'matplotlib.tests.test_spines', 'matplotlib.tests.test_image', 'matplotlib.tests.test_simplification', -'matplotlib.tests.test_mathtext' +'matplotlib.tests.test_mathtext', +'matplotlib.tests.test_text' ] I added a pull request for this two line change just in case there was a specific reason to *exclude* test_text from the test modules?=20 For instance, right now, I get one failure in the test suite if I include it. The failure is in test_text:test_font_styles, but this has been the case for a while, it's just that these tests weren't running before. Any developers want to chime in on this? best, -- Paul Ivanov http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 Michael Droettboom, on 2010-07-27 11:19, wrote: > Hmm... surprisingly, I am actually able to reproduce this sort of=20 > behaviour here. I'll look into it further. >=20 > Mike >=20 > On 07/27/2010 09:49 AM, Michael Droettboom wrote: > > Of course, we'll prefer to see all of the tests pass... > > > > I'm surprised the two modes of running the tests gives different > > results. Are you sure they are running the same python? Does > > > > python `which nosetests` matplotlib.tests > > > > give you the same result as > > > > nosetests matplotlib.tests > > > > ? > > > > There must be some environmental difference between the two to cause the > > different results. > > > > Mike > > > > On 07/24/2010 05:09 PM, Adam wrote: > > =20 > >> Hello, I have just updated to v1.0.0 and am trying to run the test > >> suite to make sure everything is ok. There seems to be two different > >> suites and I am not sure which is correct/current: > >> > >> $python -c 'import matplotlib; matplotlib.test()' > >> [...snipped output...] > >> Ran 138 tests in 390.991s > >> OK (KNOWNFAIL=3D2) > >> > >> $nosetests matplotlib.tests I get: > >> [...snipped output] > >> Ran 144 tests in 380.165s > >> FAILED (errors=3D4, failures=3D1) > >> > >> Two of these errors are the known failures from above, and the other > >> two are in "matplotlib.tests.test_text.test_font_styles": > >> ImageComparisonFailure: images not close: > >> /home/adam/result_images/test_text/font_styles.png vs. > >> /home/adam/result_images/test_text/expected-font_styles.png (RMS > >> 23.833) > >> ImageComparisonFailure: images not close: > >> /home/adam/result_images/test_text/font_styles_svg.png vs. > >> /home/adam/result_images/test_text/expected-font_styles_svg.png (RMS > >> 12.961) > >> > >> The module that fails is: > >> > >> FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip > >> -- > >> Traceback (most recent call last): > >>File "/usr/local/lib/python2.6/dist-packages/nose-0.11.4-py2.6.egg/= nose/case.py", > >> line 186, in runTest > >> self.test(*self.arg) > >>File "/usr/local/lib/python2.6/dist-packages/matplotlib/tests/test_= mlab.py", > >> line 24, in test_recarray_csv_roundtrip > >> assert np.allclose( expected['x'], actual['x'] ) > >> AssertionError > >> > >> > >> > >> I am not sure of the importance level of these - but I wanted to ask > >> to see if I should do anything or if they can safely be ignored. > >> > >> Thanks, > >> Adam. signature.asc Description: Digital signature -- Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] [Matplotlib-users] matplotlib.test() no errors, but $nosetest matplotlib.tests -> errors and failure?
Blast from the past! I just ran into this and it comes from the fact that 'matplotlib.tests.test_text' is not in the default_test_modules variable inside matplotlib's __init__.py Here's the necessary diff: index 82633a5..649e4d8 100644 --- a/lib/matplotlib/__init__.py +++ b/lib/matplotlib/__init__.py @@ -968,7 +968,8 @@ default_test_modules = [ 'matplotlib.tests.test_spines', 'matplotlib.tests.test_image', 'matplotlib.tests.test_simplification', -'matplotlib.tests.test_mathtext' +'matplotlib.tests.test_mathtext', +'matplotlib.tests.test_text' ] I added a pull request for this two line change just in case there was a specific reason to *exclude* test_text from the test modules? For instance, right now, I get one failure in the test suite if I include it. The failure is in test_text:test_font_styles, but this has been the case for a while, it's just that these tests weren't running before. Any developers want to chime in on this? best, -- Paul Ivanov http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 Michael Droettboom, on 2010-07-27 11:19, wrote: > Hmm... surprisingly, I am actually able to reproduce this sort of > behaviour here. I'll look into it further. > > Mike > > On 07/27/2010 09:49 AM, Michael Droettboom wrote: > > Of course, we'll prefer to see all of the tests pass... > > > > I'm surprised the two modes of running the tests gives different > > results. Are you sure they are running the same python? Does > > > > python `which nosetests` matplotlib.tests > > > > give you the same result as > > > > nosetests matplotlib.tests > > > > ? > > > > There must be some environmental difference between the two to cause the > > different results. > > > > Mike > > > > On 07/24/2010 05:09 PM, Adam wrote: > > > >> Hello, I have just updated to v1.0.0 and am trying to run the test > >> suite to make sure everything is ok. There seems to be two different > >> suites and I am not sure which is correct/current: > >> > >> $python -c 'import matplotlib; matplotlib.test()' > >> [...snipped output...] > >> Ran 138 tests in 390.991s > >> OK (KNOWNFAIL=2) > >> > >> $nosetests matplotlib.tests I get: > >> [...snipped output] > >> Ran 144 tests in 380.165s > >> FAILED (errors=4, failures=1) > >> > >> Two of these errors are the known failures from above, and the other > >> two are in "matplotlib.tests.test_text.test_font_styles": > >> ImageComparisonFailure: images not close: > >> /home/adam/result_images/test_text/font_styles.png vs. > >> /home/adam/result_images/test_text/expected-font_styles.png (RMS > >> 23.833) > >> ImageComparisonFailure: images not close: > >> /home/adam/result_images/test_text/font_styles_svg.png vs. > >> /home/adam/result_images/test_text/expected-font_styles_svg.png (RMS > >> 12.961) > >> > >> The module that fails is: > >> > >> FAIL: matplotlib.tests.test_mlab.test_recarray_csv_roundtrip > >> -- > >> Traceback (most recent call last): > >>File > >> "/usr/local/lib/python2.6/dist-packages/nose-0.11.4-py2.6.egg/nose/case.py", > >> line 186, in runTest > >> self.test(*self.arg) > >>File > >> "/usr/local/lib/python2.6/dist-packages/matplotlib/tests/test_mlab.py", > >> line 24, in test_recarray_csv_roundtrip > >> assert np.allclose( expected['x'], actual['x'] ) > >> AssertionError > >> > >> > >> > >> I am not sure of the importance level of these - but I wanted to ask > >> to see if I should do anything or if they can safely be ignored. > >> > >> Thanks, > >> Adam. signature.asc Description: Digital signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] mpl on OS X with Python 3.1 (was Re: Help)
Georges Arsouze, on 2011-03-16 09:48, wrote: > Hello > I'am working with Python3.1 under Mac Os Snow Leopard > I download matplotlib with > http://www.cgl.ucsf.edu/Outreach/pc204/matplotlib.html > > It doesn't work > Can you help me ? Hi Georges, What version of matplotlib are you trying to run? At the moment, there isn't a "stable" release which is compatible with Python 3, and you have to grab it from: https://github.com/matplotlib/matplotlib-py3 Not all of the backends work in -py3, mostly because the underlying toolkits have not been ported to Python 3. You can notes about the work in progress, what's been completed, and what's left to do here: https://github.com/matplotlib/matplotlib-py3/wiki (Also, this is more of a matplotlib-users question, so I'm replying to that list) best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Orphaned RST pages
Michael Droettboom, on 2011-03-31 12:04, wrote: > On 03/31/2011 11:46 AM, Benjamin Root wrote: > > Maybe we need an entry for mpl_toolkit items? > Yes. I think we should add a toolkit category to the table of > contents and add this and AxesGrid there. +1 I guess I always find the docs for those using the search, but it'd be better to have them at least somewhat integrated with the rest of the docs. Plus it will bring the zeroth Betti number down for the docs, and I'd consider it a bug if that number is anything other than 1. (Can you tell I've been reading a pop-math book lately? _Poincaré's prize_ is actually quite accessbile) -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Last object added to the plot
[email protected], on 2011-04-04 05:15, wrote: > Hi, > > Does matplotlib keep track of the last object added to the plot axes > or its nature (line, text, collection, patch, etc.) ? > If not, would it be feasible to implement something like this in > matplotlib ? > > This could be useful for interactive plotting, as it would allow a > simple undo feature based on commands such as del ax.lines[-1]. Hi there, I think this functionality already exists exactly as you describe. ax.plot appends new lines to ax.lines, ax.scatter appends new collection to ax.collections (via the ax.add_collection method). try this, and you'll see the cyan line is removed: plt.plot([1,2,3],'r') plt.plot([1,2,1],'c') ax = plt.gca() del(ax.lines[-1]) plt.draw() -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] New issue tracker on GitHub
Darren Dale, on 2011-04-11 13:24, wrote: > On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom wrote: > > I couldn't find the old thread about Sourceforge bug tracker vs. the > > Github issue tracker, but maybe we should reevaluate based on the new > > Github issue tracker announced on Saturday: > > > > https://github.com/blog/831-issues-2-0-the-next-generation > > > > The integration with git commits (closing issues by mentioning them in > > the commit message) is particularly compelling. > > The new issue tracker is a really big improvement over the old github > tracker, and I prefer it to the one at sourceforge since it integrates > so nicely with github version control. The github tracker is still > missing some features that we may want to consider: prioritize issues, > add attachments, and perhaps report issues without opening a github > account. I'm fine either way - though moving to GitHub certainly makes sense as it has momentum - whereas SF.net has been stagnating and not getting any faster for quite some time now. My only concern / request is that we transfer and/or clean up (wholesale) the sf.net bug tracker before we move to GH. It'd be a disservice to our users if we just ignored or mass-closed those issues in the transition to GH. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] mpl@wired
Fernando Perez, on 2011-04-13 17:59, wrote: > http://www.wired.com/wiredscience/2011/04/crashing-into-wall/ > > need to teach him about annotations, though, because the acceleration > plot looks annotated by hand after the fact (from the fonts, I'm > guessing on a Mac, maybe with Keynote). Maybe citations, too? I'm guessing you inferred he used mpl from the plots and the python tag on the post - but what are mere mortals supposed to do? :) best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Bleeding edge repository location
Fernando Perez, on 2011-04-14 11:08, wrote: > On Thu, Apr 14, 2011 at 7:53 AM, John Hunter wrote: > > Any idea when this will be back up -- building the docs on my solaris > > box here at work is proving more difficult than expected (segfaults > > due to a bug in numpy's complex dtype handling, reported months ago > > but still unfixed) > > Give me an hour or so, I'll ping you back... > > f > John, Fernando, and others: I'm happy to make my work machine available for building the docs, or general development, testing, etc - it's has 64 bit Ubuntu 8.04 (python 2.5.2) on it at the moment. I can provide access to anyone who gives me their public ssh key. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Proposal for Broken Axes
ayuffa, on 2011-07-07 13:54, wrote: > Have your changes to axes.py, namely breakx and breaky, been accepted? If > not, could you post your axes.py file. Here's an example, I'm looking into why it's not making it to the official docs right now, but you should be able to run it locally: https://github.com/matplotlib/matplotlib/blob/master/examples/pylab_examples/broken_axis.py best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Plan for cutting v1.1.0?
Eric Firing, on 2011-07-13 09:54, wrote: > ipython has moved to github for their homepage and documentation, but as > far as I can see, github has no facility for hosting downloads; the > ipython tarballs are on scipy.org. They are on scipy, github, and PyPI. Here are the ones for matplotlib: https://github.com/matplotlib/matplotlib/downloads > Question: simply abandon v1.0.x-maint without a release? this makes sense to me. let's just make sure there's nothing there that never made it into trunk, but should have. best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 signature.asc Description: Digital signature -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] which to fork from?
On Tue, Oct 25, 2011 at 3:52 PM, Daniel Hyams wrote: > For small bugfixes, am I supposed to fork from v1.1.x, or master? I say 'master' (Mike's been pushing some things to v1.1.x, but as he said in a comment to #551, "Pushed to v1.1.x since this is pretty serious yet simple-to-fix bug -- it should be on the maintenance branch.") best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] tagging releases (v1.1.0 tag missing)
Hey gang, as per this discussion: On Thu, Nov 3, 2011 at 3:40 AM, John Hunter wrote: > On Nov 2, 2011, at 10:47 PM, Benjamin Root wrote: > > So the instruction should be to remind John Hunter to update the entry in > PyPi? Got it. > > > Even better, it should be: > 1) update the release notes in the devel docs > 2) give Ben access to the pypi acct. I added a note to the release docs about tagging the releases - right now, there's no clear way inside git to know what ended up in v1.1.0 final, without grabbing a tarball and poking around. I'm inlining the relevant part of that commit here, so that John/Ben can tag the release after the fact. --- For each release candidate as well as for the final release version, please `git tag` the commit you will use for packaging like so:: git tag -a v1.1.0rc1 The `-a` flag will allow you to write a message about the tag, and affiliate your name with it. A reasonable tag message would be something like ``v1.1.0 Release Candidate 1 (September 24, 2011)``. To tag a release after the fact, just track down the commit hash, and:: git tag -a v1.0.1 a9f3f3a50745 Tags allow developers to quickly checkout different releases by name, and also provides source download via zip and tarball on github. --- best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] tagging releases (v1.1.0 tag missing)
Just wanted to re-ping the list, but include John and Ben directly: can we get the appropriate commit tagged as v1.1.0 in the git repo? On Thu, Nov 3, 2011 at 2:21 PM, Paul Ivanov wrote: > I added a note to the release docs about tagging the releases - right > now, there's no clear way inside git to know what ended up in v1.1.0 > final, without grabbing a tarball and poking around. I'm inlining the > relevant part of that commit here, so that John/Ben can tag the > release after the fact. > > --- > For each release candidate as well as for the final release version, > please `git tag` the commit you will use for packaging like so:: > > git tag -a v1.1.0rc1 > > The `-a` flag will allow you to write a message about the tag, and > affiliate your name with it. A reasonable tag message would be something > like ``v1.1.0 Release Candidate 1 (September 24, 2011)``. To tag a > release after the fact, just track down the commit hash, and:: > > git tag -a v1.0.1 a9f3f3a50745 > > Tags allow developers to quickly checkout different releases by name, > and also provides source download via zip and tarball on github. > --- best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] tagging releases (v1.1.0 tag missing)
On Fri, Nov 11, 2011 at 5:40 PM, Benjamin Root wrote: > On Fri, Nov 11, 2011 at 7:19 PM, Benjamin Root wrote: >> >> On Thu, Nov 10, 2011 at 5:52 PM, Paul Ivanov wrote: >>> >>> Just wanted to re-ping the list, but include John and Ben directly: >>> >>> can we get the appropriate commit tagged as v1.1.0 in the git repo? >>> >> >> Sure thing. I will add that tag. >> >> Ben Root >> > > The best I can figure is that commit > 0fc9830fe946f6221e9ceff2910cd0c2118b0965 was the last one before the release > announcement by John on Oct. 11. There was subsequently a commit on that > day to fix ipython links. I can't remember if that happened before or after > (I think after). > > Can anybody concur? On my PR to fix those links, John closed it and said he'd add it to the release branch, and they're up on the site, so I'd say that commit made it in. But I don't know if there were others afterward that made it in -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] documentation error at http://matplotlib.sourceforge.net/examples/api/fahrenheit_celcius_scales.html
[email protected], on 2012-01-09 11:47, wrote: > "Celsius" is spelled wrongly every time. Thanks for the report, Keith, I'm taking care of this right now. -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] documentation error at http://matplotlib.sourceforge.net/examples/api/fahrenheit_celcius_scales.html
Paul Ivanov, on 2012-01-09 13:56, wrote: > [email protected], on 2012-01-09 11:47, wrote: > > "Celsius" is spelled wrongly every time. > > Thanks for the report, Keith, I'm taking care of this right now. Done. https://github.com/matplotlib/matplotlib/commit/e0cf45ed01a9a098a9acbde177812dd9ceee7ec9 -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] should the ordering of clf() matter for AxesGrid?
Hi Mike, Mike Kaufman, on 2012-01-11 19:30, wrote: > Given the code snippet below with clf() #1 uncommented works like one > would expect - both plots are drawn. If #1 is commented out and #2 is > uncommented, then the figure is cleared and neither plot is drawn. Is > this the correct behavior? It seems like a bug to me. Seems to me like this is the intended behavior and not a bug. I'm not sure what you were expecting to happen with that second call to clf. You're clearing the whole figure, so even though the axes you have in the grid variable have references to f, f has disowned them! In [39]: grid = AxesGrid(f, 111, (1,2)) In [40]: f.axes Out[40]: [, , , ] In [41]: plt.clf() In [42]: f.axes Out[42]: [] Perhaps you wanted to simply to clear the individual axes? You can do that with [g.cla() for g in grid] instead of your call to plt.clf() best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] soliciting feedback on proposed user survey
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 IPython folks also did for a while). 1. http://ipython.org/usersurvey2011.html 2. https://docs.google.com/spreadsheet/viewform?formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ 3. https://docs.google.com/spreadsheet/viewanalytics?formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] soliciting feedback on proposed user survey
Paul Ivanov, on 2012-03-28 17:22, wrote: > 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 IPython folks also did > for a while). > > 1. http://ipython.org/usersurvey2011.html > 2. > https://docs.google.com/spreadsheet/viewform?formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ > 3. > https://docs.google.com/spreadsheet/viewanalytics?formkey=dHpQS25pcTZIRWdqX0pNckNSU01sMHc6MQ Me again, just decided to inline the survey text, so that suggestions can be more readily made here, without having to following links, etc. matplotlib user survey 2012 Stand up and be counted, matplotlib developers want to hear from you! All questions are optional, we look forward to your feedback. ━━━ What country are you from? [] How long have you been using matplotlib? • (*) about a month • ( ) < 6 months • ( ) about a year • ( ) 2 to 4 years • ( ) more than 4 years What operating system do you run matplotlib on? (check all that apply) • [ ] *BSD (FreeBSD, NetBSD, OpenBSD, etc) • [ ] GNU/Linux (Ubuntu, Debian, Fedora, RHEL, OpenSUSE, Arch, Gentoo, etc) • [ ] Mac OS X • [ ] Windows • [ ] Other: [] What version of python do you use matplotlib on? (check all that apply) • [ ] 2.4 • [ ] 2.5 • [ ] 2.6 • [ ] 2.7 • [ ] 3.0 • [ ] 3.1 • [ ] 3.2 You use matplotlib for: (check all that apply) • [ ] Academic development (research, publication graphics, etc.) • [ ] Commercial development • [ ] Personal hobby / recreationally You *primarily* use matplotlib for: (check all that apply) • ( ) Academic development (research, publication graphics, etc.) • ( ) Commercial development • ( ) Personal hobby / recreationally How do you use matplotlib? [ ] [ ] [ ] How frequently do you *RUN* code which uses matplotlib? • ( ) daily • ( ) a few times per week • ( ) a few times per month • ( ) less frequently How frequently do you *WRITE* code which uses matplotlib? • ( ) daily • ( ) a few times per week • ( ) a few times per month • ( ) less frequently For the matplotlib project, do you know how to ... (check all that apply, you'll get all the answers after you hit the submit button) • [ ] locate and navigate the official documentation • [ ] run the test suite • [ ] file bug reports on GitHub • [ ] post to the matplotlib-users list • [ ] submit patches / pull requests In the past year, have you... (check all that apply) • [ ] accessed the official documentation • [ ] run the test suite • [ ] filed a bug report on GitHub • [ ] posted to the matplotlib-users list • [ ] submitted a patch / pull request How do you get matplotlib on your machine? (check all that apply) • [ ] compile and install directly from source (zip / tarball / git checkout) • [ ] use official packages provided by matplotlib team • [ ] use packages provided by my operating system (.deb, .rpm, ports, etc) • [ ] Enthought Python Distribution (EPD) http://enthought.com/products/epd.php • [ ] Python(X,Y) http://code.google.com/p/pythonxy/ • [ ] Sage http://sagemath.org/ • [ ] Other: [] What other plotting libraries do you use and why? [ ] [
Re: [matplotlib-devel] soliciting feedback on proposed user survey
Ok, added a question about backends. Hopefully I didn't miss one. Which backends do you use? (check all that apply, note that there is a "I don't know. What's a backend?" option) Agg Cairo FLTKAgg GDK GTK GTKAgg GTKCairo macosx PDF PS QTAgg QT4Agg SVG TkAgg WX WXAgg I don't know. What's a backend? -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] switching rc files (and discussion of styles)
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 lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] switching rc files (and discussion of styles)
On Fri, May 11, 2012 at 2:45 PM, Michael Droettboom wrote: > The next major release (which will include Python 3 support) bumps the > minimum requirement up to Python 2.6. Right, this was my working assumption when I made the 'with' statement suggestion. Since it's a new feature, it won't make it into the 1.1.x series, and in the next major relase (>= py2.6) we can safely use context managers. best -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] JavaScript plotting and IPython Notebook (on IPython-dev list)
Hey everyone, I know many people follow both lists, but I just wanted to point to a lively set of threads which contain "notebook plots via javascript" in the subject. it's split up into many separate conversations, so it's best to just go to this page and then search around: http://mail.scipy.org/pipermail/ipython-dev/2012-June/thread.html The limitations and advantages of current solutions and possible future directions (and possible future dead ends) have been discussed, both in terms of MPL specifically, and in terms of alternatives. -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Hacking on matplotlib
On Tue, Jul 10, 2012 at 8:06 PM, Benjamin Root wrote: > On Tuesday, July 10, 2012, Mike Kaufman wrote: >> >> It would be nice to have the label and title methods take a Text object >> (and a list of text objects -- each of whom could supply a piece of >> different colored text) in addition to a string. >> >> A list of text objects would be automagically concatenated together. How >> to generalize alignment of multiple text objects? Haven't thought that >> far yet. >> >> Either that or develop some additional color markup (and a parser) >> inside a string. Admittedly a bigger project -- though probably a better >> solution. >> >> M >> > > That is already a wishlist item. Feel free to comment on its discussion > thread with your ideas. For reference, I believe Ben's referring to #697 [1], for which I provided a possible implementation, which has the automagic concatenation you seek. 1. https://github.com/matplotlib/matplotlib/issues/697 best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] documentation error at http://matplotlib.sourceforge.net/sampledoc/custom_look.html
thanks, Keith, looks like Michael fixed the apostrophe. But not the misspelling of Eliot's last name. I've update it now. On Tue, Aug 28, 2012 at 8:50 AM, wrote: > “TS Elliots’ maxim” should be “T. S. Eliot’s maxim” J > > > > Keith > > > > > > > -- > 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/ > ___ > Matplotlib-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- 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/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Last call for 1.2.0
On Wed, Nov 7, 2012 at 6:23 PM, Michael Droettboom wrote: > The milestone is clear. Is there anything we're missing? > > If not, I plan to cut a final release and update the documentation > website tomorrow morning. I just submitted #1462 against v1.2.x, (which is also pending as #1458 against master). "use plt.subplots() in examples as much as possible" replaces a whole bunch of example code like this: fig = plt.figure() ax = plt.subplot(111) # or plt.add_subplot(111) to be just this: fig, ax = plt.subplots() This is a docs-only update - but I think it'll be worthwhile to start to give a more sensible way of creating figures and axes in one call for our the folks who'll be looking at matplotlib with fresh eyes after the 1.2 release. But I totally understand if folks feel this is too big of a pill to swallow this late in the game. go, team, go! -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] New plot type idea -- EventRaster
On Mon, Nov 12, 2012 at 7:36 AM, Michael Droettboom wrote: > On 11/11/2012 11:51 PM, Todd wrote: >> Now that 1.2 is out, can we revisit this? I would like to get it >> implemented for the next feature release. >> > > Absolutely. I think the next step, once you have an implementation, > would be to submit a pull request and we can all help with a review. This hasn't been mentioned yet, but Todd will hopefully find our developer docs useful: http://matplotlib.org/devel/index.html In particular, there's a section on writing a new pyplot function: http://matplotlib.org/devel/coding_guide.html#writing-a-new-pyplot-function -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] master vs maintenance branches (current process and proposal for future workflow)
Hey everyone, So I don't have a clear picture in my head of our development cycle, and I don't think it's well documented. I didn't want thread jack, but in another thread Mike wrote: On Mon, Nov 12, 2012 at 7:36 AM, Michael Droettboom wrote: > (BTW -- feel free to submit pull requests at any point in a release > cycle -- we have both a master and a maintenance branch, so we can work > on new stuff and stable stuff at the same time). My first question is, how are these two branches related, because I've been submitting things against master, and then switching it to be against 1.2.x when I was asked. From what I have gathered, 1.2.x is for bugfixes, and master is for new features. Can someone clarify the current process, with a section like "Submitting new Pull Requests" - this should probably go into one of these places: http://matplotlib.org/devel/coding_guide.html http://matplotlib.org/devel/gitwash/index.html My second question is that, if I do have the right idea about the current process, and the distinction between master and 1.2.x, should we change this? (I think we should). The trouble is that it seems to me now for a bugfix, if it is submitted against 1.2.x, it won't be fixed in master until changes from 1.2.x are merged back into master. So now as a developer trying to follow "bleeding edge" matplotlib, I either have to live with bugs that have been fixed in 1.2.x if I want the features from master, or if I want the bug fixes and follow 1.2.x, I miss the new features in master. I think that the mental picture is sufficiently clearer if *everything* (bugfixes and new features) go into master, and then we backport the critical bugfixes against 1.2.x. This would be easier to do if the core developer merging the bugfix into master at least opens an issue for as a placeholder / reminder for the bugfix being a candidate to go into the maintenance branch. Because it seems like at this point, we aren't even sure if we're going to do a 1.2.1 release... better, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] tick_params direction 'inout'
On Wed, Nov 14, 2012 at 7:37 PM, Mike Kaufman wrote: > Hi all, > > I don't have time to make a patch at the moment, but I thought I'd point > it out for anyone to give it a go... > > tick_params(axis='both', **kwargs) > Change the appearance of ticks and tick labels. > > Keyword arguments: > > ... > > *direction* : ['in' | 'out'] > Puts ticks inside or outside the axes. > > I just found that *direction* accepts 'inout' as well, which > does indeed place the tick on both sides of the spine. So the > documentation should be updated to reflect this. Thanks for the report, Mike, here's a PR for the patch: https://github.com/matplotlib/matplotlib/pull/1503 > If it were me, I'd allow 'both' to work as well. > I'm amenable to that, just not sure if that counts as a new feature and should go into master, or a bugfix and go into v1.2.x. I can add this functionality to #1503 if that makes sense to go to v1.2.x -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Matplotlib 'testing' page link broken
On Tue, Nov 20, 2012 at 2:21 PM, Damon McDougall wrote: > http://matplotlib.org/devel/coding_guide.html > > Scroll down to 'Testing'. Click 'Testing'. Boom. > seems to have been fixed now. The "Testing" link over at http://matplotlib.org/devel/coding_guide.html#testing takes me to http://matplotlib.org/devel/testing.html#testing -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] DeprecationWarnings in matplotlib effectively invisible (with proposed fix)
Hey everyone, In adding a deprecation warning in this pull request [1], Damon and I learned that DeprecationWarnings are ignored by default in Python 2.7 This is rather unfortunate, and I outlined possible workarounds that I see in a commend on that PR [2]. In trying to rectify this situation, I have created a MatplotlibDeperecationWarning class that inherits from UserWarning, which is *not* ignored by default. [3] 1. https://github.com/matplotlib/matplotlib/pull/1535 2. https://github.com/matplotlib/matplotlib/pull/1535#issuecomment-11061572 3. https://github.com/matplotlib/matplotlib/pull/1565 Any feedback is appreciated, better, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] DeprecationWarnings in matplotlib effectively invisible (with proposed fix)
On Wed, Dec 5, 2012 at 1:52 PM, Nathaniel Smith wrote: > If you're defining your own warning class, you might consider using > FutureWarning instead of UserWarning. > > We had a discussion about this issue for numpy recently: > http://mail.scipy.org/pipermail/numpy-discussion/2012-May/062460.html > What we eventually ended up with: > http://mail.scipy.org/pipermail/numpy-discussion/2012-May/062468.html Thanks for the pointers, Nathaniel. Though I think I disagree with continuing to use DeprecationWarnings for features that will go away and just break code - shouldn't users be given ample opportunity of coming changes without having to find out by having their code break at a future release? Robert Kern wrote: > Using FutureWarning for deprecated functions (i.e. functions that will > disappear in future releases) is an abuse of the semantics. > FutureWarning is for things like the numpy.histogram() changes from a > few years ago: changes in default arguments that will change the > semantics of a given function call. Some of our DeprecationWarnings > possibly should be FutureWarnings, but most shouldn't I don't think. then Nathaniel summarized: > If a function or similar will just disappear in a future release, > causing obvious failures in any code that depends on it, then > DeprecationWarning is fine. People's code will unexpectedly break from > time to time, but in safe ways, and anyway downgrading is easy. > - Otherwise FutureWarning is preferred And most of our DeprecationWarnings *are* about code that will just disappear in future releases. -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7> -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] closing (and opening) the user survey?
Hey everyone, I hope this email finds you well. I got a request today from someone wanting to look at the survey results. How do you feel about just sharing the full document? We're at 580 responses right now, and it's been really a slow trickle in last couple of weeks after the initial splash. Or we could do another round on twitter and G+ and say the survey will be closed at the end of the month, and then release the results. Thoughts? best, -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_).../ | \ --...J Paul Ivanov http://pirsquared.org -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Any IPython issues?
Hi David, everyone, David P. Sanders, on 2013-07-24 08:10, wrote: > Just wanted to say that I am currently at the IPython > developers' meeting in case, so I can act as a conduit in case > anybody has any suggestions / comments / bugs related to the > matplotlib--IPython interaction. I've been a bit quieter on the Matplotlib side lately, but since I'm now full-time on IPython, I wanted to pipe in that I, too, can act as a conduit. Not only for the dev meeting, but in perpetuity. I think Fernando's too busy to monitor this list closely, so you can think of me as matplotlib mole on the ipython core dev team (since I did get my matplotlib commit rights first) :) best, -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_)----.../ | \ --...J Paul Ivanov http://pirsquared.org -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] matplotlib Hangout today at 14:00 UTC (10:00am ET)
One quick reply: Daniele Nicolodi, on 2013-10-24 21:03, wrote: > One thing I dislike is, for example, the add_subplot() method: > > f = plt.figure() > a = f.add_subplot(111) > a.plot(x, y) > > it feels completely out of place (why I need to add a subplot if the > only thing I want to do is to create a figure with a single plot in it?) > and kind of magic (what is the number 111?). f, a = plt.subplots() a.plot(x, y) that's the way to go there. And if you need to make a regular grid of subplots, you can pass it the number of rows and number of columns, and get a 2D array of subplots out for the second argument. f, axes = plt.subplots(2,3) axes[0,2].plot(range(10)) axes[1,1].plot(-np.arange(10)) f.canvas.draw() best, -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_)----.../ | \ --...J Paul Ivanov http://pirsquared.org -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] matplotlib Hangout today at 14:00 UTC (10:00am ET)
Michael Droettboom, on 2013-10-24 09:41, wrote: > I'll post a public URL to watch along once it begins as well. Here's the youtube video link (which I got from Mike's G+): https://www.youtube.com/watch?feature=player_embedded&v=hWA6dMiSUiU best, -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_).../ | \ --...J Paul Ivanov http://pirsquared.org -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Hangout today
Michael Droettboom, on 2013-11-14 10:23, wrote: > Sorry - I've been without network connection this morning, but it's back > up... > > I'll be starting the matplotlib hangout shortly. Let me know if you > don't get an invite and would like to join. Mike and others, is there a link to this hangout, or was this one not recorded "on-air"? best, -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_).../ | \ --...J Paul Ivanov http://pirsquared.org -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Hangout today
Matthew Brett, on 2013-11-15 11:23, wrote: > Sorry not to get to setting up buildbot testing. Paul - do you > have time for that? I'm happy to make time for that, I guess I'll follow up with Mike, Matthew, and Matt Terry offlist about what needs doing. -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_).../ | \ ------...J Paul Ivanov http://pirsquared.org -- DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] PEP 8 change in Travis
Nelle Varoquaux, on 2014-03-26 21:27, wrote: > > Does anyone know why we are seeing a huge number of PEP 8 failures now? > > It looks to me like it is a change in which modules are subject to the > > test, or in which tests are grounds for failure. I don't know how all > > this is set up, though. > > If it started very recently, it could be linked to the new release. They > have started to make "none backward" compatible version, in the sense that > the stylechecker is increasingly strict. It is very annoying... Can we not revisit (and possibly revert) the morally absolutist PEP-8 or death position that matplotlib has taken? Quoting GvR (emphasis mine): All I want to say is, people lighten up. The style guide can't solve all your problems. You are never going to have all code compliant. Use the style guide when it helps, *ignore it when it's in the way* And from that same email: Let's try to make new stdlib modules use the best style we can think of, but limit the time spent fretting over code that's already there. The rest of the message is useful to read: https://mail.python.org/pipermail/python-dev/2010-November/105681.html Another reason for not being so rigid about PEP-8 is that its a living document. Are we really doing massive search-and-replace changes to the codebase just to comply with a moving target? best, -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_).../ | \ --...J Paul Ivanov http://pirsquared.org -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Fwd: v1.4 feature freeze + release timeline
Thomas Kluyver, on 2014-05-16 08:56, wrote: > On 16 May 2014 01:17, "Eric Firing" wrote: > > Maybe this problem could be reduced by having a directory for CHANGELOG > > chunks, one file per PR, with the PR number as the filename. Then at > > release time they could be concatenated, edited, appended to the real > > CHANGELOG, and deleted. > > We already do this in ipython for our 'whatsnew' document. We allow > arbitrary filenames rather than using PR numbers, and then we concatenate > everything from the directory periodically. You're welcome to copy our > script to do this. Yes, this has been working out quite nicely for us, and we started doing it for the very same reasons - to keep conflicts to a minimum while making it easier to keep track of everything that has gone in. Here's the direct link to our script: https://github.com/ipython/ipython/blob/master/tools/update_whatsnew.py -- _ / \ A* \^ - ,./ _.`\\ / \ / ,--.S\/ \ / `"~,_ \\ __o ? _ \<,_ /:\ --(_)/-(_).../ | \ --...J Paul Ivanov http://pirsquared.org -- "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] bad formatting on main page
Looks like Thomas Caswell changed what used to be tags to be tags, and those are getting their own lines. The fix would be to either change them back to tags, or adjust the CSS to wrap elements (instead of line breaking them) On Fri, Sep 19, 2014 at 1:16 PM, Benjamin Root wrote: > I just took a peek at the matplotlib.org page, and there is something > wonky going on. The word "pyplot" in one of the paragraphs is getting a > line all to itself. Similarly, a reference to "IPython" is also getting a > line for itself. > > Ben Root > > > -- > Slashdot TV. Video for Nerds. Stuff that Matters. > > http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk > ___ > Matplotlib-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > -- Slashdot TV. Video for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] RFC: candidates for a new default colormap
1. C 2. B 3. A But I wouldn't call them aesthetic - the purple in there just looks off - I'd prefer something like hot, afmhot, or gist_heat - or variations on those. Since this thread is bound to get plenty of attention (I suggest getting feedback from -users, too), we would be remiss if we didn't point those who didn't already see the writeup of colormaps that Kristen Thyng and colleagues did in the docs [1]. Also, I added a pointer to this thread over on #875 [2]. 1. http://matplotlib.org/users/colormaps.html 2. https://github.com/matplotlib/matplotlib/issues/875 -- ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
