On Mon, Jan 17, 2011 at 5:50 PM, João Ventura <[email protected]>wrote:
> Hello Didier Raboud, > > Em 17-01-2011 21:32, Didier 'OdyX' Raboud escreveu: > > (I am the PySide PPA maintainer as well as the Debian and Ubuntu > maintainer > > of the PySide stack) > > > > João Ventura wrote: > >> Hello, > >> > >> the same thing happened to me, and i can't seem to work it out. I'm > >> using ubuntu 10.10 and pyside 1.0~beta1 (because the ppa doesn't seem > >> to update to beta3), and since today the error occurs on "import > >> PySide". > > Hi João, > > > > "the ppa doesn't seem to update" sounds very funny: "updating to ~beta3" > is > > not automagical: it implies a certain time of work and compilation. As I > > don't update the PPA with a possibly broken PySide, it takes at least 2 > > compilations of it before the actual release and some actual packaging > work. > > And I am doing this for 3 Ubuntu releases as well as for Debian. > > > > I'm doing this on my free time, which happens to be limited these days. > it was my bad choice of words. What i meant to say is that the ppa is > not updated to beta3 so i'm still using beta1 - that i use the > binaries from the ppa and not a home-compiled version. Not criticizing > the maintainer, far from it. My goal is just to try to help narrowing > the error to a specific version. > I know that it takes a lot of personal time, and i'm one of the people > who should be thankful to you (and i am, of course) as i use the > binaries you produce. > > >> Last friday, it all worked fine, so it has to do with any ubuntu > >> update i have done this weekend. > > It's not a Ubuntu update you did; you updated from a PPA, which is far > from > > being the same: a PPA is not part of the Ubuntu distribution. AFAICS the > > PySide version from Ubuntu Maverick works correctly. > Probabily, i must have updated things from pyside between my regular > ubuntu updates, and that led me to think that it was another library > (outside pyside) that was breaking something in PySide. As i said, > friday everything worked, today "import PySide" gives that error. The > error is from the PySide ppa update? Is there any possibility of > installing a previous version of things on the ppa? > > >> When will this be ok? I've just lost today a day of work on this.. > > Feel free to contract me to do the job faster; otherwise I'll continue to > do > > this on a best-effort basis, during my free time. > Of course. Again, not refering to ppa's or anything. The reality is > that i've scheduled a free day today for working with PySide, and > could not do it. Had to install Ubuntu again, configure everything, > etc. It took me all day. > > >> Btw, when will ubuntu ppa be updated to beta3? > > Before the end of the week, hopefully. > > > >> Thanks, > >> João Ventura > > Although my mail might sound rude, I really feel offended by the tone of > > yours. But I acknowledge that the process is not perfect: it might be > > possible to wait on PySide being ready to upload before uploading > Shiboken, > > but it's more complicated for me. > It is not my purpose to offend anyone, even more when they are working > on their spare times. I've just registered today in the mailing list > to address this problem, and i have not consulted any more threads > than this one, so i don't know about what is happening and how things > work inside. I'm not accusing or pointing my fingers to anyone, and it > was not with that tone that i've wrote this email (or it was not that > intention, of course). > > > And again, please note that I (as the PPA maintainer) am not reponsible > for > > disappearing symbols: this is a responsability of PySide upstream and > > altough I am mildly annoyed by this fact, this is also normal during > "beta" > > releases, which you still use despite this "beta" state. > > > > So please refrain from accusing (me in that case) people for work days > lost > > (in particular when you are using beta free software): it only helps in > > taking away people's motivation. > Again, it was not my intention to accuse anyone, just refered to ppa > to contextualize my setup. It's my first post here, my firsts visits > to this mailing list, so i'm not in the position to accuse anyone. I > don't know anyone around here, no names are familiar to me, and that > is not absolutelly my way of working. I don't even know if the problem > is with the ppa, and never thought the ppa could have something to do > with it. > > > Respectfully, > > > > OdyX > I sure hope you don't fell demotivated. You are doing a terrific good > job by maintaining the ppa and a lot of people seems to use the fruits > of your work, and that is extremelly positive. > > > João Ventura > _______________________________________________ > PySide mailing list > [email protected] > http://lists.openbossa.org/listinfo/pyside > I used the buildscript to install PySide in a sandbox and the error went away. However I have noticed that emitting a clicked signal for a QPushButton from a different thread doesn't have call the connected slot. It works fine when manually clicking the button and also when I call the click() function. It works fine on the old installation too. However button.clicked.emit() does not do anything. Any suggestions?
_______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
