PythonQwt 0.15.0__tar.gz → 0.16.0__tar.gz

{pythonqwt-0.15.0/PythonQwt.egg-info → pythonqwt-0.16.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PythonQwt
-Version: 0.15.0
+Version: 0.16.0
 Summary: Qt plotting widgets for Python
 Author-email: Pierre Raybaut <pierre.raybaut@gmail.com>
 License: PythonQwt License Agreement
@@ -666,12 +666,11 @@ License: PythonQwt License Agreement
 Project-URL: Homepage, https://github.com/PlotPyStack/PythonQwt/
 Project-URL: Documentation, https://PythonQwt.readthedocs.io/en/latest/
 Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
 Classifier: Topic :: Scientific/Engineering :: Visualization
 Classifier: Topic :: Software Development :: Widget Sets
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: Topic :: Utilities
-Classifier: Topic :: Scientific/Engineering
-Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
 Classifier: Topic :: Software Development :: User Interfaces
 Classifier: Operating System :: MacOS
 Classifier: Operating System :: Microsoft :: Windows
@@ -683,15 +682,18 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Requires-Python: <4,>=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: NumPy>=1.19
+Requires-Dist: NumPy>=1.21
 Requires-Dist: QtPy>=1.9
 Provides-Extra: dev
+Requires-Dist: build; extra == "dev"
 Requires-Dist: ruff; extra == "dev"
 Requires-Dist: pylint; extra == "dev"
 Requires-Dist: Coverage; extra == "dev"
+Requires-Dist: pre-commit; extra == "dev"
 Provides-Extra: doc
 Requires-Dist: PyQt5; extra == "doc"
 Requires-Dist: sphinx>6; extra == "doc"
@@ -760,7 +762,7 @@ tests.run()
 or from the command line:
 
 ```bash
-PythonQwt
+PythonQwt-tests
 ```
 
 Tests may also be executed in unattended mode:
@@ -773,9 +775,9 @@ PythonQwt-tests --mode unattended
 
 The `qwt` package is a pure Python implementation of `Qwt` C++ library with the following limitations.
 
-The following `Qwt` classes won't be reimplemented in `qwt` because more powerful features already exist in `guiqwt`: `QwtPlotZoomer`, `QwtCounter`, `QwtEventPattern`, `QwtPicker`, `QwtPlotPicker`.
+The following `Qwt` classes won't be reimplemented in `qwt` because more powerful features already exist in `PlotPy`: `QwtPlotZoomer`, `QwtCounter`, `QwtEventPattern`, `QwtPicker`, `QwtPlotPicker`.
 
-Only the following plot items are currently implemented in `qwt` (the only plot items needed by `guiqwt`): `QwtPlotItem` (base class), `QwtPlotItem`, `QwtPlotMarker`, `QwtPlotSeriesItem` and `QwtPlotCurve`.
+Only the following plot items are currently implemented in `qwt` (the only plot items needed by `PlotPy`): `QwtPlotItem` (base class), `QwtPlotGrid`, `QwtPlotMarker`, `QwtPlotSeriesItem` and `QwtPlotCurve`.
 
 See "Overview" section in [documentation](https://pythonqwt.readthedocs.io/en/latest/) for more details on API limitations when comparing to Qwt.
 
@@ -798,14 +800,14 @@ Compatibility table:
 
 | PythonQwt version | PyQt5 | PyQt6 | PySide2 | PySide6 |
 |-------------------|-------|-------|---------|---------|
-| 0.16 and earlier  | ✅    | ⚠️    | ❌     | ⚠️      |
+| 0.15 and earlier  | ✅    | ⚠️    | ❌     | ⚠️      |
 | Latest            | ✅    | ✅    | ❌     | ✅      |
 
 ### Requirements
 
 - Python >=3.9
-- QtPy >= 1.3 (and a Python-to-Qt binding library, see above)
-- NumPy >= 1.5
+- QtPy >= 1.9 (and a Python-to-Qt binding library, see above)
+- NumPy >= 1.21
 
 ### Optional dependencies
 
@@ -814,12 +816,22 @@ Compatibility table:
 
 ### Installation
 
+From PyPI:
+
+```bash
+pip install PythonQwt
+```
+
 From the source package:
 
 ```bash
 python -m build
 ```
 
+## Performance investigation
+
+Tooling for performance benchmarks, profiling and visual-regression checks across PyQt5/PyQt6/PySide6 lives in [`scripts/`](scripts/README.md). See [`doc/issue93_optimization_summary.md`](doc/issue93_optimization_summary.md) for a worked example.
+
 ## Copyrights
 
 ### Main code base

{pythonqwt-0.15.0 → pythonqwt-0.16.0/PythonQwt.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PythonQwt
-Version: 0.15.0
+Version: 0.16.0
 Summary: Qt plotting widgets for Python
 Author-email: Pierre Raybaut <pierre.raybaut@gmail.com>
 License: PythonQwt License Agreement
@@ -666,12 +666,11 @@ License: PythonQwt License Agreement
 Project-URL: Homepage, https://github.com/PlotPyStack/PythonQwt/
 Project-URL: Documentation, https://PythonQwt.readthedocs.io/en/latest/
 Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
 Classifier: Topic :: Scientific/Engineering :: Visualization
 Classifier: Topic :: Software Development :: Widget Sets
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: Topic :: Utilities
-Classifier: Topic :: Scientific/Engineering
-Classifier: Topic :: Scientific/Engineering :: Human Machine Interfaces
 Classifier: Topic :: Software Development :: User Interfaces
 Classifier: Operating System :: MacOS
 Classifier: Operating System :: Microsoft :: Windows
@@ -683,15 +682,18 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Requires-Python: <4,>=3.9
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: NumPy>=1.19
+Requires-Dist: NumPy>=1.21
 Requires-Dist: QtPy>=1.9
 Provides-Extra: dev
+Requires-Dist: build; extra == "dev"
 Requires-Dist: ruff; extra == "dev"
 Requires-Dist: pylint; extra == "dev"
 Requires-Dist: Coverage; extra == "dev"
+Requires-Dist: pre-commit; extra == "dev"
 Provides-Extra: doc
 Requires-Dist: PyQt5; extra == "doc"
 Requires-Dist: sphinx>6; extra == "doc"
@@ -760,7 +762,7 @@ tests.run()
 or from the command line:
 
 ```bash
-PythonQwt
+PythonQwt-tests
 ```
 
 Tests may also be executed in unattended mode:
@@ -773,9 +775,9 @@ PythonQwt-tests --mode unattended
 
 The `qwt` package is a pure Python implementation of `Qwt` C++ library with the following limitations.
 
-The following `Qwt` classes won't be reimplemented in `qwt` because more powerful features already exist in `guiqwt`: `QwtPlotZoomer`, `QwtCounter`, `QwtEventPattern`, `QwtPicker`, `QwtPlotPicker`.
+The following `Qwt` classes won't be reimplemented in `qwt` because more powerful features already exist in `PlotPy`: `QwtPlotZoomer`, `QwtCounter`, `QwtEventPattern`, `QwtPicker`, `QwtPlotPicker`.
 
-Only the following plot items are currently implemented in `qwt` (the only plot items needed by `guiqwt`): `QwtPlotItem` (base class), `QwtPlotItem`, `QwtPlotMarker`, `QwtPlotSeriesItem` and `QwtPlotCurve`.
+Only the following plot items are currently implemented in `qwt` (the only plot items needed by `PlotPy`): `QwtPlotItem` (base class), `QwtPlotGrid`, `QwtPlotMarker`, `QwtPlotSeriesItem` and `QwtPlotCurve`.
 
 See "Overview" section in [documentation](https://pythonqwt.readthedocs.io/en/latest/) for more details on API limitations when comparing to Qwt.
 
@@ -798,14 +800,14 @@ Compatibility table:
 
 | PythonQwt version | PyQt5 | PyQt6 | PySide2 | PySide6 |
 |-------------------|-------|-------|---------|---------|
-| 0.16 and earlier  | ✅    | ⚠️    | ❌     | ⚠️      |
+| 0.15 and earlier  | ✅    | ⚠️    | ❌     | ⚠️      |
 | Latest            | ✅    | ✅    | ❌     | ✅      |
 
 ### Requirements
 
 - Python >=3.9
-- QtPy >= 1.3 (and a Python-to-Qt binding library, see above)
-- NumPy >= 1.5
+- QtPy >= 1.9 (and a Python-to-Qt binding library, see above)
+- NumPy >= 1.21
 
 ### Optional dependencies
 
@@ -814,12 +816,22 @@ Compatibility table:
 
 ### Installation
 
+From PyPI:
+
+```bash
+pip install PythonQwt
+```
+
 From the source package:
 
 ```bash
 python -m build
 ```
 
+## Performance investigation
+
+Tooling for performance benchmarks, profiling and visual-regression checks across PyQt5/PyQt6/PySide6 lives in [`scripts/`](scripts/README.md). See [`doc/issue93_optimization_summary.md`](doc/issue93_optimization_summary.md) for a worked example.
+
 ## Copyrights
 
 ### Main code base

{pythonqwt-0.15.0 → pythonqwt-0.16.0}/PythonQwt.egg-info/SOURCES.txt

@@ -12,9 +12,9 @@ PythonQwt.egg-info/top_level.txt
 doc/conf.py
 doc/index.rst
 doc/installation.rst
+doc/issue93_optimization_summary.md
 doc/overview.rst
 doc/plot_example.py
-doc/requirements.txt
 doc/symbol_path_example.py
 doc/_static/PythonQwt_logo.png
 doc/_static/QwtPlot_example.png

{pythonqwt-0.15.0 → pythonqwt-0.16.0}/PythonQwt.egg-info/requires.txt

@@ -1,10 +1,12 @@
-NumPy>=1.19
+NumPy>=1.21
 QtPy>=1.9
 
 [dev]
+build
 ruff
 pylint
 Coverage
+pre-commit
 
 [doc]
 PyQt5

{pythonqwt-0.15.0 → pythonqwt-0.16.0}/README.md

@@ -57,7 +57,7 @@ tests.run()
 or from the command line:
 
 ```bash
-PythonQwt
+PythonQwt-tests
 ```
 
 Tests may also be executed in unattended mode:
@@ -70,9 +70,9 @@ PythonQwt-tests --mode unattended
 
 The `qwt` package is a pure Python implementation of `Qwt` C++ library with the following limitations.
 
-The following `Qwt` classes won't be reimplemented in `qwt` because more powerful features already exist in `guiqwt`: `QwtPlotZoomer`, `QwtCounter`, `QwtEventPattern`, `QwtPicker`, `QwtPlotPicker`.
+The following `Qwt` classes won't be reimplemented in `qwt` because more powerful features already exist in `PlotPy`: `QwtPlotZoomer`, `QwtCounter`, `QwtEventPattern`, `QwtPicker`, `QwtPlotPicker`.
 
-Only the following plot items are currently implemented in `qwt` (the only plot items needed by `guiqwt`): `QwtPlotItem` (base class), `QwtPlotItem`, `QwtPlotMarker`, `QwtPlotSeriesItem` and `QwtPlotCurve`.
+Only the following plot items are currently implemented in `qwt` (the only plot items needed by `PlotPy`): `QwtPlotItem` (base class), `QwtPlotGrid`, `QwtPlotMarker`, `QwtPlotSeriesItem` and `QwtPlotCurve`.
 
 See "Overview" section in [documentation](https://pythonqwt.readthedocs.io/en/latest/) for more details on API limitations when comparing to Qwt.
 
@@ -95,14 +95,14 @@ Compatibility table:
 
 | PythonQwt version | PyQt5 | PyQt6 | PySide2 | PySide6 |
 |-------------------|-------|-------|---------|---------|
-| 0.16 and earlier  | ✅    | ⚠️    | ❌     | ⚠️      |
+| 0.15 and earlier  | ✅    | ⚠️    | ❌     | ⚠️      |
 | Latest            | ✅    | ✅    | ❌     | ✅      |
 
 ### Requirements
 
 - Python >=3.9
-- QtPy >= 1.3 (and a Python-to-Qt binding library, see above)
-- NumPy >= 1.5
+- QtPy >= 1.9 (and a Python-to-Qt binding library, see above)
+- NumPy >= 1.21
 
 ### Optional dependencies
 
@@ -111,12 +111,22 @@ Compatibility table:
 
 ### Installation
 
+From PyPI:
+
+```bash
+pip install PythonQwt
+```
+
 From the source package:
 
 ```bash
 python -m build
 ```
 
+## Performance investigation
+
+Tooling for performance benchmarks, profiling and visual-regression checks across PyQt5/PyQt6/PySide6 lives in [`scripts/`](scripts/README.md). See [`doc/issue93_optimization_summary.md`](doc/issue93_optimization_summary.md) for a worked example.
+
 ## Copyrights
 
 ### Main code base

{pythonqwt-0.15.0 → pythonqwt-0.16.0}/doc/conf.py

@@ -101,7 +101,12 @@ autodoc_member_order = "bysource"
 
 # The theme to use for HTML and HTML Help pages.  Major themes that come with
 # Sphinx are currently 'default' and 'sphinxdoc'.
-html_theme = "default"
+try:
+    import python_docs_theme  # noqa: F401
+
+    html_theme = "python_docs_theme"
+except ImportError:
+    html_theme = "default"
 
 # Theme options are theme-specific and customize the look and feel of a theme
 # further.  For a list of options available for each theme, see the

{pythonqwt-0.15.0 → pythonqwt-0.16.0}/doc/examples/index.rst

@@ -6,19 +6,19 @@ Examples
 The test launcher
 -----------------
 
-A lot of examples are available in the ``qwt.test`` module ::
+A lot of examples are available in the ``qwt.tests`` module ::
 
     from qwt import tests
     tests.run()
 
-The two lines above execute the ``PythonQwt`` test launcher:
+The two lines above execute the ``PythonQwt-tests`` test launcher:
 
 .. image:: /../qwt/tests/data/testlauncher.png
 
-GUI-based test launcher can be executed from the command line thanks to the 
-``PythonQwt`` test script.
+GUI-based test launcher can be executed from the command line thanks to the
+``PythonQwt-tests`` test script.
 
-Unit tests may be executed from the commande line thanks to the console-based script 
+Unit tests may be executed from the command line thanks to the console-based script
 ``PythonQwt-tests``: ``PythonQwt-tests --mode unattended``.
 
 Tests
@@ -26,11 +26,11 @@ Tests
 
 
 
-Here are some examples from the `qwt.test` module:
+Here are some examples from the `qwt.tests` module:
 
 .. toctree::
     :maxdepth: 2
-    
+
     bodedemo
     cartesian
     cpudemo

{pythonqwt-0.15.0 → pythonqwt-0.16.0}/doc/installation.rst

@@ -15,6 +15,10 @@ Requirements:
 Installation
 ------------
 
+From PyPI:
+
+    `pip install PythonQwt`
+
 From the source package:
 
     `python -m build`

pythonqwt-0.16.0/doc/issue93_optimization_summary.md

@@ -0,0 +1,284 @@
+# Issue #93 — Performance degradation with Qt6: optimization summary
+
+This document summarises the work done on the `fix/93-performance-degradation-with-qt6` branch to investigate and close the Qt5↔Qt6 performance gap reported in [issue #93](https://github.com/PlotPyStack/PythonQwt/issues/93). It walks through each optimization phase, the diagnostic method used, the change applied, and the measured impact.
+
+All numbers below were collected on the same Windows 11 machine, Python 3.11.9, with three sibling virtual environments (`.venvs/pyqt5`, `.venvs/pyqt6`, `.venvs/pyside6`), each pinning a single Qt binding (PyQt5 5.15.11 / Qt 5.15.2, PyQt6 6.11.0 / Qt 6.11.0, PySide6 6.11.0 / Qt 6.11.0).
+
+Two benchmarks were used throughout:
+
+- **`qwt/tests/test_loadtest.py`** — the PythonQwt micro load test (raw QwtPlot widgets, no PlotPy). Driven by `scripts/bench_qt.ps1`. Reports `Average elapsed time: <ms> ms` per binding.
+- **PlotPy `test_loadtest`** — `plotpy/tests/benchmarks/test_loadtest.py`, the test cited in the original GitHub issue. Driven by `scripts/bench_plotpy_loadtest.py` (60 plot widgets, 3 runs).
+
+## Baseline (master, commit `1ab70cd`)
+
+| Benchmark | PyQt5 | PyQt6 | PySide6 |
+|---|---:|---:|---:|
+| PythonQwt `test_loadtest` (avg of 5) | ~1 900 ms | ~2 300 ms | ~2 900 ms |
+| PlotPy `test_loadtest`, 60 plots (avg of 3) | 25 134 ms | 42 202 ms | 53 160 ms |
+
+Headline gap on PlotPy: **PyQt6 ≈ +68 % slower than PyQt5**, **PySide6 ≈ +111 % slower than PyQt5**.
+
+The cProfile traces taken on master pointed at four hot families of code paths inside PythonQwt:
+
+1. `QwtScaleMap.transform()` — called on every coordinate transformed.
+2. `QwtScaleDiv.contains()` and `QwtScaleEngine.contains()/strip()` — called on every tick label candidate.
+3. `QwtAbstractScaleDraw.labelRect()` and helpers — called on every drawn tick.
+4. `QwtText` / `QwtPlainTextEngine` text-size and text-margin computations — called on every tick label and every plot title.
+
+All four are amortised over thousands of calls per plot, and all four are sensitive to per-call Python overhead (attribute lookups, QObject machinery, redundant Qt round-trips). That is precisely the kind of overhead that the Qt6 bindings (especially PySide6) make more expensive than Qt5, which explains why a regression that is barely visible on Qt5 becomes a 2× slowdown on Qt6.
+
+## Phase 1 — cProfile-driven optimizations (commit `ef793e1`)
+
+**Method.** `scripts/profile_loadtest.py` runs the PythonQwt load test under `cProfile` and dumps a sorted-by-cumulative-time stats file. Diff between PyQt5 and PySide6 traces highlighted the four families above.
+
+**Changes.**
+
+- **`qwt/scale_map.py`** — inlined the scalar fast path in `QwtScaleMap.transform()` (avoid the array branch and a method dispatch when the input is a plain Python `float`).
+- **`qwt/scale_div.py`** — rewrote `QwtScaleDiv.contains()` as a direct comparison against the cached lower/upper bounds, instead of going through `QwtInterval`.
+- **`qwt/scale_engine.py`** — `QwtScaleEngine.contains()` and `QwtScaleEngine.strip()` similarly bypass `QwtInterval` round-trips for the common case.
+- **`qwt/scale_draw.py`** — replaced the per-call alignment branching in `labelRect()`/`labelPosition()` with module-level constants (`_ALIGN_BOTTOM`, `_ALIGN_TOP`, `_ALIGN_LEFT`, `_ALIGN_RIGHT`); added a rotation==0 fast path in `labelRect()`; cached the axis `orientation` once in `setAlignment()` instead of recomputing it on every call.
+- **`qwt/text.py`** — first round of cleanups around `QwtText.textSize()` and `QwtPlainTextEngine.textMargins()`, plus a per-engine "last seen font id" fast path that skips the `QFontMetricsF` rebuild when the same `QFont` instance is reused (which is the dominant case during a single plot repaint).
+
+**Results after phase 1** (PythonQwt micro `test_loadtest`, 5 runs each):
+
+| Binding | Before | After phase 1 | Speedup |
+|---|---:|---:|---:|
+| PyQt5 | ~1 900 ms | ~620 ms | ×3.0 |
+| PyQt6 | ~2 300 ms | ~780 ms | ×2.9 |
+| PySide6 | ~2 900 ms | ~960 ms | ×3.0 |
+
+Phase 1 closed most of the absolute slowdown but did not change the *relative* Qt5↔Qt6 gap — all three bindings benefited roughly equally, because the optimizations attacked Python-side overhead that scales with call count regardless of binding.
+
+## Phase 2 — line-profiler-driven optimizations (commit `27a0e17`)
+
+**Method.** `scripts/lineprofile_loadtest.py` instruments the surviving hot functions with `line_profiler` (`@profile`) and re-runs the load test. The line-by-line traces revealed two new dominant costs that did not show up clearly in cProfile:
+
+1. The `QObject` base class on `QwtText_PrivateData` and on the `_PrivateData` classes inside `qwt/scale_draw.py`. Every instantiation went through Qt's meta-object system, which is dramatically more expensive on PyQt6 / PySide6 than on PyQt5.
+2. Repeated calls to `QFont.key()` from within `QwtText.textSize()`, `QwtText.effectiveAscent()` and `QwtPlainTextEngine.textMargins()`. Each call serialises the full font descriptor; the same descriptor is hit thousands of times during a single load test because the same default font instance is reused.
+
+**Changes.**
+
+- **`qwt/text.py`** — `QwtText_PrivateData` is now a plain `object` subclass with `__slots__`; no QObject. Added a process-wide `_FONT_KEY_CACHE` keyed by `id(font)` that memoizes `font.key()` (with a hard cap of 1024 entries to avoid unbounded growth). Helper `font_key_cached()` is used by `effectiveAscent`, `QwtPlainTextEngine.textMargins`, and `QwtText.textSize`.
+- **`qwt/scale_draw.py`** — the various `_PrivateData` containers also drop `QObject` and use `__slots__`.
+
+**Results after phase 2** (PythonQwt micro `test_loadtest`, 5 runs each):
+
+| Binding | Before phase 2 | After phase 2 | Speedup vs phase 1 | Speedup vs master |
+|---|---:|---:|---:|---:|
+| PyQt5 | ~620 ms | ~445 ms | ×1.4 | ×4.3 |
+| PyQt6 | ~780 ms | ~480 ms | ×1.6 | ×4.8 |
+| PySide6 | ~960 ms | ~600 ms | ×1.6 | ×4.8 |
+
+Phase 2 finally closed the *relative* gap as well: Qt6 bindings benefit more than Qt5 from removing QObject inheritance and `font.key()` calls, because the per-call overhead they save is binding-cost-dominated.
+
+## Phase 3 — screenshot regression analysis
+
+**Method.** Two new helpers were added in `scripts/`:
+
+- **`capture_screenshots.py`** — runs each of the 22 PythonQwt visual tests in a subprocess with `PYTHONQWT_TAKE_SCREENSHOTS=1` and copies the resulting PNGs into `shots/<branch>/<binding>/`.
+- **`diff_screenshots.py`** — pixel-compares two screenshot folders (Pillow + NumPy) and emits a markdown table with `IDENTICAL` / `EQUAL_PIXELS` / `DIFFER` status, plus the count and magnitude of differing pixels.
+
+A full matrix was captured (master × 3 bindings, fix × 3 bindings, plus self-compare baselines master×master and fix×fix to filter out flaky tests that have inherently random or time-stamped output).
+
+**Findings.**
+
+- **PyQt6 and PySide6**: zero new deterministic differences vs master. Every diff that appeared was already present in the master self-compare baseline (the 6 tests `test_cpudemo`, `test_curvebenchmark1/2`, `test_data`, `test_loadtest`, `test_mapdemo`, all of which use random data or timestamps).
+- **PyQt5**: 6 *new* deterministic, sub-perceptual differences appeared, in `test_backingstore`, `test_bodedemo`, `test_image`, `test_relativemargin`, `test_symbols`, `test_vertical`. All diffs were tiny (a few dozen pixels each, max magnitude ≤ 26/255), scattered around antialiased text and curve edges.
+
+### Per-test screenshot status (master vs phase-2 fix, all bindings)
+
+Each cell aggregates two pixel-diffs per test (master vs `master2` self-compare baseline, and master vs phase-2 fix). The classification rule is:
+
+- ✅ — both diffs report identical or pixel-equal output (test is fully reproducible *and* the optimization branch did not change it).
+- ⚠️ — both diffs are non-zero (test is *intrinsically* flaky — random data, timestamps, live system stats — so any difference is noise, not a regression).
+- ❌ — baseline is identical but the fix differs (a real visual regression introduced by the optimization branch).
+
+| Test | PyQt5 | PyQt6 | PySide6 |
+|---|:-:|:-:|:-:|
+| `test_backingstore` | ❌ 55 px (max=11) | ✅ | ✅ |
+| `test_bodedemo` | ❌ 39 px (max=16) | ✅ | ✅ |
+| `test_cartesian` | ✅ | ✅ | ✅ |
+| `test_cpudemo` | ⚠️ | ⚠️ | ⚠️ |
+| `test_curvebenchmark1` | ⚠️ | ⚠️ | ⚠️ |
+| `test_curvebenchmark2` | ⚠️ | ⚠️ | ⚠️ |
+| `test_curvedemo1` | ✅ | ✅ | ✅ |
+| `test_curvedemo2` | ✅ | ✅ | ✅ |
+| `test_data` | ⚠️ | ⚠️ | ⚠️ |
+| `test_errorbar` | ✅ | ✅ | ✅ |
+| `test_eventfilter` | ✅ | ✅ | ✅ |
+| `test_highdpi` | ✅ | ✅ | ✅ |
+| `test_image` | ❌ 6 px (max=9) | ✅ | ✅ |
+| `test_loadtest` | ⚠️ | ⚠️ | ⚠️ |
+| `test_logcurve` | ✅ | ✅ | ✅ |
+| `test_mapdemo` | ⚠️ | ⚠️ | ⚠️ |
+| `test_multidemo` | ✅ | ✅ | ✅ |
+| `test_relativemargin` | ❌ 72 px (max=11) | ✅ | ✅ |
+| `test_simple` | ✅ | ✅ | ✅ |
+| `test_stylesheet` | ✅ | ✅ | ✅ |
+| `test_symbols` | ❌ 4 px (max=9) | ✅ | ✅ |
+| `test_vertical` | ❌ 88 px (max=26) | ✅ | ✅ |
+
+**Summary at end of phase 3.** PyQt6 and PySide6: 16 ✅ / 6 ⚠️ / **0 ❌**. PyQt5: 10 ✅ / 6 ⚠️ / **6 ❌**. The 6 ❌ entries on PyQt5 are the regression that phase 4 fixes.
+
+**Root cause.** The id-keyed `font.key()` cache subtly changes the order in which the Qt5 font engine is asked to materialise specific font descriptors. On Qt5, the font engine hints text glyphs slightly differently depending on first-touch order — invisible to a human, but bit-non-identical to master. Qt6's font engine does not show this sensitivity.
+
+## Phase 4 — Option A: gate the font-key fast path on Qt5 (current state)
+
+**Change.** In `qwt/text.py`, the id-keyed cache is now guarded by a Qt-version check:
+
+```python
+from qtpy import QT_VERSION as _QT_VERSION
+
+_USE_FONT_KEY_FAST_PATH = not str(_QT_VERSION).startswith("5.")
+
+def font_key_cached(font) -> str:
+    if not _USE_FONT_KEY_FAST_PATH:
+        return font.key()
+    # ... id-keyed cache lookup ...
+```
+
+On Qt5 this becomes a thin pass-through to `font.key()` — bit-identical output to master is restored. On Qt6 (where it actually matters most for this issue) the optimization stays in place.
+
+**Verification.**
+
+1. **Screenshot regression** — re-ran PyQt5 capture and diff. The 6 ❌ entries from the phase 3 table all flip to ✅. Final per-binding tally becomes **16 ✅ / 6 ⚠️ / 0 ❌** on every binding — i.e. byte-identical output to master on every test that is reproducible at all.
+2. **Test suite** — `pytest -q` with `PYTHONQWT_UNATTENDED_TESTS=1` on all three bindings:
+   - PyQt5: 26 passed, 1 skipped
+   - PyQt6: 26 passed, 1 skipped
+   - PySide6: 26 passed, 1 skipped, 1 warning
+3. **Performance** — PyQt5 micro-bench rose from ~445 ms to ~450–550 ms (≈ +5 ms, well within the run-to-run noise). Qt6 numbers are unchanged.
+
+## Phase 5 — closing the residual Qt5↔Qt6 gap
+
+After phases 1–4 the Qt6 path was still measurably slower than Qt5 on the micro load test (~+20 % / +100 ms). The goal of phase 5 was to **understand and remove that residual gap**, not just to keep optimising blindly.
+
+**Method.** A second cProfile + `line_profiler` pass was run on the post-phase-4 tip, this time focused on the diff between PyQt5 and PyQt6 traces (rather than absolute hotspots). Three concrete root causes were identified, all specific to the Qt6 binding:
+
+1. **Python `enum.IntFlag` arithmetic.** PyQt6 exposes Qt enums as `enum.Flag` subclasses; every `flags & Qt.SomeFlag` test goes through `enum.__and__ → enum.__call__ → enum.__new__` (~6 µs each). PyQt5 uses plain ints, so the same code costs ~50 ns there. cProfile attributed ≈ 62 ms / run on PyQt6 to `enum.py`, **0 ms on PyQt5**. The single worst caller was `QwtPainterCommand.__init__`, which performs **twelve** successive `flags & QPaintEngine.DirtyXxx` tests per painter command — at ~300 commands per load-test run that is 3 600 enum operations alone.
+2. **`QFont.key()` is ~3× slower per call on PyQt6.** Per-call sip dispatch costs were measured at 3.3 µs (PyQt5) vs 9.3 µs (PyQt6) for cheap getters. `font.key()` was the single biggest residual hotspot inside `QwtText.textSize()`.
+3. **The `id(font)` fast path misfires on PyQt6.** PyQt6 returns a *fresh* Python wrapper around the same underlying `QFont` on most calls, so `id(font)` changes between calls and the id-keyed cache misses ~92 % of the time (vs ~60 % on PyQt5). The slower `font.key()` path then takes over, compounding cause #2.
+
+**Changes.**
+
+- **`qwt/painter_command.py`** — added a `_flag_int(flag)` helper (PyQt5/PyQt6 portable) and module-level `_DIRTY_PEN`, `_DIRTY_BRUSH`, … int constants. The State branch in `__init__` casts `state.state()` to int *once* and bitwise-tests against the cached int constants instead of going through `enum.__and__` 12 times per command.
+- **`qwt/graphic.py`** — same pattern in `qwtPaintCommand`'s State-replay branch (12 more flag tests per replayed command).
+- **`qwt/text.py`** — same pattern for `Qt.AlignXxx` flags (`_ALIGN_LEFT`, `_ALIGN_RIGHT`, …) in the hot bitwise-test sites in `taggedRichText()`, `QwtTextLabel.sizeHint()/heightForWidth()/textRect()`. The `setRenderFlags()` setter still stores the value as `Qt.AlignmentFlag` so downstream Qt APIs that strictly require an enum on PyQt6 (`QTextOption.setAlignment`, `QPainter.drawText`, `QFontMetrics.boundingRect`) keep working — only the per-test bitwise sites cast back to int locally.
+- **`qwt/text.py`** — **replaced the entire `id(font) → font.key()` cache** with a tuple-key cache. The new `font_key_cached(font)` returns an interned `(family, pixelSize-or-pointSizeF, weight, italic, stretch, styleStrategy)` tuple instead of `font.key()`. The two-level design keeps the original id-keyed fast path for repeated calls with the same QFont instance, and falls back to the tuple key (which never calls `QFont.key()`) for the PyQt6 case where wrappers churn. The same key is now also used by `fontmetrics()`/`fontmetrics_f()` — they previously called `font.toString()` per lookup, another ~3× more expensive on PyQt6.
+- The Qt-5 fast-path gate (`_USE_FONT_KEY_FAST_PATH`) introduced in phase 4 is no longer needed and was removed: since the new cache never calls `font.key()`, the font-engine first-touch ordering issue that motivated the gate cannot occur.
+
+**Verification.**
+
+- **Test suite** — `pytest -q` with `PYTHONQWT_UNATTENDED_TESTS=1` on both bindings: PyQt5 26 passed / 1 skipped, PyQt6 26 passed / 1 skipped. Same as phase 4.
+- **Performance** — PythonQwt micro `test_loadtest`, 10 runs each, run back-to-back on the same machine immediately after phase 5:
+
+| Config | PyQt5 ms (median / mean) | PyQt6 ms (median / mean) | Δ (PyQt6 − PyQt5) | PyQt6/PyQt5 |
+|---|--:|--:|--:|--:|
+| `master` (no optimisations) | 798 / 805 | 1 000 / 986 | +202 ms | **+25 %** |
+| `fix/93` tip (end of phase 4) | 511 / 517 | 611 / 622 | +100 ms | **+20 %** |
+| `fix/93` + phase 5 | 539 / 533 | 590 / 591 | **+51 ms** | **+9 %** |
+
+PyQt5 is essentially unchanged by phase 5 (the new int constants are inert on PyQt5 — Qt5 enums are already plain ints). PyQt6 dropped another ~20 ms median (mean −5 %): the Python `enum.Flag.__and__` budget is gone for the painter-command State branches (~3 600 enum ops/run eliminated), and the tuple-key font cache replaces the ~6 400 `QFont.key()` calls/run that previously cost ~45 ms.
+
+**Cumulative speed-ups on the micro load test, vs `master`:**
+
+| Binding | master → end of phase 4 | end of phase 4 → +phase 5 | **Total** |
+|---|--:|--:|--:|
+| PyQt5 | −36 % | +5 % (noise) | **−33 %** |
+| PyQt6 | −39 % | −3 % | **−41 %** |
+
+**The PyQt6↔PyQt5 ratio more than halved** (+20 % → +9 %). The remaining +9 % is the structural sip-dispatch cost (PyQt6 marshalling for cheap getters like `drawLine`, `boundingRect`, attribute reads) that is *not* removable from PythonQwt — it can only be mitigated by calling Qt fewer times per render, which phases 1–5 already pursue aggressively.
+
+## Final results
+
+> Numbers below summarise the state at the end of phase 4 (the version covered by the Option A gate). Phase 5 was applied on top and further closes the residual Qt5↔Qt6 gap on the micro load test from +20 % to +9 % — see the dedicated phase-5 table above. PlotPy load test was not re-run after phase 5; phase 5 is targeted at the per-call enum/sip overhead that dominates the *micro* benchmark, so the PlotPy improvement is expected to be smaller in relative terms but in the same direction.
+
+### PythonQwt micro `test_loadtest` (5 runs each, ms)
+
+| Binding | master | fix/93 (Option A) | Speedup |
+|---|---:|---:|---:|
+| PyQt5 | ~1 900 | ~450–550 | ×3.5–×4.2 |
+| PyQt6 | ~2 300 | ~450–675 | ×3.4–×5.1 |
+| PySide6 | ~2 900 | ~580–795 | ×3.6–×5.0 |
+
+### PlotPy `test_loadtest`, 60 plots (3 runs each, ms)
+
+| Binding | master (`1ab70cd`) | fix/93 (Option A) | Speedup |
+|---|---:|---:|---:|
+| PyQt5 | 25 134 | **16 169** | ×1.55 |
+| PyQt6 | 42 202 | **21 387** | ×1.97 |
+| PySide6 | 53 160 | **24 849** | ×2.14 |
+
+### Cross-binding gap (PlotPy load test)
+
+| Comparison | master | fix/93 |
+|---|---:|---:|
+| PyQt6 vs PyQt5 | +68 % slower | **+32 % slower** |
+| PySide6 vs PyQt5 | +111 % slower | **+54 % slower** |
+
+The original issue — a 1.5×–2× penalty for Qt6 over Qt5 — is largely resolved on the PlotPy load test, while the PyQt5 path remains bit-compatible with master both visually and behaviourally.
+
+## Backwards compatibility & public API surface
+
+The optimizations are deliberately confined to internal hot paths and do not alter the documented public API:
+
+- `QwtScaleMap.transform()`, `QwtScaleDiv.contains()`, `QwtScaleEngine.contains()/strip()`, `QwtAbstractScaleDraw.labelRect()/labelPosition()` — same signatures, same semantics, same return values.
+- `QwtText` and `QwtPlainTextEngine` — same signatures and semantics. The internal `_PrivateData` containers no longer derive from `QObject`; this is invisible from the outside because `_PrivateData` was a private holder, never exposed and never used as a Qt signal/slot target.
+- New module-level helper `qwt.text.font_key_cached()` is internal (lowercase, undocumented). It can be safely removed or refactored later without breaking any public consumer.
+- No new dependency. No change to `qtpy` requirements; the Qt-version gate uses `qtpy.QT_VERSION` which is already imported transitively.
+
+The screenshot regression sweep above is the empirical confirmation of this: byte-identical PNGs on every non-flaky test mean PythonQwt's rendered output is unchanged, on every binding.
+
+## Reproduction quickstart
+
+The whole evaluation can be reproduced from a fresh checkout in a few commands. The scripts assume three sibling virtual environments under `.venvs/{pyqt5,pyqt6,pyside6}/`, each with a single Qt binding plus `numpy`, `qtpy`, `pytest`, `pillow`, and `PythonQwt` installed editable.
+
+```powershell
+# 1. PythonQwt micro load test, all three bindings, 5 runs each
+.\scripts\bench_qt.ps1 -Repeat 5
+
+# 2. Visual regression sweep (PyQt5 example; repeat for pyqt6 / pyside6)
+$env:QT_API = "pyqt5"
+& .\.venvs\pyqt5\Scripts\python.exe scripts\capture_screenshots.py shots\fix\pyqt5
+& .\.venvs\pyqt5\Scripts\python.exe scripts\capture_screenshots.py shots\master\pyqt5  # after `git checkout master`
+& .\.venvs\pyside6\Scripts\python.exe scripts\diff_screenshots.py shots\master\pyqt5 shots\fix\pyqt5
+
+# 3. PlotPy load test (the test cited in the original GitHub issue)
+$env:PYTHONPATH = "c:\Dev\PlotPy;c:\Dev\guidata"
+foreach ($b in "pyqt5","pyqt6","pyside6") {
+    & ".\.venvs\$b\Scripts\python.exe" scripts\bench_plotpy_loadtest.py --repeat 3 --nplots 60
+}
+```
+
+## Test environment
+
+| Component | Value |
+|---|---|
+| OS | Windows 11 (x64) |
+| Python | 3.11.9 (NuGet build) |
+| PyQt5 | 5.15.11 (Qt 5.15.2) |
+| PyQt6 | 6.11.0 (Qt 6.11.0) |
+| PySide6 | 6.11.0 (Qt 6.11.0) |
+| qtpy | latest available at the time of capture |
+| PlotPy (for PlotPy load test) | 2.9.1 (editable install from `c:\Dev\PlotPy`) |
+| guidata (for PlotPy load test) | 3.14.3 (editable install from `c:\Dev\guidata`) |
+| Display | physical desktop session (not `offscreen`) — measurements include real Qt paint/composite cost |
+
+## Files touched
+
+| File | Phase 1 (cProfile) | Phase 2 (line-profiler) | Phase 4 (Option A) | Phase 5 (Qt5↔Qt6 gap) |
+|---|:-:|:-:|:-:|:-:|
+| `qwt/scale_map.py` | ✓ | | | |
+| `qwt/scale_div.py` | ✓ | | | |
+| `qwt/scale_engine.py` | ✓ | | | |
+| `qwt/scale_draw.py` | ✓ | ✓ (drop QObject, `__slots__`) | | |
+| `qwt/text.py` | ✓ | ✓ (drop QObject, font cache) | ✓ (Qt5 gate) | ✓ (alignment ints, tuple-key font cache, drop Qt5 gate) |
+| `qwt/painter_command.py` | | | | ✓ (int-flag State branch, `_flag_int` helper) |
+| `qwt/graphic.py` | | | | ✓ (int-flag State-replay branch) |
+
+Tooling added under `scripts/`:
+
+- `bench_qt.ps1` — driver for the PythonQwt micro load test across the three venvs.
+- `profile_loadtest.py` — cProfile harness used in phase 1.
+- `lineprofile_loadtest.py` — line_profiler harness used in phase 2.
+- `capture_screenshots.py` / `diff_screenshots.py` — phase 3 visual regression tooling.
+- `bench_plotpy_loadtest.py` — driver for the PlotPy load test (the test cited in the original issue).