Michael Sonntag
Thanks for reporting this issue! I saved a document using `Python 2.7` with `odml 1.4.1` but was not able to recreate the reported error. Could you give more details about...
PR #355 should address this issue. A follow up PR will further cleanup all Deprecation warnings we'll find.
PR #356 should have cleaned up the remaining Deprecation warnings. Please let me know if I missed any.
By default, a conversion that encounters a non-v1.1 odml Section.include will lead to a [warning] conversion log message, but will export the Section.include unchanged. The converter will include a flag...
Hi @penguinpee, thank you for the comment! This issue has been on my todo list for quite a while now, but unfortunately I cannot say, when I will get around...
> Would you have an estimate when this small change can be expected? I would like to fix it within the next 2 month, but I am a bit swamped...
@penguinpee: I think I managed to upgrade to the usage of rdflib >= 6.0.0, but still need to clear some changes with the other core devs and run some tests...
A new release (1.5.3) has been uploaded to PyPI that supports rdflib v6+ by default. There should be no changes in behavior. Users that require Python
I think this issue asks for odml v1.3 documentation. We can check if we can enable readthedocs builds for the version_1.3 branch.
The flaky rdflib dependency strikes again, tests fail on github actions for Windows with Python 3.7 only while all AppVeyor tests run fine. Will look into the issue but keep...