-
Notifications
You must be signed in to change notification settings - Fork 4
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
Split Python Packages options and collect under common dir #16
Conversation
About cookiecutter template inheritance: cookiecutter/cookiecutter#1485 |
b9eab1f
to
2bc11d3
Compare
I'm facing some problems when trying to perform a "tree copy" of the |
Solved locally! It was not a problem related with |
Problem: Once the Solution: Create a function called I'm planning to take advantage of the tempfile module for this. Fingers crossed... 🤞🏽 Edit: It worked! 🚀 |
5b91b97
to
54769c2
Compare
For the CI, I think the following approach should work:
|
Smoke tests in Python 3.7 are failing because |
Solves for #14 and will allow to start working on #10. This PR sets the base for creating any kind of template and reusing common files. New design is based on the following ideas:
templates/python
,templates/fortran
).common/
directory contains shared resources across different family templates (e.g.templates/python/common
).cookiecutter.json
is provided inside thetemplates/family/common/
and holds basic private variables. This ensures new families of templates need to override these vars in their customcookiecutter.json
.Before merging this:
doc
about new usage and addition of new templates. CheckREADME.rst
too..pre-commit-config.yaml
so it does not interfere with template files.