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

List:       pykde
Subject:    Re: [PyQt] Bug in qpycore_PyObject_AsQString
From:       Phil Thompson <phil () riverbankcomputing ! com>
Date:       2015-09-19 11:48:06
Message-ID: EB9CF401-D88D-4C38-BF7E-7A48E07B51A9 () riverbankcomputing ! com
[Download RAW message or body]

On 19 Sep 2015, at 9:36 am, Kovid Goyal <kovid@kovidgoyal.net> wrote:
> 
> I saw the following assert in one of my programs:
> 
> python3: ../qpy/QtCore/qpycore_qstring.cpp:165: QString \
> qpycore_PyObject_AsQString(PyObject*): Assertion \
> `(((PyASCIIObject*)obj)->state.ready)' failed. 
> This will happen if a python string that is not "ready" is passed into a
> PyQt API (such strings can be created by C python extensions, notably
> sqlite). That function should call PyUnicode_READY (and check its return
> value). 
> 
> As a workaround, one can call str() on the string before passing it to
> PyQt.

Fixed in tonight's snapshots.

Thanks,
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]