Re: [matplotlib-devel] Release schedule

2015-06-16 Thread OceanWolf
The only concerns on doing 1.5 - 2.0 come from the huge amount of extra work in uncherrypicking recherrypicking. Given the amount of testing that both master and color-overhaul have gone through by us devs and other interested people, I feel it perhaps better to keep the release schedule as it

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-06 Thread Benjamin Root
sunset has a connotation of things ending. Howabout sunrise? On Sun, Apr 5, 2015 at 5:18 PM, Olga Botvinnik obotv...@ucsd.edu wrote: How about pythonic sunset ? On Sun, Apr 5, 2015 at 2:01 PM Benjamin Root ben.r...@ou.edu wrote: That is nice. The blue is a bit heavy, but that might be my

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Benjamin Root
That is nice. The blue is a bit heavy, but that might be my display. Now, how should we order it by default? I am used to thinking of blues as lower values, and reds as higher. The yellow at the end throws me off a bit, because I would think of it as a weaker color. Maybe if it was more gold-like?

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Olga Botvinnik
How about pythonic sunset ? On Sun, Apr 5, 2015 at 2:01 PM Benjamin Root ben.r...@ou.edu wrote: That is nice. The blue is a bit heavy, but that might be my display. Now, how should we order it by default? I am used to thinking of blues as lower values, and reds as higher. The yellow at the

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread OceanWolf
I like it, but perhaps we should condense it to one word for ease of typing, how about Redgauntlet? It kind of feels appropriate (for those who need an explanation of why, see https://www.youtube.com/watch?v=_guKhYVr5vA). On the colormap itself, it looks good apart from the fade into blue,

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread gary ruben
Just wondering whether anyone has suggested checking candidate colormaps against typical printer color gamuts? On 6 Apr 2015 1:11 pm, Eric Firing efir...@hawaii.edu wrote: On 2015/04/04 10:10 PM, Nathaniel Smith wrote: We'd welcome any feedback from readers with non-simulated color

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Nathaniel Smith
On Apr 5, 2015 8:29 PM, gary ruben gary.ru...@gmail.com wrote: Just wondering whether anyone has suggested checking candidate colormaps against typical printer color gamuts? How would you go about doing this in practice? Is it even possible to choose a subset of sRGB space and have printers

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Eric Firing
problems as well. Eric Forwarded Message Subject: Re: [matplotlib-devel] release strategy and the color revolution Date: Sun, 5 Apr 2015 00:20:03 -0700 From: Nathaniel Smith n...@pobox.com To: Eric Firing efir...@hawaii.edu CC: Michael Waskom mwas...@stanford.edu

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Nathaniel Smith
On Mon, Feb 23, 2015 at 10:46 AM, Eric Firing efir...@hawaii.edu wrote: On 2015/02/18 2:39 PM, Nathaniel Smith wrote: On Feb 16, 2015 3:39 PM, Eric Firing efir...@hawaii.edu wrote: On 2015/02/16 1:29 PM, Michael Waskom wrote: Nathaniel's January 9 message in that thread (can't figure out

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Nathaniel Smith
On Sun, Apr 5, 2015 at 12:46 AM, Eric Firing efir...@hawaii.edu wrote: On 2015/04/04 9:20 PM, Nathaniel Smith wrote: While it's taking longer than hoped, just to reassure you that this isn't total vaporware, here's a screenshot from the colormap designer that Stéfan van der Walt and I have

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Eric Firing
On 2015/04/04 9:20 PM, Nathaniel Smith wrote: While it's taking longer than hoped, just to reassure you that this isn't total vaporware, here's a screenshot from the colormap designer that Stéfan van der Walt and I have been working on... still needs fine-tuning (which at this point probably

Re: [matplotlib-devel] release strategy and the color revolution

2015-04-05 Thread Juan Nunez-Iglesias
3 3 3 Love the prototype colormap!!!-- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software

Re: [matplotlib-devel] release strategy and the color revolution

2015-03-17 Thread Thomas Caswell
I have opened a PR to document this discussion. It is meant to provide a permanent record of the thought process leading up to color map and to serve as a tool in making the finial decision. https://github.com/matplotlib/matplotlib/pull/4238 On Mon, Mar 2, 2015 at 6:32 AM jni jni.s...@gmail.com

Re: [matplotlib-devel] release strategy and the color revolution

2015-03-02 Thread Pierre Haessig
Hi, Le 01/03/2015 23:27, jni a écrit : As someone working with images, I think for displaying images you want a colormap that spans as much as possible of the luminance range. The colormap suggested by Michael Waskom would be quite perfect as-is. (recap: middle colormap here:

Re: [matplotlib-devel] release strategy and the color revolution

2015-03-02 Thread jni
Hi Pierre, Could you please elaborate a bit on this usecase. I was thinking, naively, that when plotting a grayscale image, one would simply used a gray colormap. Using a colormap with hue and saturation gives you better contrast than pure grayscale. For natural images, that is, photographs

Re: [matplotlib-devel] release strategy and the color revolution

2015-03-01 Thread jni
Hi everyone, As someone working with images, I think for displaying images you want a colormap that spans as much as possible of the luminance range. The colormap suggested by Michael Waskom would be quite perfect as-is. (recap: middle colormap here:

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-28 Thread Todd
On Feb 19, 2015 1:39 AM, Nathaniel Smith n...@pobox.com wrote: On Feb 16, 2015 3:39 PM, Eric Firing efir...@hawaii.edu wrote: On 2015/02/16 1:29 PM, Michael Waskom wrote: Nathaniel's January 9 message in that thread (can't figure out how to link to it in the archives) had a

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-28 Thread Benjamin Root
Well, since we are thinking of it... What about prettyplotlib's style? I am not sure I want to completely steal either project's style as it is their own look-n-feel (and there are some aspects of their styles I don't quite like, but I am something of a luddite...). But I would certainly be

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-23 Thread Eric Firing
On 2015/02/18 2:39 PM, Nathaniel Smith wrote: On Feb 16, 2015 3:39 PM, Eric Firing efir...@hawaii.edu wrote: On 2015/02/16 1:29 PM, Michael Waskom wrote: Nathaniel's January 9 message in that thread (can't figure out how to link to it in the archives) had a suggestion that I thought was very

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-23 Thread Pierre Haessig
Hi, Le 16/02/2015 23:01, Eric Firing a écrit : For a long time there has been discussion of replacing the matplotlib default color map [...] I've started building a small interactive Lab point editor to build a sequential colormap. https://github.com/pierre-haessig/lab-colormap-creator The

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-23 Thread Benjamin Root
Interesting choices, and I think we are on the right paths (no pun intended) through the two possible colors. However, I think the same problem arises that I noted before. Both ends of the colormap are nearly black to nearly white. IIRC, our perception of luminosity has a much greater range than

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-23 Thread Eric Firing
On 2015/02/23 8:16 AM, Benjamin Root wrote: Interesting choices, and I think we are on the right paths (no pun intended) through the two possible colors. However, I think the same problem arises that I noted before. Both ends of the colormap are nearly black to nearly white. IIRC, our

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-23 Thread Benjamin Root
My eyes are definitely favoring the L20-80 over the L5-95 colormaps. Does Luminosity take into account human's non-linearity in perceiving brightness? I remember a few years ago many of the open-source graphics tools (such as GIMP) had to be fixed because it assumed a linear brightness perception.

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Michael Waskom
Cool! I knew there had been some useful tools posted on the earlier thread but didn't have time to dig them out. Interesting observation about the colorfulness. I don't know enough about all the transformations involved to full account for that, but I added some stuff to the notebook to figure

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Michael Waskom
I've made a second notebook that uses the IPython interactive machinery to let anyone play with the parameters and explore different ways of setting them. you can download the notebook with that here: http://nbviewer.ipython.org/gist/mwaskom/842d1497b6892d081bfb (I made it using IPython 3.0rc1;

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Benjamin Root
The problem I have with hcl is that while it is technically colorful (or whatever the term may be), only the reds really come out because the other colors are only used when either really light or really dark. Perhaps squashing the brightness range a bit and let the natural lightness of yellow

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Eric Firing
On 2015/02/18 6:31 AM, Benjamin Root wrote: The problem I have with hcl is that while it is technically colorful (or whatever the term may be), only the reds really come out because the other colors are only used when either really light or really dark. Perhaps squashing the brightness range a

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Michael Waskom
On Wed, Feb 18, 2015 at 4:42 PM, Olga Botvinnik obotv...@ucsd.edu wrote: FYI the notebook isn't working for me in IPython 2.2.0 Oops, sorry. I agree with Michael's sentiment that from a marketing perspective, a matplotlib-only colormap is advantageous to maintain a consistent brand. Just

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Eric Firing
On 2015/02/18 2:39 PM, Nathaniel Smith wrote: On Feb 16, 2015 3:39 PM, Eric Firing efir...@hawaii.edu wrote: On 2015/02/16 1:29 PM, Michael Waskom wrote: Nathaniel's January 9 message in that thread (can't figure out how to link to it in the archives) had a suggestion that I thought was very

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Olga Botvinnik
FYI the notebook isn't working for me in IPython 2.2.0 I agree with Michael's sentiment that from a marketing perspective, a matplotlib-only colormap is advantageous to maintain a consistent brand. Will these colormaps also be used for non-imshow/colormesh/pcolormesh data, as in for line colors

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Thomas Caswell
@Nathaniel I think developing the color-overhaul as a maintenance release is a decent compromise. All non-color changes get directed at the master branch and we can cherry-picked back bug-fixes as needed. The next feature release is planned for July/August, I _really_ hope sorting out the colors

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Michael Waskom
On Wed, Feb 18, 2015 at 5:23 PM, Eric Firing efir...@hawaii.edu wrote: Do you think there is a way to make a sequential map that is more pleasing to those of us who are more comfortable with blues and greens than with the slightly muddy purples and browns in the initial attempt at HCL? Just

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Eric Firing
On 2015/02/18 2:42 PM, Olga Botvinnik wrote: FYI the notebook isn't working for me in IPython 2.2.0 I agree with Michael's sentiment that from a marketing perspective, a matplotlib-only colormap is advantageous to maintain a consistent brand. Provided we can find a good colormap for that

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-18 Thread Nathaniel Smith
On Feb 16, 2015 3:39 PM, Eric Firing efir...@hawaii.edu wrote: On 2015/02/16 1:29 PM, Michael Waskom wrote: Nathaniel's January 9 message in that thread (can't figure out how to link to it in the archives) had a suggestion that I thought was very promising, to do something similar to

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-17 Thread Michael Waskom
Hey Olga, On Tue, Feb 17, 2015 at 6:24 PM, Olga Botvinnik obotv...@ucsd.edu wrote: Out of curiosity, what are the advantages of the HCL colormap over YlGnBu for continuous values? I'm biased towards YlGnBu because green is my favorite color and want to know what makes HCL objectively better

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-17 Thread Olga Botvinnik
Out of curiosity, what are the advantages of the HCL colormap over YlGnBu for continuous values? I'm biased towards YlGnBu because green is my favorite color and want to know what makes HCL objectively better for perceiving values. I added YlGnBu_r versions of those plots just below yours:

