on't break everything.
Meh, perhaps I just act too overcautious.
From: Thomas Caswell
To: OceanWolf ;
"matplotlib-devel@lists.sourceforge.net"
Sent: Wednesday, 17 June 2015, 6:04
Subject: Re: [matplotlib-devel] Release schedule
I am not sur
I am not sure what you mean by cherry-picking/uncherry picking. I just
looked at what is on `color_overhaul` which is not in master and it is:
changes that should be discarded (changes to cxx / changes to _tri.* that
rely on cxx), one change related to mathtext layout (and conflicts due to
mathext
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
Following up on the last email, I would like to aim for a 1.5 release at
the end of July, with the sprint at scipy being focused on finishing it
off. The 2.0 color/style release will happen (hopefully soon) after that.
Does this schedule seem ok to everyone?
I have started to triage the issues/
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 '.matplotlibrc
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 m
On Thu, Oct 28, 2010 at 2:46 PM, Russell E. Owen 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 what we alr
In article <4cc9bcd8.60...@noaa.gov>,
Christopher Barker 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
> >
On Thu, Oct 28, 2010 at 1:50 PM, John Hunter wrote:
> On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker
> 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 th
On Thu, Oct 28, 2010 at 1:11 PM, Christopher Barker
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
>> matplotlib v
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
> matplotlib via os.environment.
I'm glad I've learned about this, and will star
On Thu, Oct 28, 2010 at 9:55 AM, John Hunter wrote:
> On Thu, Oct 28, 2010 at 9:05 AM, Benjamin Root 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
On Thu, Oct 28, 2010 at 9:05 AM, Benjamin Root 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
> area became
On Thu, Oct 28, 2010 at 12:44 AM, Andrew Straw 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 again before
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
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
On Mon, Oct 25, 2010 at 4:09 PM, Daniel Hyams 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)...
JDH
---
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 wrote:
> On Mon, Oct 25, 2010 at 3:41 PM, Daniel Hyams wrote:
>
> > It doesn't really insist on it right? There
On Mon, Oct 25, 2010 at 3:41 PM, Daniel Hyams 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 it in the sour
On Mon, Oct 25, 2010 at 4:15 PM, Russell E. Owen wrote:
> In article <4cc22964.1050...@stsci.edu>,
> 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 fr
In article
,
John Hunter wrote:
> On Fri, Oct 22, 2010 at 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
> >
In article <4cc22964.1050...@stsci.edu>,
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 f
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 mysteri
On Fri, Oct 22, 2010 at 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 applicat
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 d
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 deletes the font cache).
That problem is allegedly fixed
26 matches
Mail list logo
