Add option to crawlee cli to install the project or not

[Pijukatel]

Currently there are following options for package manager when running crawlee cli: Poetry Pip Uv Manual

Selecting any of the options except for the manual will not only prepare the project files, but immediately also install the packages to whatever environment is currently active, which might not be desired. (What is the use case where this is actually desired?)

Add one more boolean cli option "install the project to current environment" which will follow after package manager selection and will control whether the post_gen hook installs the project or not.

(Maybe drop the manual option?)

[janbuchar]

Selecting any of the options except for the manual will not only prepare the project files, but immediately also install the packages to whatever environment is currently active, which might not be desired. (What is the use case where this is actually desired?)

Um, starting a new project? Installing dependencies is the next step after bootstrapping for most users - it is comfortable if we do it for them.

Add one more boolean cli option "install the project to current environment" which will follow after package manager selection and will control whether the post_gen hook installs the project or not.

(Maybe drop the manual option?)

Yeah, dropping that option sounds like a good idea.

[vdusek]

Add one more boolean cli option "install the project to current environment" which will follow after package manager selection and will control whether the post_gen hook installs the project or not.

👍

[Pijukatel]

Um, starting a new project? Installing dependencies is the next step after bootstrapping for most users - it is comfortable if we do it for them.

Yes, I agree it is useful to install the dependencies for the users, I am just questioning the part about installing it to the currently active environment.

I would be also happy if this is just solved by installing the project automatically, but to dedicated freshly created environment.