Personally I consider it bloat for private projects. Using pyenv suffices.
tools that interact with virtual environments need to be installed outside of the environment they interact with. And example for that is poetry. Refer to this note: Global CLI tool installation

Howto

Create

Replace venv_folder/ with your own name for the virtual environment.
{shell}python -m venv venv_folder/

Activate

{shell}source venv_folder/bin/activate

Automation

#!/bin/bash 
# Save the current directory 
CURRENT_DIR=$(pwd) 

# Navigate to the parent directory 
cd .. 

# Activate the virtual environment 
source venv_folder/bin/activate 

# Return to the original directory 
cd "$CURRENT_DIR" 

# Notify the user 
echo "Virtual environment activated and returned to $CURRENT_DIR"
  1. {shell}chmod +x activate_env.sh
  2. {shell}source activate_env.sh