graphistry/pygraphistry

Summary Modernize CI/docs Python interpreter choices while preserving library backward compatibility. Policy (explicit) PyGraphistry runtime backward compatibility SHOULD remain Python 3.8+ for now. CI SHOULD keep explicit compatibility testing across the known-supported matrix (currently 3.8 .. 3.14, where working). CI jobs that are primarily operational/build/docs/tooling lanes should avoid EOL interpreters and move to maintained versions (prefer newer where feasible). Why Python 3.8 is EOL, so non-compat lanes pinned to 3.8 create avoidable infra risk. We still need confidence in older-runtime compatibility for users. Splitting compatibility lanes from operational lanes gives both safety and forward motion. Scope for this issue Inventory and classify Python-version usage across CI/docs/packaging as: compatibility lanes (must include old+new supported versions), operational lanes (prefer maintained/current interpreters), policy declarations (python_requires, docs claims, toolin

Summary Adopt repo-wide mypy --strict via phased rollout, with explicit separation between contributor work (safe incremental fixes) and maintainer work (policy, CI gates, and suppression governance). Related Pyright monitor-mode tracking: #1075 Prior pyright/pylance request: #465 M0b IR typing work (completed): #1091 Baseline (initial strict run) Reference command: PYTHONPATH=. uv run --python 3.13 --no-project --with mypy==1.14.1 \ python -m mypy --config-file mypy.ini --strict graphistry Observed (initial pass): Total errors: 1966 Top codes: no-untyped-def (745), no-untyped-call (547), type-arg (222), unused-ignore (167), attr-defined (98) Highest-density area: graphistry/layout/* (~518) Top files: feature_utils.py (187), layout/sugiyama/sugiyamaLayout.py (152), PlotterBase.py (127), layout/graph/graphBase.py (86), embed_utils.py (70) Working model Contributor-friendly PR shape Keep PRs small and mechanical: single error family and small file set. Prefer one of these scopes p

Problem During #977 (cudf SIGSEGV fix), a real UnboundLocalError in hop.py was missed by both ruff and mypy: # edge_map assigned only inside this branch: if g_out._edges is not None and edge_hop_col is not None and ...: edge_map = ... # then used outside it — NameError/UnboundLocalError at runtime: if missing_mask.any() and edge_hop_col is not None and ...: ... safe_map_series(..., edge_map) # edge_map possibly unbound! The bug was masked by an upstream SIGSEGV (so it never surfaced in production), and only caught by writing a test that exercised the specific branch combination (`label_node_hops=True, label_edge_hops=None` with a non-empty `missing_mask`). Why ruff/mypy missed it ruff F821 only catches names with no assignment anywhere in scope — not conditionally-assigned names mypy does not flag "possibly unbound" from conditional branches unless the variable is annotated before the branch (e.g. `edge_map: pd.Series` declared before the `if`) Neither tool does full dat

Summary Explore packaging the GFQL Cypher compiler as a WASM module for browser/JS environments. This would enable client-side Cypher query compilation and potentially execution on in-memory graph data without server round-trips. Why this matters Interactive notebooks/dashboards: Run Cypher queries directly in the browser against local graph data Offline/edge use cases: Graph query capability without network dependency Developer tools: Cypher playground, query validation, AST visualization in the browser Embedding: Ship a lightweight Cypher engine in JS/TS applications without a Python backend Recommended first spike The easiest entry point is testing whether the existing Python Cypher compiler works in Pyodide (CPython-in-WASM): ```python In a Pyodide environment (e.g., https://pyodide.org/en/stable/console.html): import micropip await micropip.install('pygraphistry') from graphistry.compute.gfql.cypher.api import compile_cypher Does this work without pandas? compiled = compile_cyph