Upgrade to capellambse v0.6.x #131
Merged
Conversation
This file contains 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
Wuestengecko
force-pushed
the
capellambse-v0.6
branch
4 times, most recently
from
a6ea67e to
554970a
Compare
Merged
Wuestengecko
force-pushed
the
capellambse-v0.6
branch
from
554970a to
e95d172
Compare
- The "description" field now uses the correct spelling of py-capellambse - Shorten the license info in the PyPI sidebar to just the license name
ewuerger
force-pushed
the
capellambse-v0.6
branch
from
e95d172 to
514da5d
Compare
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.
This PR migrates the codebase to the new import structure and changed class names in capellambse v0.6.x.
The diff is a bit inflated, as I also took the opportunity to unify the imports, and also repair the mypy hook (so I could rely on it during the migration). The latter uncovered a variety of type errors, which I then also went ahead and fixed. I didn't touch any of the logic (as far as I could), so there shouldn't be any breakage.
I've marked the commit as breaking change, to try and make downstream more aware of this upgrade.