[Stackless] Still getting crashes with PySide
richard.m.tew at gmail.com
Thu Nov 22 19:14:44 CET 2012
No, PySide is considerably more crashy with Stackless involved. The
only crashes I get without it, as I use it now without Stackless as
Christian does, are reconcilable ones. PySide signals have a declared
type that are sent through them, send a different type and crash.
That sort of thing.
On Thu, Nov 22, 2012 at 10:16 PM, Kristján Valur Jónsson
<kristjan at ccpgames.com> wrote:
> So, it could be that Anselm's patch solved the last remaining (or last known, rather) issue of Stackless-related Pyside problems, and that the others are just regular PySide bugs that have nothing to do with Stackless...
> I started a patch to try to change at how we define the PyTypeObject in stackless, so that the extensions were hidden. That would make the extensions visible only to code that used them and allow everything else to work as expected... But it turned out to be complicated.
> Perhaps I will give it another shot, though.
>> -----Original Message-----
>> From: John Ehresman [mailto:jpe at wingware.com]
>> Sent: 20. nóvember 2012 15:12
>> To: Christian Tismer
>> Cc: The Stackless Python Mailing List; Kristján Valur Jónsson; Stephan Deibel
>> Subject: Re: [Stackless] Still getting crashes with PySide
>> On 11/20/12 9:09 AM, Christian Tismer wrote:
>> > Howdy,
>> > this seems to be an important one, because of PySide's popularity.
>> > While I'm not convinced that PySide is really bug-free... I have to
>> > ask the Wing guys about how stable it is meanwhile.
>> We've found more bugs than we wanted to while using PySide; I just posted
>> a description of one such bug on the pyside list and have filed reports of
>> others on the pyside bug tracker. We've been able to work around the bugs,
>> though doing so often requires thinking through how things work on the C++
>> side of things.
>> We're using the standard CPython 2.7 interpreter.
> Stackless mailing list
> Stackless at stackless.com
More information about the Stackless