matplotlib-devel Mailing List for matplotlib

On Sat, Feb 25, 2012 at 1:54 PM, Benjamin Root <ben...@ou...> wrote:
>
>> > I would be interested in accelerating the schedule. Since this is a
>> > bug-fix release and not a major release, we can presume the tree is
>> > pretty stable. How about we aim for an release candidate rc1 the
>> > week after next? Are there any issues or pull requests that should
>> > hold the release? If so, let's tag them with release-critical.
>> >
>> > After we get the bugfix out I'd like to gear up for a major python3
>> > release.
>> >
>> >
>> > The QT4 event handling bugs needs a qt expert on them. I tried looking
>> > into them and there is no obvious reason to me why they aren't working.
>>
>> Are you referring to 771, 707, and 525? 771 would appear to be the
>> most urgent.
>
>
> 711 and 707. Didn't even notice 525, but it is probably related to 707.
> If true, then 707 and 525 are likely focus issues (maybe window-manager
> dependent?). 711 definitely seem to be release blocking.
>
>
Hi Pierre, we are still having trouble with the close event in mpl figure
windows not being emitted. I see you posted on this subject in 2009 and
did some monkey patching to work around the problem for spyder
http://old.nabble.com/Qt4-backend%3A-critical-bug-with-PyQt4-v4.6%2B-td26205716.html
This was a while ago so I don't know if your suggestions are still
appropriate for recent pyqt and mpl. Would you have a minute to take a
look at this mpl issue
https://github.com/matplotlib/matplotlib/issues/711
and advise us on a fix?
Thanks,
JDH

On Saturday, February 25, 2012, Eric Firing wrote:
> On 02/25/2012 08:34 AM, Benjamin Root wrote:
> >
> >
> > On Saturday, February 25, 2012, John Hunter wrote:
> >
> >
> >
> > On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben...@ou...<javascript:;>
> > <javascript:_e({}, 'cvml', 'ben...@ou... <javascript:;>');>>
> wrote:
> >
> >
> >
> > On Thursday, February 23, 2012, RuiDC wrote:
> >
> >
> > Hi,
> > There's a number of bugs fixed that would be nice to have
> > without running
> > git versions.
> > Is there a release schedule for the next version?
> >
> >
> > There is not one in place right now. In about a month, I will
> > be starting up my new job, which I hope will allow me to devote
> > more time and effort to this project. There are a number of
> > features I have in mind to get added and there are many pull
> > requests that needs evaluating.
> >
> > Even if you are not a developer, members of this community can
> > still help us out by trying out pull requests and letting us
> > know if it works for them.
> >
> >
> >
> > I would be interested in accelerating the schedule. Since this is a
> > bug-fix release and not a major release, we can presume the tree is
> > pretty stable. How about we aim for an release candidate rc1 the
> > week after next? Are there any issues or pull requests that should
> > hold the release? If so, let's tag them with release-critical.
> >
> > After we get the bugfix out I'd like to gear up for a major python3
> > release.
> >
> >
> > The QT4 event handling bugs needs a qt expert on them. I tried looking
> > into them and there is no obvious reason to me why they aren't working.
>
> Are you referring to 771, 707, and 525? 771 would appear to be the
> most urgent.
711 and 707. Didn't even notice 525, but it is probably related to 707.
 If true, then 707 and 525 are likely focus issues (maybe window-manager
dependent?). 711 definitely seem to be release blocking.
Ben Root

