Fix import statements for importing from the toplevel package#24
Merged
jesusmartinez-garcia merged 5 commits intoRobbie-H:mainfrom Jul 22, 2025
Merged
Conversation
71 tasks
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
2 participants
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.
pyproject.tomldeclares that the top-level package is calledCompGIT.When the package is installed (for example using
sage -pip install .), one cannot rely on being "in the folder". Instead, users would dofrom CompGIT import ....orfrom CompGIT.Git import .....Also fixes #25.
That the testing instructions involved setting of
PYTHONPATHwas a symptom of this bug. I've simplified it for you.