[codex] Use a named Python import package - #16
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
src/aep_load_forecasting/package layoutaep_load_forecastingand never exposes a top-levelsrcpackageWhy
The v0.1.0 wheel treated the source container itself as the import package. A generic top-level
srcpackage is collision-prone and is not the standard PyPA src layout. The stableaep-*console commands remain unchanged; direct Python imports now useaep_load_forecasting.*.Validation
python -m pytest -q— 66 passedpython -m ruff check src tests streamlit_app.pypython -m compileall -q src tests streamlit_app.pypython -m buildaep_load_forecasting/__init__.pyand excludesrc/__init__.py--help