Re: [matplotlib-devel] Release planning/milestones

2015-02-17 Thread Todd
I wasn't referring to just the default colors, but the default style in general. Things like background, line thickness, padding, ticks, etc. I thought that there was agreement that the default matplotlib style is not optimal, and that the point of the 2.0 release was to put all the stylistic

[matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Eric Firing
For a long time there has been discussion of replacing the matplotlib default color map and color cycle, but we still haven't done it. We need a clear set of criteria, and a small set of good alternatives, leading to a decision, a PR, and a release. Now is the time. Here is what I think is

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Paul Hobson
There are several cycles in seaborn. Is it safe to assume that you mean the 'deep' palette? On Mon, Feb 16, 2015 at 14:40 Eric Firing efir...@hawaii.edu wrote: On 2015/02/16 12:01 PM, Eric Firing wrote: Proposals for the new color cycle for line plots? Here is a proposal: we simply adopt

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Michael Waskom
On Mon, Feb 16, 2015 at 3:15 PM, Eric Firing efir...@hawaii.edu wrote: Does anyone have a suggestion for a colorblind-friendly cycle? Maybe omit the green and tack a gray on the end? I haven't checked, so I don't know if this would work well. Here are two palettes that are optimized for

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Michael Waskom
On Mon, Feb 16, 2015 at 3:19 PM, Michael Waskom mwas...@stanford.edu wrote: Here are two palettes that are optimized for colorblindness actually I should say I have no idea if those are optimal, but the simulations do suggest they work well.

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Michael Waskom
On Mon, Feb 16, 2015 at 2:01 PM, Eric Firing efir...@hawaii.edu wrote: Here is what I think is the most recent extensive thread: http://comments.gmane.org/gmane.comp.python.matplotlib.devel/13122 ... 1) A greyscale has been proposed; it satisfies several of the criteria very well, but

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Michael Waskom
See [here](http://nbviewer.ipython.org/gist/mwaskom/6a43a3b94eca4a9e2e8b) for a quick and dirty implementation that should get a general idea. This probably ins't the best way to do it -- anyone should feel free to build on this. On Mon, Feb 16, 2015 at 3:38 PM, Eric Firing efir...@hawaii.edu

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Eric Firing
On 2015/02/16 12:42 PM, Paul Hobson wrote: There are several cycles in seaborn. Is it safe to assume that you mean the 'deep' palette? Yes, in the sense that when I wrote the message I was just looking at seaborn's tutorial showing the default, which is 'deep'--but I didn't know it then. A

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Eric Firing
On 2015/02/16 1:19 PM, Michael Waskom wrote: Here are two palettes that are optimized for colorblindness: http://www.cookbook-r.com/Graphs/Colors_%28ggplot2%29/#a-colorblind-friendly-palette Strange--they have both red and green, so I would never have expected them to work. The yellow looks

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Eric Firing
On 2015/02/16 1:29 PM, Michael Waskom wrote: Nathaniel's January 9 message in that thread (can't figure out how to link to it in the archives) had a suggestion that I thought was very promising, to do something similar to Parula but rotate around the hue circle the other direction so that the

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Michael Waskom
It's helped by pulling the green towards blue and the red towards yellow, but they are probably the hardest to distinguish in the set. Which emphasizes that, while it's good to start with a colorblind-friendly set of colors, the person making the figure also has the responsibility to choose how

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Eric Firing
On 2015/02/16 12:01 PM, Eric Firing wrote: Proposals for the new color cycle for line plots? Here is a proposal: we simply adopt seaborn's cycle. Eric -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT

Re: [matplotlib-devel] release strategy and the color revolution

2015-02-16 Thread Benjamin Root
Do remember that I have a PR to add linestyle cycling, which would greatly mitigate problems for colorblindness and non-color publications. I also prefer it for slideshows as projectors at conferences tend to have crappy colors anyway (was at a radar conference when the projector's red crapped

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Sandro Tosi
Hi all! On Sun, Feb 8, 2015 at 12:13 AM, Thomas Caswell tcasw...@gmail.com wrote: Hey all, To start with, the 2.0 release is pending a choice of new default color map. I think that when we pick that we should cut 2.0 off of the last release and then the next minor release turns into 2.1. If

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Thomas Caswell
Ah, no I mean the exact opposite! My proposal is to cut 2.0 off of what ever the current stable release is (ex, 1.4.3) and then merge that into master. The next minor release would then be 2.1 and there would be no new 1.Y releases. Tom On Sun Feb 08 2015 at 2:04:24 PM Sandro Tosi

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Todd
On Feb 8, 2015 1:13 AM, Thomas Caswell tcasw...@gmail.com wrote: Hey all, To start with, the 2.0 release is pending a choice of new default color map. I think that when we pick that we should cut 2.0 off of the last release and then the next minor release turns into 2.1. If we want to do

[matplotlib-devel] Release planning/milestones

2015-02-07 Thread Thomas Caswell
Hey all, To start with, the 2.0 release is pending a choice of new default color map. I think that when we pick that we should cut 2.0 off of the last release and then the next minor release turns into 2.1. If we want to do other breaking changes we will just do a 3.0 when that happens. It

[matplotlib-devel] Release Candidate

2012-09-10 Thread Michael Droettboom
Today is the scheduled day for release candidate 1.2rc1. We seem to be in really good shape. Thanks to everyone that has been working so hard to squash bugs, particularly ones that turned out to be bottomless rabbit holes. We have a few outstanding issues, which I'll categorize below:

Re: [matplotlib-devel] Release Candidate

2012-09-10 Thread Nelle Varoquaux
Hello, Do you still accept pep8 cleaning up ? I've got a couple of important deadlines coming up soon, but I might be able to clean up the whole code. Thanks, N On 10 September 2012 18:00, Michael Droettboom md...@stsci.edu wrote: Today is the scheduled day for release candidate 1.2rc1. We

Re: [matplotlib-devel] Release Candidate

2012-09-10 Thread Michael Droettboom
I'd certainly like to see that work continue, but I don't know if it's worth holding up the release candidate for. We probably won't get it out today given the other critical things yet to go in -- but once the release candidate is cut, I'd prefer to be really conservative about what changes

Re: [matplotlib-devel] Release Candidate

2012-09-10 Thread Mark Lawrence
On 10/09/2012 17:00, Michael Droettboom wrote: Today is the scheduled day for release candidate 1.2rc1. We seem to be in really good shape. Thanks to everyone that has been working so hard to squash bugs, particularly ones that turned out to be bottomless rabbit holes. We have a few

Re: [matplotlib-devel] Release Candidate

2012-09-10 Thread Michael Droettboom
On 09/10/2012 12:49 PM, Mark Lawrence wrote: My offer to test on Windows still holds. The question is test what? Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then different versions of Visual Studio are needed as detailed here http://bugs.python.org/issue13210. I can't see

Re: [matplotlib-devel] Release Candidate

2012-09-10 Thread Damon McDougall
On Mon, Sep 10, 2012 at 5:00 PM, Michael Droettboom md...@stsci.edu wrote: We have a few outstanding issues, which I'll categorize below: Critical things that need just a little more work: #1223dpi= for bitmaps not handled correctly I don't believe this is release critical. It only

Re: [matplotlib-devel] Release Candidate

2012-09-10 Thread Christoph Gohlke
On 9/10/2012 10:08 AM, Michael Droettboom wrote: On 09/10/2012 12:49 PM, Mark Lawrence wrote: My offer to test on Windows still holds. The question is test what? Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then different versions of Visual Studio are needed as detailed

[matplotlib-devel] release: stalled again?

2011-09-17 Thread Eric Firing
What will it take to get a release out, so that debian, ubuntu, etc. can have something better than 1.0.1? And so that the python 3 merge can take place? Eric -- BlackBerryreg; DevCon Americas, Oct. 18-20, San

Re: [matplotlib-devel] release: stalled again?

2011-09-17 Thread Benjamin Root
I think it will take a declaration of a firm deadline. How about this? Cut RC release Friday, Sept 23rd Release v1.1.0 Friday, Sept. 30th. (Barring any major significant changes) In particular, for the RC, I want to make sure that installation and documents for the installation is solid. I

Re: [matplotlib-devel] release: stalled again?

2011-09-17 Thread Christoph Gohlke
On 9/17/2011 2:08 PM, Benjamin Root wrote: I think it will take a declaration of a firm deadline. How about this? Cut RC release Friday, Sept 23rd Release v1.1.0 Friday, Sept. 30th. (Barring any major significant changes) In particular, for the RC, I want to make sure that installation

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread Andrew Straw
On 10/23/2010 04:59, John Hunter wrote: I would be happy to do a release early next week. Is anyone aware of any show stopper bugs that need to be fixed first? I think we should really get the build bot to all green again before doing a release. Currently, the last that happened was October

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread Benjamin Root
On Thu, Oct 28, 2010 at 12:44 AM, Andrew Straw straw...@astraw.com wrote: On 10/23/2010 04:59, John Hunter wrote: I would be happy to do a release early next week. Is anyone aware of any show stopper bugs that need to be fixed first? I think we should really get the build bot to all green

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread John Hunter
On Thu, Oct 28, 2010 at 9:05 AM, Benjamin Root ben.r...@ou.edu wrote: Just as a quick question that I would like to throw out.  It isn't a bug, but rather an aesthetics issue that I caused for the version 1.0 release. With allowing 3d plots to be made subplottable, the margins for the plot

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread Benjamin Root
On Thu, Oct 28, 2010 at 9:55 AM, John Hunter jdh2...@gmail.com wrote: On Thu, Oct 28, 2010 at 9:05 AM, Benjamin Root ben.r...@ou.edu wrote: Just as a quick question that I would like to throw out. It isn't a bug, but rather an aesthetics issue that I caused for the version 1.0 release.

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread John Hunter
On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker chris.bar...@noaa.gov wrote: On 10/25/10 1:41 PM, Daniel Hyams wrote: It doesn't really insist on it right?  There are MATPLOTLIBDIR and MPLCONFIGDIR environment variables. You can set these env variables within your code, before import of

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread Benjamin Root
On Thu, Oct 28, 2010 at 1:50 PM, John Hunter jdh2...@gmail.com wrote: On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker chris.bar...@noaa.gov wrote: On 10/25/10 1:41 PM, Daniel Hyams wrote: It doesn't really insist on it right? There are MATPLOTLIBDIR and MPLCONFIGDIR environment

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread Russell E. Owen
In article 4cc9bcd8.60...@noaa.gov, Christopher Barker chris.bar...@noaa.gov wrote: On 10/25/10 1:41 PM, Daniel Hyams wrote: It doesn't really insist on it right? There are MATPLOTLIBDIR and MPLCONFIGDIR environment variables. You can set these env variables within your code, before

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread John Hunter
On Thu, Oct 28, 2010 at 2:46 PM, Russell E. Owen ro...@uw.edu wrote: It's an interesting question. You can't call a matplotlib function to do it because it has to happen before matplotlib is loaded. I suppose there could be a configuration package to perform the operation. This is basically

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread Christopher Barker
On 10/28/10 11:50 AM, John Hunter wrote: On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker You can set these env variables within your code, before import of matplotlib via os.environment. The MPLCONFIGDIR tells mpl where to find the config file. It's hard to read the config, no matter

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-28 Thread James Evans
In reference to the configuration package idea... I (and the users that I support) use matplotlib both as a standalone plotter for generating lots of plots, as an interactive plotter, and as an embedded plot in an application environment. In all of these instances we have found the

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-26 Thread Jason Grout
On 10/23/10 10:35 PM, jason-s...@creativetrax.com wrote: On 10/22/10 7:16 PM, Michael Droettboom wrote: On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due. My application is suffering badly from the issue that an incorrect font cache

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-25 Thread Russell E. Owen
In article 4cc22964.1050...@stsci.edu, Michael Droettboom md...@stsci.edu wrote: On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due. My application is suffering badly from the issue that an incorrect font cache will cause matplotlib

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-25 Thread Russell E. Owen
In article aanlktinusoohzkqdg9p2lbpb3vyjwk3jakaqcnhnp...@mail.gmail.com, John Hunter jdh2...@gmail.com wrote: On Fri, Oct 22, 2010 at 7:16 PM, Michael Droettboom md...@stsci.edu wrote:  On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due.

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-25 Thread Daniel Hyams
On Mon, Oct 25, 2010 at 4:15 PM, Russell E. Owen ro...@uw.edu wrote: In article 4cc22964.1050...@stsci.edu, Michael Droettboom md...@stsci.edu wrote: On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due. My application is

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-25 Thread John Hunter
On Mon, Oct 25, 2010 at 3:41 PM, Daniel Hyams dhy...@gmail.com wrote: It doesn't really insist on it right?  There are MATPLOTLIBDIR and MPLCONFIGDIR environment variables.  The former is for the location of mpl-data, and is not really documented well (that I could find, anyway, but I found

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-25 Thread Daniel Hyams
Right, I was referring specifically to MATPLOTLIBDIR ;) I was just pleased as punch to find it in the source code, documented or no :) On Mon, Oct 25, 2010 at 5:06 PM, John Hunter jdh2...@gmail.com wrote: On Mon, Oct 25, 2010 at 3:41 PM, Daniel Hyams dhy...@gmail.com wrote: It doesn't

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-25 Thread John Hunter
On Mon, Oct 25, 2010 at 4:09 PM, Daniel Hyams dhy...@gmail.com wrote: Right, I was referring specifically to MATPLOTLIBDIR ;) I was just pleased as punch to find it in the source code, documented or no :) I'm guessing you mean MATPLOTLIBDATA ? And you're right, it isn't documented (yet)...

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-23 Thread John Hunter
On Fri, Oct 22, 2010 at 7:16 PM, Michael Droettboom md...@stsci.edu wrote:  On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due. My application is suffering badly from the issue that an incorrect font cache will cause matplotlib to fail (the

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-23 Thread jason-sage
On 10/22/10 7:16 PM, Michael Droettboom wrote: On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due. My application is suffering badly from the issue that an incorrect font cache will cause matplotlib to fail (the application mysteriously

Re: [matplotlib-devel] Release schedule for version 1.0.1?

2010-10-22 Thread Michael Droettboom
On 10/22/2010 05:45 PM, Russell E. Owen wrote: I'm curious when the next release of matplotlib is due. My application is suffering badly from the issue that an incorrect font cache will cause matplotlib to fail (the application mysteriously exits partway through startup until the user

[matplotlib-devel] Release candidate 2 for NumPy 1.4.1 and SciPy 0.7.2

2010-04-15 Thread Ralf Gommers
Hi, I am pleased to announce the second release candidate of both Scipy 0.7.2 and NumPy 1.4.1. Please test, and report any problems on the NumPy or SciPy list. I also want to specifically ask you to report success/failure with other libraries (Matplotlib, Pygame, your favorite lib here) based on

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-13 Thread Charlie Moad
On Mon, Apr 13, 2009 at 11:46 AM, John Hunter jdh2...@gmail.com wrote: On Sun, Apr 12, 2009 at 10:20 PM, Charlie Moad cwm...@gmail.com wrote: I updated the binaries at the same link as before: http://drop.io/tvuqe3o I just tested the python2.5 installer matplotlib-0.98.5.3.win32-py2.5.exe

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-12 Thread Charlie Moad
I updated the binaries at the same link as before: http://drop.io/tvuqe3o NOTE: I used John's OSX build scripts which ran great, but I am getting a segfault when trying to plot. I need to call it a night and might not have time to look into the issue this week. Please run with my files and feel

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-10 Thread Charlie Moad
0.98.6 only? On Wed, Apr 8, 2009 at 2:59 PM, Eric Firing efir...@hawaii.edu wrote: Charlie Moad wrote: I might be able to squeeze some time in this weekend.  I am not thrilled about the new visual studio requirements, nor do I have access to it.  I know John started a build script for OSX

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-10 Thread Charlie Moad
Sorry, I guess 0.98.5.3 looking at the branch. No need for a 0.91 update though? On Fri, Apr 10, 2009 at 3:06 PM, Charlie Moad cwm...@gmail.com wrote: 0.98.6 only? On Wed, Apr 8, 2009 at 2:59 PM, Eric Firing efir...@hawaii.edu wrote: Charlie Moad wrote: I might be able to squeeze some time

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-10 Thread Charlie Moad
I found that thread not too long ago and dug up the tool John mentioned. http://www.dependencywalker.com/ Looks like our friend msvcrXX (msvcr90 for py2.6) is back. I am removing the link from distutils right now and giving it a try. - Charlie On Fri, Apr 10, 2009 at 10:08 PM, Andrew Straw

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-10 Thread Charlie Moad
Yeah, that worked. Removed the link from distutils/cygwinccompiler.py. I didn't get the error from python 2.4 or 2.5, but that's probably because I have had them installed for a while and these dll's have been installed from other modules. I'll try to get some binaries posted soon. - Charlie

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-10 Thread Charlie Moad
http://drop.io/tvuqe3o Please test these windows builds. I committed a change to set tcltk8.5 flags for python 2.6 and I also uploaded a modified win32_static.zip file. Could someone please replace the previous one with the newer version? It includes the tcltk8.5 headers needed for the build.

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-08 Thread Charlie Moad
I might be able to squeeze some time in this weekend. I am not thrilled about the new visual studio requirements, nor do I have access to it. I know John started a build script for OSX and I have been meaning to try something similar for mingw. Is anyone opposed to creating the official

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-08 Thread william ratcliff
I'd actually prefer it ; On Wed, Apr 8, 2009 at 9:14 AM, Charlie Moad cwm...@gmail.com wrote: I might be able to squeeze some time in this weekend. I am not thrilled about the new visual studio requirements, nor do I have access to it. I know John started a build script for OSX and I have

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-08 Thread John Hunter
On Apr 8, 2009, at 9:14 AM, Charlie Moad cwm...@gmail.com wrote: I might be able to squeeze some time in this weekend. I am not thrilled about the new visual studio requirements, nor do I have access to it. I know John started a build script for OSX and I have been meaning to try

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-07 Thread Andrew Straw
John Hunter wrote: In general, only very clear bugfixes which are unlikely to result in surprise breakages should go in. The _png patch, though a bug fix, has more of the feel of a feature enhancement, and given its complexity, should probably not go in to the branch unless someone makes a

Re: [matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-07 Thread Sandro Tosi
On Tue, Apr 7, 2009 at 18:06, Andrew Straw straw...@astraw.com wrote: John Hunter wrote: We are not that far away, at least for src snapshots, os x binaries, and the docs.  The windows binary would take some work, as would a linux binary, eg a debian package. FWIW, the Debian packagers will

[matplotlib-devel] release strategy, and the role of v0_98_5_maint

2009-04-05 Thread Eric Firing
It is not always clear what should go in the 0.98.5 maintenance branch. For example, is the _png.cpp patch by Tobias, committed by Andrew, a bug fix or a new feature? I would have said the latter, but I can see arguments either way. More generally, how long do we need to keep updating this

Re: [matplotlib-devel] release? no, this time really I mean it

2008-12-09 Thread John Hunter
On Mon, Dec 8, 2008 at 5:31 PM, John Hunter [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 12:38 PM, Charlie Moad [EMAIL PROTECTED] wrote: Works for me. Let's aim for Saturday night so we have Sunday to test it out. Doable? I've been working on a number of docstring fixes, and several

Re: [matplotlib-devel] release? no, this time really I mean it

2008-12-08 Thread John Hunter
On Thu, Dec 4, 2008 at 12:38 PM, Charlie Moad [EMAIL PROTECTED] wrote: Works for me. Let's aim for Saturday night so we have Sunday to test it out. Doable? I've been working on a number of docstring fixes, and several other changes and last-minute bug fixes have been coming in. I think we

Re: [matplotlib-devel] release? no, this time really I mean it

2008-12-07 Thread Charlie Moad
Is there any need for a maintenance release? On Thu, Dec 4, 2008 at 1:53 PM, John Hunter [EMAIL PROTECTED] wrote: On Thu, Dec 4, 2008 at 12:38 PM, Charlie Moad [EMAIL PROTECTED] wrote: Works for me. Let's aim for Saturday night so we have Sunday to test it out. Doable? Great -- everyone

  1   2   >