Skip to content

Fix ValueError when parsing TXT records with escaped semicolons (\;)#62

Merged
aredwood merged 3 commits intomasterfrom
claude/resolve-issue-49-EnBoq
Mar 17, 2026
Merged

Fix ValueError when parsing TXT records with escaped semicolons (\;)#62
aredwood merged 3 commits intomasterfrom
claude/resolve-issue-49-EnBoq

Conversation

@aredwood
Copy link
Copy Markdown
Owner

The remove_comments function was treating ; as a comment boundary, stripping the semicolon and leaving a trailing backslash. This caused shlex.split to raise ValueError: No escaped character.

Now escaped semicolons are skipped so they are preserved as part of the record value, which shlex correctly converts to a literal semicolon.

Fixes #49

claude and others added 3 commits March 16, 2026 22:52
The remove_comments function was treating \; as a comment boundary,
stripping the semicolon and leaving a trailing backslash. This caused
shlex.split to raise ValueError: No escaped character.

Now escaped semicolons are skipped so they are preserved as part of
the record value, which shlex correctly converts to a literal semicolon.

Fixes #49

https://claude.ai/code/session_012JHkX4dZkEHyQ6nNtD1a1B
@aredwood aredwood merged commit 2b5e1ad into master Mar 17, 2026
5 checks passed
@aredwood aredwood deleted the claude/resolve-issue-49-EnBoq branch March 17, 2026 18:11
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.

ValueError: No escaped character

2 participants