You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The python-side aiida-dftk and the julia-side AiidaDFTK.jl will inevitably have some form of version locking, in the sense that their expected IO interfaces depend on each other. We should agree on some convention about this.
E.g. will the semantic versioning in AiidaDFTK.jl reflect breaking changes where aiida-dftk needs to change ? If yes, then some for of checking of the version should probably occurr in aiida-dftk ?
The text was updated successfully, but these errors were encountered:
in the test environment under the assumption that we'd bump AiidaDFTK to 0.2 when breaking changes happen.
There should be some check at runtime too, I agree. We can either insert it in the julia -e argument, or add some "format version" to the json file. ({ "version": 1, ... })
The python-side aiida-dftk and the julia-side AiidaDFTK.jl will inevitably have some form of version locking, in the sense that their expected IO interfaces depend on each other. We should agree on some convention about this.
E.g. will the semantic versioning in AiidaDFTK.jl reflect breaking changes where aiida-dftk needs to change ? If yes, then some for of checking of the version should probably occurr in aiida-dftk ?
The text was updated successfully, but these errors were encountered: