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.
Resolves #1149
I was a bit opinionated with these changes in expanding import paths fully and using relative imports, but I don't particularly believe that needs to be enforced and no linting rules exist to enforce it anyway. I do think that it will be a bit helpful in the near term, with structural refactors ahead, and that we should discuss whether or not to codify it in the style guide. Some major projects, e.g. pandas, do this.
This also adds a manual check in linting ci to make sure no further
import xtgeo
s are added