You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This exposes the package as src.babel_validation rather than the idiomatic babel_validation. Downstream consumers must write from src.babel_validation.X import Y, which is unusual and may surprise users expecting standard package layout.
This would expose babel_validation directly. All internal imports (from src.babel_validation...) would also need to change to (from babel_validation...).
Notes
The current choice appears intentional (there is a comment in pyproject.toml). This issue is just documenting the trade-off flagged during the Opus code review of PR Add GitHub issue tests #67.
Any change here requires updating all from src.babel_validation... imports throughout the test suite and library.
Not blocking; assess whether downstream consumer ergonomics matter before changing.
Background
pyproject.tomlcurrently sets:This exposes the package as
src.babel_validationrather than the idiomaticbabel_validation. Downstream consumers must writefrom src.babel_validation.X import Y, which is unusual and may surprise users expecting standard package layout.Standard layout alternative
This would expose
babel_validationdirectly. All internal imports (from src.babel_validation...) would also need to change to (from babel_validation...).Notes
from src.babel_validation...imports throughout the test suite and library.