1. as suggested in the comments: don't use sudo pip install as you will get conflicts with the system package manager sooner or later. Always install python packages via pip install --user.

2. $HOME/.local/lib/python3.6/site-packages shouldn't be on PATH, it's the directory containing python modules (python source code files), but no executables. You can check the path for user-installed executables with:

   $ python3 -m site --user-base | xargs -I {} echo {}/bin 

Most probably it's the $HOME/.local/bin. Add this one to PATH instead of site-packages. In your .profile/.bashrc/.bash_profile (whatever your OS specifies):

PATH="$HOME/.local/bin:$PATH" export PATH 

Notice the $PATH instead of PATH in the path appending command. Now restart the terminal (or source the profile file) and check whether the installed executables are available:

 $ which eb $ eb --help 

etc.

1. as suggested in the comments: don't use sudo pip install as you will get conflicts with the system package manager sooner or later. Always install python packages via pip install --user.

2. $HOME/.local/lib/python3.6/site-packages shouldn't be on PATH, it's the directory containing python modules (python source code files), but no executables. You can check the path for user-installed executables with:

   $ python3 -m site --user-base | xargs -I {} echo {}/bin 

Most probably it's the $HOME/.local/bin. Add this one to PATH instead of site-packages. In your .profile/.bashrc/.bash_profile (whatever your OS specifies):

 PATH="$HOME/.local/bin:$PATH"  export PATH 

Notice the $PATH instead of PATH in the path appending command. Now restart the terminal (or source the profile file) and check whether the installed executables are available:

 $ which eb $ eb --help 

etc.