-
Notifications
You must be signed in to change notification settings - Fork 15
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
Always use periodic_table.csv file embedded in the repo #1191
Conversation
setup.py
Outdated
@@ -61,5 +61,5 @@ | |||
'structuretoolkit==0.0.11' | |||
], | |||
cmdclass=versioneer.get_cmdclass(), | |||
|
|||
package_data={'': ['_data/*.csv']}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a specific reason to name the folder _data
rather than just data
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I considered this private to the repo. However, since there is no __init__
(at least not yet). It will not pop up in the dir of the package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I also do not expect there to be any __init__
in the data directory but on the root level of the repository I would prefer to have it as data
rather than _data
or .data
.
I think the "proper" way to access package data is via pkgutil, then you can also hard code "pyiron_atomistics" as the package name rather than relying on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
@niklassiemer I guess it makes sense to release a new version of |
No description provided.