Hi,
1.0.3 packages are available for OS X.
I'll be going on vacation next week and my work project using PySide
will be winding down over the same period. It would be nice if the
PySide changes could be pulled into master before then
Thanks,
Gerald.
On 31/05/2011 5:10 PM, Gerald Storer
ait for next PySide release to
>> confirm your pyside patch works on MacOs.
>> Will test as soon as next pyside version is out and available on
>> macports. I do not have time nor will to test with the latest current
>> pyside head.
>>
>> Regards,
>>
>>
On 18/05/2011 5:14 AM, Eric Firing wrote:
> 3) We don't have to always push sets of changes from an original pull
> request to upstream; they can be consolidated using any of a variety of
> methods to form a new local feature branch with the same net effect but
> fewer commits (maybe only one), and
lable on
> macports. I do not have time nor will to test with the latest current
> pyside head.
>
> Regards,
>
> David
>
>
>
> Le 06/05/11 03:36, Gerald Storer a écrit :
>> Hi,
>> I was wondering if I could get a comment on this. Its been 4 weeks
>> si
Hi,
I was wondering if I could get a comment on this. Its been 4 weeks
since I submitted the original version and it has been more or less
production ready since Monday.
https://github.com/matplotlib/matplotlib/pull/80
Thanks,
Gerald.
On 11/04/2011 4:49 PM, Gerald Storer wrote:
> Hi,
>
03/2011 3:25 AM, butt...@gmail.com wrote:
> Looking forward, supporting the Python 3 compatible PyQt API is likely
> the way to go.
>
> Le , Gerald Storer a écrit :
> > On 28/03/2011 1:10 AM, Peter Butterworth wrote:
> >
> >
> > Wouldn't it be possible to us
Formlayout could probably be updated so it doesn't need the hacks but I
wanted to keep changes to a minimum.
Gerald.
On 17/03/2011 11:21 AM, Gerald Storer wrote:
On 01/18/2011 08:13 PM, Jed Ludlow wrote:
> Please forgive me if I'm raising a heretical question with this since I
&g
On 01/18/2011 08:13 PM, Jed Ludlow wrote:
> Please forgive me if I'm raising a heretical question with this since I
> understand the topic of competing Qt bindings for Python gets a little
> touchy in and of itself. Nonetheless, the elephant is in the room. I
> searched the archives and found only
