| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| langroid-0.67.4-py3-none-any.whl | 2026-08-30 | 484.7 kB | |
| langroid-0.67.4.tar.gz | 2026-08-30 | 432.8 kB | |
| 0.67.4 source code.tar.gz | 2026-08-30 | 59.2 MB | |
| 0.67.4 source code.zip | 2026-08-30 | 59.7 MB | |
| README.md | 2026-08-30 | 1.2 kB | |
| Totals: 5 Items | 119.9 MB | 0 | |
Bug fixes
read_file handles ~ paths safely — and a file-tool sandbox escape is closed (#1120)
read_file failed on ~-prefixed paths because it checked existence
before expanding the home directory. The originally proposed fix
(#1118) exposed a subtler problem: safe_resolve_path treated ~ as a
literal directory name, so naively expanding it would have turned a
previously blocked read into a working escape from the file-tool
sandbox — an agent could have named home-directory files from inside a
restricted curr_dir. 0.67.4 fixes both together: ~ is expanded so
legitimate reads work, and the sandbox guard now validates both the
expanded and literal readings of the path, verified end-to-end against
a fake $HOME. Thanks @pacocartones for surfacing the underlying bug.
parse_number_range_list tolerates malformed segment specs (#1119)
A malformed segment spec (e.g. a stray "3-" or non-numeric token)
raised and aborted the whole parse. It is now tolerated and logged, so
one bad segment no longer discards the valid ones. Thanks
@pacocartones for the original report and fix (#1117).
Full Changelog: https://github.com/langroid/langroid/compare/0.67.3...0.67.4