Skip to content

Require complete bytes in Base16 validation - #517

Open
Apeksha9389 wants to merge 1 commit into
python-validators:masterfrom
Apeksha9389:fix/base16-complete-bytes
Open

Apeksha9389 wants to merge 1 commit into
python-validators:masterfrom
Apeksha9389:fix/base16-complete-bytes

Conversation

@Apeksha9389

Copy link
Copy Markdown

base16("ABC") currently succeeds even though the value contains only one and a half encoded bytes and Python's Base16 decoder rejects it. Require complete pairs of hexadecimal characters while retaining lowercase support and the existing empty-input behavior.

RFC 4648 section 8 encodes each byte as two Base16 characters. This deliberately tightens validation for odd-length hexadecimal strings, which were previously accepted.

Five new regressions fail on master and pass with this change. Full tests including doctests pass on Python 3.12 (1,176 passed). Ruff lint/format checks and strict Pyright pass with zero diagnostics. Other Python versions are left to CI.

Prepared with AI assistance; reproduced and tested locally.

@Apeksha9389

Copy link
Copy Markdown
Author

Could a maintainer approve the pending CI runs and review this PR for merging? Local tests, doctests, Ruff, and strict Pyright all pass. Thank you.

This branch has not been deployed

No deployments
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