We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
package_dir_name
I assumed the package_dir_name to be bg_mpl_stylesheets during the cookiecutter setup:
[3/10] project_name (diffpy.my_project): bg-mpl-stylesheets [4/10] package_dist_name (bg-mpl-stylesheets): [5/10] package_dir_name (bg_mpl_stylesheets):
However, after generating the repository, the directory structure shows:
Untracked files: requirements/README.txt src/bg-mpl-stylesheets/
It seems that package_dir_name was set to bg-mpl-stylesheets instead of bg_mpl_stylesheets.
bg-mpl-stylesheets
bg_mpl_stylesheets
The text was updated successfully, but these errors were encountered:
I think it should be bg-mpl-stylesheets shouldn't it?
Sorry, something went wrong.
If we use src/bg-mpl-stylesheets, then we get the following:
src/bg-mpl-stylesheets
I think it should be bg_mpl_stylesheets. So, we need to fix it one way or another for non-namespace packages containing -."
-
Also look into /src/billingegroup/*/version.cfg generated in .gitignore instead of /src/bg_mpl_stylesheets/*/version.cfg
/src/billingegroup/*/version.cfg
.gitignore
/src/bg_mpl_stylesheets/*/version.cfg
Addressed by Billingegroup/bg-mpl-stylesheets#65 (comment)
Yes, the import name has to have underscores. But everything else is with dashes. Directories, repo and package name
Successfully merging a pull request may close this issue.
I assumed the package_dir_name to be bg_mpl_stylesheets during the cookiecutter setup:
However, after generating the repository, the directory structure shows:
It seems that
package_dir_name
was set tobg-mpl-stylesheets
instead ofbg_mpl_stylesheets
.The text was updated successfully, but these errors were encountered: