Add support for creating a virtual environment inside the rendered template about cookiecutter-pylibrary HOT 4 CLOSED

Now sure what you're asking of me here. The packaging provided by this template should work in any environment than works with source or wheel distributions, and that includes virtualenvs.

Clarify what this means:

During set up, this template installs Python packages through pip to the Python user install directory

What "set up"?

from cookiecutter-pylibrary.

What I meant to suggest was adding the option to set up a virtual environment after executing cookiecutter .... Something like

1 - no
2 - yes
Install dependencies inside venv? [1]: 

By selecting option 1, everything would happen as right now. By selecting option 2 though a virtual environment would be created inside the rendered template, and it would then be sourced so tox and other template dependencies were installed in the venv.

I thought this would be a good feature since I wasn't expecting installing a library to my user as a side effect of cloning a cookiecutter template, and because some users prefer installing packages using pip only on virtual environments.

from cookiecutter-pylibrary.

Adding this would involve adding the option to the cookiecutter menu and then modifying this part of the post-gen hook

Implementing it should be straightforward, except perhaps for supporting the different shells and their different ways of activating the venv.

from cookiecutter-pylibrary.

I don't think this is a widely accepted workflow. I am using pipx to install tooling (including tox) ... and all this seems very crummy and will create support work for me, something I want to avoid especially when it's not my daily workflow.

from cookiecutter-pylibrary.