Skip to content

Fix qt warnings - #473

Merged
jenshnielsen merged 2 commits into
toolsforexperiments:masterfrom
jenshnielsen:fix_qt_warnings
Nov 2, 2026
Merged

jenshnielsen merged 2 commits into
toolsforexperiments:masterfrom
jenshnielsen:fix_qt_warnings

Conversation

@jenshnielsen

@jenshnielsen jenshnielsen commented Oct 5, 2026 •

Copy link
Copy Markdown
Collaborator

Clean up warnings raised during tests

@jenshnielsen
jenshnielsen marked this pull request as ready for review October 6, 2026 06:54
Comment thread plottr/node/fitter.py Resolved
Comment thread test/pytest/test_ddh5.py Resolved
Recent PySide6 emits a RuntimeWarning instead of raising TypeError when
disconnecting a slot that is not connected, so the try/except TypeError
guards no longer keep this quiet.

- PlotWithColorbar: connect colorbar.sigLevelsChanged to
  _colorScatterPoints once in __init__ (it is a no-op without a scatter
  plot) instead of disconnecting on every clearPlot.
- FittingGui: only connect the freshly built param-option signals when
  live update is on, rather than disconnecting never-connected signals.
  Also drive live update from QCheckBox.toggled(bool): with PySide6,
  stateChanged emits an int that never equals Qt.Checked, so checking
  the box disabled live update (and disconnected unconnected slots).
Forking the multi-threaded (Qt) pytest process raises "This process is
multi-threaded, use of fork() may lead to deadlocks in the child"
DeprecationWarning on Linux with Python >= 3.12. Use the spawn start
method on all platforms (Windows already used it).
@jenshnielsen
jenshnielsen merged commit 1bc512a into toolsforexperiments:master Nov 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants