It would be really neat if we could have a way to update the generated project with a newer version of the template.

By having separate templates maintained by various people, myself included, there will obviously be problems both introduced and solved over time. Because of this many or, if there was a serious problem, all of the projects generated from that template may need to be "regenerated". Support for this would definitely be an enhancement I believe.

However the idea of persevering the users current setup at the same time could be a challenge. For the basic values that cookiecutter needs to generate its templates, the json could just be written into the generated project as a dotfile or something to allow simple regeneration. However if some one has edited a generated file, not to replace the templates structure, but to add say, information about the project to the readme, it should be kept somehow.

I have not dug into the implementation details of cookiecutter and its code but if no one else wants to I may make a fork and attempt this in the future and submit a pull request if i can pull it off. However I would like to hear any thoughts on fixing the already edited file issue first.

As a possible extension to this update idea, maybe it could be possible to use the updating system to change a project from one base template to another... just an interesting thought, although admittedly of likely limited use..

Thanks