Issue #2239 resolved

native Qt signal is not callable on startup

Tim Delaney
created an issue

This appears to be a regression or another case of issue #2193, although my Qt and PyQt versions are different. Linux Mint 10.

After upgrading to tip in the stable branch, the following occurs when starting the workbench and every time the tree is updated:

** Mercurial version (2.3.2).  TortoiseHg version (2.5.1+25-d1be42dde1ba)
** Command: 
** CWD: /home/tim/hg/storageconsole
** Encoding: UTF-8
** Extensions loaded: relink, children, churn, graphlog, rebase, purge, highlight, fetch, collapse, prompt, hggit, hgsubversion, remotebranches, versions, punchcard, extdiff
** Python version: 2.6.6 (r266:84292, Sep 15 2010, 16:22:56) [GCC 4.4.5]
** Qt-4.7.0 PyQt-4.7.4
TypeError: native Qt signal is not callable

Comments (2)

  1. Yuya Nishihara

    repomodel: use old-style signal for QTimer.singleShot connection (fixes #2239)

    PyQt 4.7.4 does not support new-style signal-signal connection for this case.

    v4.7.5 31st August 2010 - A signal defined with pyqtSignal() can now be used with methods that make an internal call to QObject::connect(), e.g. QTimer.singleShot().

    Also note that:

    • QTimer.singleShot(0, lambda: self.filled.emit()) confuses lifetime of QObject (refs #1267)
    • QTimer.singleShot(0, self.filled.emit) segfaults if self has been destroyed

    → <<cset fdde19e206c6>>

  2. Log in to comment