Bug Report: venv create failed & wrong command tips

[Golden-Pigeon]

Hi, thanks for your script!
When using the script, I found several bugs as follows.

• venv create failed
  • consequence: python3.8-venv not installed automatically.
  • suggestion: add sudo apt install python3.8-venv before building the venv
• wrong command tips
  • details: the sript tells the user to run source virtualEnvironment/bin/activate to activate the venv. However, virtualEnvironment could be replaced by ${directory}/${venvPATH} so that the user can directly copy and run the command.

Hope all above could help you to fix the script.

[CharryLee0426]

Hi, Stable version 1.1.0 has fixed these 2 bugs:

• The python version has been declared in the script when check environment tools. There is a question that all of the recent Linux releases have installed Python 3.8 or later. Therefore, most users won't meet the venv build wrong in fact;

• This is a good suggestion that the command tips should be improvement. I have changed a lot about tips, including text color, grammar and so on. Now it is more comfortable for use.

I want to say thanks for your good issue and my further plan is to make more powerful tools to simplify our routine workflow.