Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Eric Firing
On 04/11/2011 11:19 AM, Darren Dale wrote: > On Mon, Apr 11, 2011 at 3:40 PM, Michael Droettboom wrote: >> (Hmm... git doesn't use its own issue tracker for tracking its own >> issues... what does that say?) > > Brilliant, whatever they use allows uploading attachments. They are using this: http:

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Benjamin Root
On Mon, Apr 11, 2011 at 4:19 PM, Darren Dale wrote: > On Mon, Apr 11, 2011 at 3:40 PM, Michael Droettboom > wrote: > > (Hmm... git doesn't use its own issue tracker for tracking its own > > issues... what does that say? ) > > Brilliant, whatever they use allows uploading attachments. > > Maybe i

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Darren Dale
On Mon, Apr 11, 2011 at 3:40 PM, Michael Droettboom wrote: > (Hmm... git doesn't use its own issue tracker for tracking its own > issues... what does that say? ) Brilliant, whatever they use allows uploading attachments. ---

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Michael Droettboom
On 04/11/2011 03:51 PM, Eric Firing wrote: > On 04/11/2011 07:24 AM, Darren Dale 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 reevalua

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Eric Firing
On 04/11/2011 07:24 AM, Darren Dale 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: >

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Darren Dale
On Mon, Apr 11, 2011 at 3:02 PM, Paul Ivanov wrote: > 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

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Paul Ivanov
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:

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Darren Dale
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-ne

[matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Michael Droettboom
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 m

[matplotlib-devel] Fwd: Source of inaccuracies in the matplotlib library

2011-04-11 Thread Konrad Bartkowski
Ok, forwarding it to the matplotlib-devel list. Best wishes, Konrad (on behalf of our workgroup) Original Message Subject:Source of inaccuracies in the matplotlib library Date: Fri, 8 Apr 2011 18:12:47 +0200 From: Bartkowski, Konrad

Re: [matplotlib-devel] Backend for Pyside

2011-04-11 Thread Gerald Storer
Hi, I've submitted a pull request with backend changes that (should) let all currently supported versions of PyQt work along side PySide. I've tested with PyQt 4.8.3 and PySide 1.0.0. I haven't bothered chasing down old versions of PyQt as they seem elusive. Gerald. On 29/03/2011 3:25 AM, but