Skip to content

fix(memory): emit posix paths in memory index on Windows - #17

Open
ryanduguid wants to merge 1 commit into
JeffBrines:mainfrom
ryanduguid:fix/windows-path-separators
Open

ryanduguid wants to merge 1 commit into
JeffBrines:mainfrom
ryanduguid:fix/windows-path-separators

Conversation

@ryanduguid

Copy link
Copy Markdown

Summary

  • Memory index paths used str(Path), which emits backslashes on Windows and breaks test_memory_retrieval nested-path assertions (corrections/collections.md).
  • Store .as_posix() so agents and YAML round-trips see the same separators on every OS.
  • Add a Linux-visible test that stubs Path.relative_to to return PureWindowsPath, because Ubuntu CI never caught this (noted on Australian localisation pack: AU calendar, payroll, GST/BAS #14).

This is the small Windows fix from openfpa#14. It does not include the Australian pack.

A previous PR (#15) had the one-line change without a CI-reproducible test and was closed unmerged.

Test plan

  • pytest tests/test_memory_retrieval.py (5 passing, including the new backslash stub)
  • full pytest -q green locally
  • GitHub Actions on 3.11 / 3.12 / 3.13

Copy link
Copy Markdown
Author

The pull-request workflow runs are currently waiting for maintainer approval. Please approve them when convenient so CI can run against this revision.

Path stringification uses backslashes on Windows, so nested index
entries failed equality checks in test_memory_retrieval. Use
as_posix() and cover it on Linux by stubbing relative_to to return
PureWindowsPath — Ubuntu CI never exercised the old bug.
@ryanduguid
ryanduguid force-pushed the fix/windows-path-separators branch from 71e6a30 to 7adb404 Compare September 6, 2026 10:26
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.

1 participant