On 02/25/2012 08:34 AM, Benjamin Root wrote:
>
>
> On Saturday, February 25, 2012, John Hunter wrote:
>
>
>
> On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben...@ou...
> <javascript:_e({}, 'cvml', 'ben...@ou...');>> wrote:
>
>
>
> On Thursday, February 23, 2012, RuiDC wrote:
>
>
> Hi,
> There's a number of bugs fixed that would be nice to have
> without running
> git versions.
> Is there a release schedule for the next version?
>
>
> There is not one in place right now. In about a month, I will
> be starting up my new job, which I hope will allow me to devote
> more time and effort to this project. There are a number of
> features I have in mind to get added and there are many pull
> requests that needs evaluating.
>
> Even if you are not a developer, members of this community can
> still help us out by trying out pull requests and letting us
> know if it works for them.
>
>
>
> I would be interested in accelerating the schedule. Since this is a
> bug-fix release and not a major release, we can presume the tree is
> pretty stable. How about we aim for an release candidate rc1 the
> week after next? Are there any issues or pull requests that should
> hold the release? If so, let's tag them with release-critical.
>
> After we get the bugfix out I'd like to gear up for a major python3
> release.
>
>
> The QT4 event handling bugs needs a qt expert on them. I tried looking
> into them and there is no obvious reason to me why they aren't working.
Are you referring to 771, 707, and 525? 771 would appear to be the 
most urgent.
>
> I would be amendable to a bug-fix release soon to hold everybody over
> for the next major release.
Agreed.
Eric
>
> Ben Root
>

Hi,
I will be on vacation with limited email from February 18-25, 2012.
Bonjour,
Je serai en conge du 18 au 25 fevrier, 2012.
Thanks,
David

On Saturday, February 25, 2012, John Hunter wrote:
>
>
> On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben...@ou...<javascript:_e({}, 'cvml', 'ben...@ou...');>
> > wrote:
>
>>
>>
>> On Thursday, February 23, 2012, RuiDC wrote:
>>
>>>
>>> Hi,
>>> There's a number of bugs fixed that would be nice to have without running
>>> git versions.
>>> Is there a release schedule for the next version?
>>
>>
>> There is not one in place right now. In about a month, I will be
>> starting up my new job, which I hope will allow me to devote more time and
>> effort to this project. There are a number of features I have in mind to
>> get added and there are many pull requests that needs evaluating.
>>
>> Even if you are not a developer, members of this community can still help
>> us out by trying out pull requests and letting us know if it works for them.
>>
>
>
> I would be interested in accelerating the schedule. Since this is a
> bug-fix release and not a major release, we can presume the tree is pretty
> stable. How about we aim for an release candidate rc1 the week after next?
> Are there any issues or pull requests that should hold the release? If
> so, let's tag them with release-critical.
>
> After we get the bugfix out I'd like to gear up for a major python3
> release.
>
The QT4 event handling bugs needs a qt expert on them. I tried looking into
them and there is no obvious reason to me why they aren't working.
I would be amendable to a bug-fix release soon to hold everybody over for
the next major release.
Ben Root

On Sat, Feb 25, 2012 at 8:34 AM, Benjamin Root <ben...@ou...> wrote:
>
>
> On Thursday, February 23, 2012, RuiDC wrote:
>
>>
>> Hi,
>> There's a number of bugs fixed that would be nice to have without running
>> git versions.
>> Is there a release schedule for the next version?
>
>
> There is not one in place right now. In about a month, I will be starting
> up my new job, which I hope will allow me to devote more time and effort to
> this project. There are a number of features I have in mind to get added
> and there are many pull requests that needs evaluating.
>
> Even if you are not a developer, members of this community can still help
> us out by trying out pull requests and letting us know if it works for them.
>
I would be interested in accelerating the schedule. Since this is a
bug-fix release and not a major release, we can presume the tree is pretty
stable. How about we aim for an release candidate rc1 the week after next?
 Are there any issues or pull requests that should hold the release? If
so, let's tag them with release-critical.
After we get the bugfix out I'd like to gear up for a major python3 release.

On Thursday, February 23, 2012, RuiDC wrote:
>
> Hi,
> There's a number of bugs fixed that would be nice to have without running
> git versions.
> Is there a release schedule for the next version?
There is not one in place right now. In about a month, I will be starting
up my new job, which I hope will allow me to devote more time and effort to
this project. There are a number of features I have in mind to get added
and there are many pull requests that needs evaluating.
Even if you are not a developer, members of this community can still help
us out by trying out pull requests and letting us know if it works for them.
Cheers!
Ben Root