# Custom Signal/Slots with PythonQt

**URL:** <https://discourse.slicer.org/t/custom-signal-slots-with-pythonqt/3278>\
**Category:** Development\
**Tags:** python, qt\
**Created:** [June 25, 2018, 1:38pm UTC](https://discourse.slicer.org/t/custom-signal-slots-with-pythonqt/3278 "2018-06-25T13:38:25Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [June 28, 2018, 2:54pm UTC](https://discourse.slicer.org/t/custom-signal-slots-with-pythonqt/3278/6 "2018-06-28T14:54:42Z")

</div>

> [@jcfr](#):
>
> That said, `QObject` is not available. We should probably update the version of PythonQt bundled in Slicer. It is currently based on [r455](https://sourceforge.net/p/pythonqt/code/455/).

@jcfr I looked through the commits after r455, and didn’t see anything that was obviously related… I wonder if something from CTK is shadowing/removing QObject, because it is [registered](https://github.com/commontk/PythonQt/blob/patched-8/generated_cpp_56/com_trolltech_qt_core/com_trolltech_qt_core_init.cpp#L109) the same way as many other classes which _are_ available under `PythonQt.QtCore` in the repl (e.g. `QMimeData`).

---

_[View the full topic](https://discourse.slicer.org/t/custom-signal-slots-with-pythonqt/3278)._
