On Mon, Mar 7, 2011 at 10:39 AM, Darren Dale wrote:
> On Mon, Mar 7, 2011 at 11:24 AM, Benjamin Root wrote:
> >
> >
> > On Mon, Mar 7, 2011 at 10:20 AM, Darren Dale wrote:
> >>
> >> On Mon, Mar 7, 2011 at 11:04 AM, Benjamin Root wrote:
> >> >
> >> >
> >> > On Fri, Mar 4, 2011 at 4:23 AM, Marti
On Mon, Mar 7, 2011 at 11:24 AM, Benjamin Root wrote:
>
>
> On Mon, Mar 7, 2011 at 10:20 AM, Darren Dale wrote:
>>
>> On Mon, Mar 7, 2011 at 11:04 AM, Benjamin Root wrote:
>> >
>> >
>> > On Fri, Mar 4, 2011 at 4:23 AM, Martin Teichmann
>> >
>> > wrote:
>> >>
>> >> Hi Ben, Hi list,
>> >>
>> >> >
On Mon, Mar 7, 2011 at 10:20 AM, Darren Dale wrote:
> On Mon, Mar 7, 2011 at 11:04 AM, Benjamin Root wrote:
> >
> >
> > On Fri, Mar 4, 2011 at 4:23 AM, Martin Teichmann <
> lkb.teichm...@gmail.com>
> > wrote:
> >>
> >> Hi Ben, Hi list,
> >>
> >> > Exactly. That's all I found too. Nothing indic
On Mon, Mar 7, 2011 at 11:04 AM, Benjamin Root wrote:
>
>
> On Fri, Mar 4, 2011 at 4:23 AM, Martin Teichmann
> wrote:
>>
>> Hi Ben, Hi list,
>>
>> > Exactly. That's all I found too. Nothing indicates that we need to
>> > change anything. We are throwing away the second part of the tuple
>> > w
On Fri, Mar 4, 2011 at 4:23 AM, Martin Teichmann wrote:
> Hi Ben, Hi list,
>
> > Exactly. That's all I found too. Nothing indicates that we need to
> > change anything. We are throwing away the second part of the tuple
> > which has the returned filter. The only reason I see for the new
> > fu
Hi Ben, Hi list,
> Exactly. That's all I found too. Nothing indicates that we need to
> change anything. We are throwing away the second part of the tuple
> which has the returned filter. The only reason I see for the new
> function is so the coder can get back the filter string, which we
> do
On Thursday, March 3, 2011, Darren Dale wrote:
> On Thu, Mar 3, 2011 at 10:22 AM, Benjamin Root wrote:
>> Just for completeness, I wanted to include a link to some sort of reference
>> indicating a need to change the function. I can not find any documentation
>> that says that we need to change
On Thu, Mar 3, 2011 at 10:22 AM, Benjamin Root wrote:
> Just for completeness, I wanted to include a link to some sort of reference
> indicating a need to change the function. I can not find any documentation
> that says that we need to change from getSaveFileName() to
> getSaveFileNameAndFilter(
On Thu, Mar 3, 2011 at 3:15 AM, Martin Teichmann wrote:
> Hi Benjamin, Hi List,
>
> sorry for the backwards patch, here the forward one:
>
>
> --- backend_qt4_orig.py 2011-03-02 16:16:38.257797767 +0100
> +++ backend_qt4.py
On Thu, Mar 3, 2011 at 9:36 AM, Benjamin Root wrote:
> As for the sourceforge/github confusion, we are currently in a transition
> phase. Our repository is now hosted on github, but the official website and
> trackers are still sourceforge. Sorry for any confusion there. The
> (un)official new
On Thu, Mar 3, 2011 at 3:15 AM, Martin Teichmann wrote:
> Hi Benjamin, Hi List,
>
> sorry for the backwards patch, here the forward one:
>
>
> --- backend_qt4_orig.py 2011-03-02 16:16:38.257797767 +0100
> +++ backend_qt4.py
Hi Benjamin, Hi List,
sorry for the backwards patch, here the forward one:
--- backend_qt4_orig.py 2011-03-02 16:16:38.257797767 +0100
+++ backend_qt4.py 2011-03-02 16:17:19.526831397 +0100
@@ -395,8 +395,9 @@
On Wed, Mar 2, 2011 at 4:26 PM, Darren Dale wrote:
> On Wed, Mar 2, 2011 at 10:26 AM, Martin Teichmann
> wrote:
>> Hi list,
>>
>> I'm using matplotlib as a library, in a program using the
>> new APIs of PyQt4, which will be the normal APIs for
>> Python 3. Unfortunately, the matplotlib Qt4 backen
On Wed, Mar 2, 2011 at 10:26 AM, Martin Teichmann
wrote:
> Hi list,
>
> I'm using matplotlib as a library, in a program using the
> new APIs of PyQt4, which will be the normal APIs for
> Python 3. Unfortunately, the matplotlib Qt4 backend is
> not compatible with this new API.
This really doesn't
On Wed, Mar 2, 2011 at 9:26 AM, Martin Teichmann wrote:
> Hi list,
>
> I'm using matplotlib as a library, in a program using the
> new APIs of PyQt4, which will be the normal APIs for
> Python 3. Unfortunately, the matplotlib Qt4 backend is
> not compatible with this new API.
>
> The problems are
Hi list,
I'm using matplotlib as a library, in a program using the
new APIs of PyQt4, which will be the normal APIs for
Python 3. Unfortunately, the matplotlib Qt4 backend is
not compatible with this new API.
The problems are easy to fix: first QFileDialog.getSaveFileName
has changed, and is to b
16 matches
Mail list logo
