Support multiple kinds of project templates

[benjixx]

I have different kind of python projects in mind that require slightly different templates:

• lib (library that is used in other Python projects),
• cli (application that is used -- probably interactively -- from command line),
• daemon (application that is prepared to run as a daemon, including init.d scripts, etc.)

I'm already working on a prototype that uses Jinja (on which we already depend through Sphinx) together with template inheritance to support multiple project templates without (too much) code duplication.

Also it would be nice to get this template generation process integrated with virtualenvwrapper's mkproject command. Ideas and thoughts about this probably should go into a separate ticket.

[seanfisk]

This is a great idea. I especially like the idea of adding a command which just creates a project inside a directory. That specially is something that I have been thinking about for a while.

If we do create a command, it would be nice for PPT to be an installable Python module. The difficult part is that it would significantly change the layout of the template project.

[benjixx]

Yes, PPT needs to be installed as a Python module itself then.

It will significantly change project layout, but makes also a lot of things cleaner as no removing of files is necessary anymore -- just an example.

[seanfisk]

I agree. I think that this is the eventual path of PPT anyway, so we might as well get started. In fact, most of the files can be kept, but they will need to be moved into a "data directory" that gets included with the PPT package. We can even use PPT recursively to create a project for itself :)