-
Notifications
You must be signed in to change notification settings - Fork 19
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
Return type of atomic_symbol
changed
#134
Comments
Yes indeed. I also noticed this, but I thought it was intentional. As mentioned by @cortner in #110 the problem with symbols is that they are not At the very least I agree @rashidrafeek that it should be documented 👍. Are you able to attend the monthly call next Monday or is this too horrible wrt. your timezone ? |
Yeah, it would be great to clarify this in the documentation. Thank you for pointing out the earlier issue—I completely missed it. This seems to be a duplicate and can be addressed there, so I’ll go ahead and close this issue. I’ll do my best to attend the monthly call on Monday. Will the timings be shared in the Zulip channel? If so, I can plan accordingly. Thanks for the invitation. |
They should be on the zulip, channel |
In the 0.5 update, it seems that
atomic_symbol
now returns aChemicalSpecies
object and not aSymbol
.returns
ChemicalSpecies
. Was this intentional? I was thinking that theatomic_symbol
is supposed to return aSymbol
, although the interface docs is also not clear about this. Currently there is aspecies
function which returns a ChemicalSpecies object. So if this was intentional, these two functions seems to have the same functionality. Also, It might be helpful to clarify the return type in the interface docs.The text was updated successfully, but these errors were encountered: