On Sunday, November 27, 2016 6:22:48 PM CET Dmitry Shachnev wrote:
> Such code should not be run on module *import* time, it should be run
> when the spyder code is first *used*.
I completely agree with this.
Also, I second the opinion that segfaults when using Qt code without a
QApplication
And qt also does not produces exceptions, and that's by design.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
On Sun, Nov 27, 2016 at 06:22:52PM +, PICCA Frederic-Emmanuel wrote:
> > In other words: if you want to use Qt you *need* a QApplication instance.
> > That's Qt basics. Not using it is a bug.
>
> I understand,
>
> Nervertheless I think that the python binding should fail gracefully with
> an
> In other words: if you want to use Qt you *need* a QApplication instance.
> That's Qt basics. Not using it is a bug.
I understand,
Nervertheless I think that the python binding should fail gracefully with an
exception instead of segfaulting...
Cheers
In other words: if you want to use Qt you *need* a QApplication instance.
That's Qt basics. Not using it is a bug.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
Hi,
On Sun, Nov 27, 2016 at 03:16:36PM +, PICCA Frederic-Emmanuel wrote:
> > The QFontDatabase method will definitely not work properly without a
> > Q(Gui)Application instance.
>
> thanks for this analyze.
>
> so if I understand correctly, the problem is in the QFontDatabse method
> which
Hello Dmitry
> The QFontDatabase method will definitely not work properly without a
> Q(Gui)Application instance.
thanks for this analyze.
so if I understand correctly, the problem is in the QFontDatabse method which
should raise an exception instead of segfaulting.
right ?
so I should clone
Hi all, and sorry for the late response.
On Sat, Nov 19, 2016 at 11:48:51AM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> I'm CCing the pyqt5 maintainer and expert. Python is not my realm really.
The problem with python-spyder is that it tries to use Qt widgets without a
QApplication
On sábado, 19 de noviembre de 2016 14:02:27 ART PICCA Frederic-Emmanuel wrote:
> > From the original bug report (the only thing I had up to know):
> I attached my backtrace in the bug report. this is why we are speaking about
> different things;)
And you seem to be solving another bug and not
> From the original bug report (the only thing I had up to know):
I attached my backtrace in the bug report. this is why we are speaking about
different things;)
> Then if the gdb backtrace in the original bug report is to be trusted then
> you are indeed mixing Qt4 and Qt5. And you can expect
On sábado, 19 de noviembre de 2016 13:40:56 ART PICCA Frederic-Emmanuel wrote:
> > Hi Picca! Please next time you reassign a bug also CC the maintainer/team
> > that receives the bug, else we don't get this very text you wrote above
> > :-)
> sorry about that.
No problems, I've made the same
> Hi Picca! Please next time you reassign a bug also CC the maintainer/team that
> receives the bug, else we don't get this very text you wrote above :-)
sorry about that.
> No, this not seems to be a Qt bug, and even less a Qt5 bug, as the lib
> mentioned in the backtrace is from Qt4. By
reassign 844601 python-spyder 3.0.1+dfsg1-1
thanks
Hi Picca! Please next time you reassign a bug also CC the maintainer/team that
receives the bug, else we don't get this very text you wrote above :-)
On sábado, 19 de noviembre de 2016 12:40:25 ART picca wrote:
> Hello libqt5gui5 maintainer, I
Hello libqt5gui5 maintainer, I will reassign this bug to you since it seems
that the segfault is in your library.
It can be caused by a missued of your library but nevertheless it should not
segfault :).
Package: python-spyder
Version: 3.0.1+dfsg1-1
Severity: normal
Tags: upstream
Dear Maintainer,
We have tried the spyder package from unstable and we have found a
problem.
The steps to reproduce it are:
apt-get update
apt-get install -y python-spyder
export USER=
python -c "from
15 matches
Mail list logo
