-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated emmocheck to ahead to latest formulation of units #809
Merged
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
5a7b904
Updated emmocheck to ahead to latest formulation of units
jesper-friis 850ad3d
Also ignore emmo.CGSUnit when checking unit dimension
jesper-friis 692533a
Merge branch 'master' into update-emmocheck2
francescalb a7fe590
Merge branch 'master' into update-emmocheck2
jesper-friis f30a66b
Merge branch 'master' into update-emmocheck2
jesper-friis 64d5073
Merge branch 'master' into update-emmocheck2
jesper-friis 8fcc5d8
Fixing two new pylint issues
jesper-friis 91794d5
Added some exceptions for EMMO unit dimension classes
jesper-friis 5c642a9
Merge branch 'master' into update-emmocheck2
jesper-friis d314b2a
Merge branch 'emmocheck-unit-dimension' into update-emmocheck2
jesper-friis 8ea482c
Also ignore CGSUnit
jesper-friis 9ea1c8f
Merge branch 'master' into update-emmocheck2
jesper-friis 9560af8
Removed Python 3.7 from CI Tests, but added Python 3.12 and 3.13 instead
jesper-friis eeff32b
Merge branch 'update-emmocheck2' of github.com:emmo-repo/EMMO-python …
jesper-friis f13883e
Removed test for Python 3.13
jesper-friis 06463a4
Removed Python 3.7 and added Python 3.12 to setup.py
jesper-friis 983c116
Allow missing elucidation for unit subclasses with a physical dimension
jesper-friis 99e8ada
Trying to fix failing test
jesper-friis ed28f35
Added configuration to skip modules
jesper-friis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have two tests? Shuold we not just stick to one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because EMMO changed since 1.0.0-rc2.
test_dimensional_unit()
works for current version of EMMO.test_dimensional_unit_rc2()
works for previous version of EMMO.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The common way for software to handle changes in their dependencies is to keep the latest version in sync with the latest version of the dependencies. That is why
test_dimensional_unit()
is updated to the latest version of EMMO. In addition we kept a renamed copy of the test that works with EMMO up to 1.0.0-rc2.To make the latest version of EMMOntoPy handle multiple versions of EMMO, it is not sufficient to rename the tests differently, we need a whole new formalisation to (preferably in a declarative way) specify what versions of EMMO each test is valid for. I added issue #821 for that.