switch from calc.get_property to calc.results.get #359
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.
After all, I think this should be
calc.results.get, notcalc.get_property. If nopropertiesare given, that defaults to all of the standard properties incalc.results, so a direct.getis more straightforward. That's what happens incalc.get_property(name, allow_calculation=False)anyway, but it also checks if the property is incalc.implemented_properties. And calculators aren't consistent about that, e.g.free_energyis incalc.results, but not incalc.implemented_propertiesfor xtb.implemented_propertiesdon't matter if we usecalc.results.getinstead.