[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] Strange abort with function inside custom type
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2017-03-22 21:17:55
Message-ID: D9198E00-0B33-43B7-BD44-0CE59FD654A3 () riverbankcomputing ! com
[Download RAW message or body]

On 22 Mar 2017, at 1:01 pm, Cody Scott <cody@perspexis.com> wrote:
> 
> FWIW this was working in PyQt<5.8
> 
> The function is only used in QML.

The bug is caused by the fix for another bug you reported (related to properties) \
which itself was caused by changes in Qt v5.8.0.

I think it is more important that properties work than the ability to define \
JavaScript functions.

Phil

> On Tue, Mar 21, 2017 at 7:21 PM, Phil Thompson <phil@riverbankcomputing.com> wrote:
> On 21 Mar 2017, at 3:42 pm, Cody Scott <cody@perspexis.com> wrote:
> > 
> > I have a custom type and if there is a function created inside the custom type \
> > there is a SIGSEGV 
> > https://gist.github.com/Siecje/ae3f033daca3cfb52d8060dde2a08b91
> > 
> > This is using PyQt5==5.8.1.1
> 
> This is a bug but I don't think it is fixable. Trying to integrate QML with \
> (dynamic) Python is never going to work as well as with (static) C++. PyQt does \
> it's best to fool QML into thinking it is talking to C++ but I think this is a step \
> too far. The QML implementation just keeps too much information under the covers. 
> Generally I'd recommend keeping the QML to a minimum - just use it to implement the \
> view and implement all model and controller code in Python. 
> Phil
> 

_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt


[prev in list] [next in list] [prev in thread] [next in thread]