Made the init method trigger also the install

[Ledoux]

@pocketjoso @franblas

if people wants to first create a project folder <app_name> and inside of it create a venv.
They can actually do then a

tpt init --templates <templates>

and the result will be the same as if they would have done

tpt -c --name <app_name> --templates <templates>

For that I needed to make trigger install in the dump sub task in the case where the program is equel to the init task.

[pocketjoso]

I'm not sure I see value adding a second way of doing the same thing. What's the use case - when you're too lazy to delete/move an already existing folder to use the tpt -c command from scratch? Imo more important to keep api surface area small than providing convenience for that use case.

[Ledoux]

@pocketjoso
I met two use cases yersterday:

• one with adrien when he asked how to make internal the python venv in your project. Because you cannot actually create a venv, then create your folder app and after mv your venv inside of it becaus eof path breakings.
• one with myself when I wanted to create an app already in a git repo that I have initiated from github and git cloned.

But I agree that we don't specially need to talk about this sub-api, it is kind of necessary existing as long as the create method calls it anyway, but it would be useful to mention for people that meet these use cases

[franblas]

@Ledoux The workflow should be to create the venv before creating the app, and people should follow those rules. So the 1st use case you are quoted should not happened.