Re: [Fwd: python-soappy: fpconst missing]

2006-07-21 Thread Manuel Metz
OK - thank you.

I have just submitted a bug report to the BTS.

Manuel

Pierre Habouzit wrote:
> Le ven 21 juillet 2006 13:31, Manuel Metz a écrit :
>> Sorry to bother you again. I have the feeling that the maintainer of
>> SOAPpy is not fixing bugs very quickly :-( I figured out a problem
>> with fpconst.py again (not yet reported the bug to debian bug
>> report).
>>
>> The version included in SOAPpy (0.6.0) does not work correctly on 64
>> Bit systems. G. R. Warnes has released an updated version:
>> http://mac.warnes.net/~warnes/files/fpconst-0.7.2.tar.gz
>> , also attached to this E-Mail.
>>
>> Could you please update the package.
>>
>> And again, sorry for bothering you.
>>
>> Manuel
> 
> well, I'd like to avoid doing that, I don't use python-soappy at all, 
> even does not know what it does. My two previous uploads were due to :
>  (1) transitionning the package to a new packaging standard,
>  (2) fixing a bug due to my previous upload (that you reported to me,
>  and you were right to do so).
> 
> But I'm not well placed to deal with a package I don't know well. I 
> forward your mail to the debian-python list, maybe someone will be 
> willing to check on that package, and ensure it's of release quality.
> 
> Also note that if the package is unusable, you should open a bug on the 
> BTS, with a high severity (if relevant). bugs of high severity *will* 
> be checked by developpers, presumably by some that know about that 
> package better than me.
> 
> Note that here, I'm convinced a new upstream has to be packaged asap, 
> but as said, not knowing the package, I don't know how stable the more 
> recent upstream releases are, and can't take such a decision.
> 
> Cheers,


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: [Fwd: python-soappy: fpconst missing]

2006-07-21 Thread Pierre Habouzit
Le ven 21 juillet 2006 13:31, Manuel Metz a écrit :
> Sorry to bother you again. I have the feeling that the maintainer of
> SOAPpy is not fixing bugs very quickly :-( I figured out a problem
> with fpconst.py again (not yet reported the bug to debian bug
> report).
>
> The version included in SOAPpy (0.6.0) does not work correctly on 64
> Bit systems. G. R. Warnes has released an updated version:
> http://mac.warnes.net/~warnes/files/fpconst-0.7.2.tar.gz
> , also attached to this E-Mail.
>
> Could you please update the package.
>
> And again, sorry for bothering you.
>
> Manuel

well, I'd like to avoid doing that, I don't use python-soappy at all, 
even does not know what it does. My two previous uploads were due to :
 (1) transitionning the package to a new packaging standard,
 (2) fixing a bug due to my previous upload (that you reported to me,
 and you were right to do so).

But I'm not well placed to deal with a package I don't know well. I 
forward your mail to the debian-python list, maybe someone will be 
willing to check on that package, and ensure it's of release quality.

Also note that if the package is unusable, you should open a bug on the 
BTS, with a high severity (if relevant). bugs of high severity *will* 
be checked by developpers, presumably by some that know about that 
package better than me.

Note that here, I'm convinced a new upstream has to be packaged asap, 
but as said, not knowing the package, I don't know how stable the more 
recent upstream releases are, and can't take such a decision.

Cheers,
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpq4fjTi3Akf.pgp
Description: PGP signature


Re: What GUI lib to choose: GTK, TK, WX, QT, other?

2006-07-21 Thread emilp



--On Monday, July 17, 2006 00:28:07 +0200 Josselin Mouette 
<[EMAIL PROTECTED]> wrote:



Le lundi 10 juillet 2006 à 14:37 +0200, Michal ?iha? a écrit :

I was in very similar situation three years ago. I decided to use
wxWidgets and now I thing about rewrite using something less
problematic (probably Gtk). Maybe I just hit too much corner cases,
but wxWidgets brought me too much pain and workarounds in my code.


FWIW, this is what happened to pyslsk (which was rewritten into
nicotine), so you're not the only one with issues in wxWidgets.
Furthermore, pygtk is quite portable nowadays.


Could you please share some more detailes about your problems
with wxWidgets?

I'm started to learn wxWidgets (actually wxPython) some time ago
as it seemed to be one of the better choices - reasonably easy
yet not too limiting, as well as cross platform.
 I didn't spend that much time investigating other options thoug,
and of course I'd rather not spend more time just find myself in
a dead end later...

// Emil