Skip to content

test: [expected failures] function-library fixtures pending spec decisions - #165

Draft
leongdl wants to merge 1 commit into
OpenJobDescription:mainlinefrom
leongdl:conformance-func-lib-expected-failures
Draft

test: [expected failures] function-library fixtures pending spec decisions#165
leongdl wants to merge 1 commit into
OpenJobDescription:mainlinefrom
leongdl:conformance-func-lib-expected-failures

Conversation

@leongdl

@leongdl leongdl commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Important

Expected-failure / spec-question fixtures — do not expect these to pass. Parked in EXPR/proposed/ (not discovered by the runner). Each asserts a strawman expectation and must not move into jobs/ until the spec question beside it is resolved or the bug is fixed. Details in proposed/README.md.

Contents (3 fixtures, dual-implementation verified)

  • expr2.2.6--repr-py-newline-roundtrip — implementation bug in BOTH implementations: repr_py("a\nb") emits a raw newline inside the quotes (invalid Python literal; ast.literal_eval raises SyntaxError). §2.2.6 is explicit that repr_py follows Python's repr, which escapes. Move to jobs/ once fixed.
  • expr2.2.4--center-odd-padding — spec gap, NO divergence: both implementations put the odd pad space on the RIGHT (matching Python str.center). §2.2.4 is silent on the split. The spec should document the de facto behaviour; then this fixture (with corrected expectation) goes live.
  • expr2.2.4--isdigit-unicode — spec ambiguity, NO divergence: both implementations return false for isdigit("٣") (ASCII-only digits). §2.2.4 leaves "digit" undefined while §2.2.5 gives \d explicit Unicode semantics. Note the Python openjd CLI here deviates from native Python str.isdigit. The spec must define "digit"; the de facto agreement is ASCII-only.

Companion to the green-fixture PR from branch conformance-func-lib-gaps.

…sed/)

Three parked fixtures with dual-implementation observations: center() odd-padding and ASCII-only isdigit() are spec gaps where BOTH implementations agree (no divergence - the spec should document the de facto behaviour), and repr_py raw-newline emission is a bug in BOTH implementations per the explicit spec text. Details in proposed/README.md. Companion to conformance-func-lib-gaps.

Signed-off-by: David Leong <116610336+leongdl@users.noreply.github.com>
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