prxnvt ad6aca08bf XLSX: a Python spill is recorded at its anchor, and one too large keeps its values ...

A Python cell's spill range was recorded only when the file held a record for
one of its other cells, so a result whose other cells are blank, which a file
may leave out, opened with no spill and no rebuilt result. The range is now
recorded when the anchor is read, if a result can fill it.

A Python range larger than a result may be (more than 1,000,000 cells, but
within what the reader tracks) emptied the cells it covered, although it is
no spill and file-format-parity.md says such cells keep the values the file
shows. They are now kept as plain values; a formula's spilled values are still
dropped, since recalculation fills them again.

Tests: a_python_spill_whose_blank_cells_have_no_records_is_still_a_spill and
a_python_spill_range_larger_than_a_result_keeps_its_values_as_plain_values;
both fail without the fix.

2026-11-02 02:02:07 -05:00

..

examples

fix: satisfy stricter clippy lints CI's newer stable toolchain catches

2026-10-12 02:52:07 +02:00

src

XLSX: a Python spill is recorded at its anchor, and one too large keeps its values

2026-11-02 02:02:07 -05:00

tests/it

Merge origin/main (25881a8e) into the Python cells branch

2026-11-02 01:29:06 -05:00

Cargo.toml

Enforce workspace Clippy standards and document lint policy

2026-10-28 10:52:53 +00:00