Skip to content
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

Remove Owlready2 as a direct dependency #36

Merged
merged 2 commits into from
Apr 27, 2021
Merged

Remove Owlready2 as a direct dependency #36

merged 2 commits into from
Apr 27, 2021

Conversation

CasperWA
Copy link
Contributor

@CasperWA CasperWA commented Apr 27, 2021

Fixes #35.

As stated in #35, we can remove Owlready2 as a dependency and rely on EMMO-Python to get it instead.

Note: Although, we do use Owlready2 directly in the generate_cif.py file. I have gotten second thoughts on this. Perhaps we should instead report this in the EMMO-Python repository and ensure a broader Owlready2 dependency version range? @jesper-friis and @francescalb what do you think?

This PR also updates the pre-commit hooks black and flake8. No files were updated after running pre-commit run --all-files using the updated versions.

@jesper-friis
Copy link
Collaborator

Good question. Explicit dependencies on specific versions is important. However, since EMMO-python has already an explicit dependency on Owlready2 (updated to Owlready2=0.30) we have a chain of explicit dependencies. I think it will be easier to maintain to only specify the version of Owlready2 in EMMO-python

jesper-friis
jesper-friis previously approved these changes Apr 27, 2021
Get it through EMMO instead.
No files updated when running `pre-commit run --all-files`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pip install error due to Owlready2/EMMO-Python discrepancy
2 participants