Naming convention for skeleton.py: rename or leave as-is? #638
sgbaird
started this conversation in
Best Practices & Workflows
Replies: 1 comment 3 replies
-
Hi @sgbaird, the Does this answer your question? Do you have a suggestion what we could add to the docstring so that this becomes clearer? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It's not entirely clear to me: is the intention for the user to rename
skeleton.py
to something more consistent with the project or leave it namedskeleton.py
? I would assume the former followed by updating any references to the skeleton module being renamed as well.For example, I took after some of the structure of UMAP's repo in several of mine, where if the package name / directory is called
mat_discover
then I make a module calledmat_discover_.py
:Alternatively I could call it
core.py
for example.Beta Was this translation helpful? Give feedback.
All reactions