Allow deprecated set_kpoints_path of KpointsData without cell #1047
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.
Fixes #1046
In a recent update, various buggy methods of the
KpointsData
class weredeprecated. The deprecated interface would raise a
ValueError
if theset_kpoints_path
would be called before a cell had been set, however,the deprecated methods used to allow for this, as long as the provided
list used explicit reciprocal coordinates and Cartesian mode was False.
Always raising when a cell was not defined was therefore breaking backwards
compatibility.
To restore this behavior, we now pass
cell=None
when it is not set, to thelegacy version of the
get_explicit_kpoints_path
method. This also requiredsome minor changes to the helper function
analyze_cell
A regression test was added to verify that the old behavior was successfully
restored through these changes