Issues

• Is support for in-place operations intentional?

  bug
  pyiron/flowrep#328 · Filter by author XzzX opened on Sep 8, 2026
  2

• Improve .draw(): indicate data for retrospective objects

  enhancement
  pyiron/flowrep#327 · Filter by author liamhuber opened on Sep 8, 2026

• Include status in the retrospective graph

  enhancement
  pyiron/flowrep#322 · Filter by author samwaseda opened on Sep 1, 2026
  1

• Parser errors should be easier to track down

  pyiron/flowrep#320 · Filter by author liamhuber opened on Aug 26, 2026

• QoL symmetry: Run.inputs mirroring Run.outputs

  enhancement
  pyiron/flowrep#314 · Filter by author liamhuber opened on Aug 14, 2026
  1

• A metadata template

  pyiron/flowrep#310 · Filter by author liamhuber opened on Aug 10, 2026
  1

• Why input-/output_port and not just inputs/outputs in NodeData?

  pyiron/flowrep#305 · Filter by author samwaseda opened on Jul 24, 2026
  1

• For-each parsing options

  enhancement
  pyiron/flowrep#287 · Filter by author liamhuber opened on Jul 15, 2026
  2

• Parsing python operators

  enhancement
  pyiron/flowrep#276 · Filter by author liamhuber opened on Jul 11, 2026
  20

• QoL: if parser should accept known symbols for its case

  enhancement
  pyiron/flowrep#267 · Filter by author liamhuber opened on Jul 8, 2026
  4

• Parse in-line if statements

  enhancement
  pyiron/flowrep#138 · Filter by author liamhuber opened on Feb 18, 2026
  1

  

• Add metadata to the flowrep dictionary?

  enhancement
  pyiron/flowrep#99 · Filter by author samwaseda opened on Jan 26, 2026
  6