When this command is executed, it will upgrade frappe-bench package inside the virtualenv.
But when you run bench, it is probably using frappe-bench which is outside the virtualenv. You can run where bench and it will tell where it is installed.
Based on that, you can upgrade the corresponding frappe-bench package by running
Sorry, I don’t think that’s quite right. If each pip3 command is run from the env, shouldn’t it be dealing with it’s env only, rather that anywhere else? Here’s what I see:
erpnext@ded1 ~/erpnext $ ./env/bin/pip3 list | grep frappe
frappe 13.18.0 /home/erpnext/erpnext/apps/frappe
frappe-bench 5.7.5
erpnext@ded1 ~/erpnext $ ./env/bin/pip3 install --upgrade frappe-bench
Requirement already satisfied: frappe-bench in ./env/lib/python3.9/site-packages (5.7.5)
Requirement already satisfied: virtualenv in ./env/lib/python3.9/site-packages (from frappe-bench) (20.13.0)
Requirement already satisfied: honcho in ./env/lib/python3.9/site-packages (from frappe-bench) (1.1.0)
Requirement already satisfied: requests in ./env/lib/python3.9/site-packages (from frappe-bench) (2.25.1)
Requirement already satisfied: Jinja2~=2.11.3 in ./env/lib/python3.9/site-packages (from frappe-bench) (2.11.3)
Requirement already satisfied: python-crontab~=2.4.0 in ./env/lib/python3.9/site-packages (from frappe-bench) (2.4.2)
Requirement already satisfied: setuptools in ./env/lib/python3.9/site-packages (from frappe-bench) (58.1.0)
Requirement already satisfied: Click in ./env/lib/python3.9/site-packages (from frappe-bench) (7.1.2)
Requirement already satisfied: GitPython~=2.1.15 in ./env/lib/python3.9/site-packages (from frappe-bench) (2.1.15)
Requirement already satisfied: semantic-version~=2.8.2 in ./env/lib/python3.9/site-packages (from frappe-bench) (2.8.5)
Requirement already satisfied: gitdb2<3,>=2 in ./env/lib/python3.9/site-packages (from GitPython~=2.1.15->frappe-bench) (2.0.6)
Requirement already satisfied: MarkupSafe>=0.23 in ./env/lib/python3.9/site-packages (from Jinja2~=2.11.3->frappe-bench) (2.0.1)
Requirement already satisfied: python-dateutil in ./env/lib/python3.9/site-packages (from python-crontab~=2.4.0->frappe-bench) (2.8.2)
Requirement already satisfied: chardet<5,>=3.0.2 in ./env/lib/python3.9/site-packages (from requests->frappe-bench) (4.0.0)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in ./env/lib/python3.9/site-packages (from requests->frappe-bench) (1.26.7)
Requirement already satisfied: certifi>=2017.4.17 in ./env/lib/python3.9/site-packages (from requests->frappe-bench) (2021.10.8)
Requirement already satisfied: idna<3,>=2.5 in ./env/lib/python3.9/site-packages (from requests->frappe-bench) (2.10)
Requirement already satisfied: six<2,>=1.9.0 in ./env/lib/python3.9/site-packages (from virtualenv->frappe-bench) (1.15.0)
Requirement already satisfied: distlib<1,>=0.3.1 in ./env/lib/python3.9/site-packages (from virtualenv->frappe-bench) (0.3.4)
Requirement already satisfied: platformdirs<3,>=2 in ./env/lib/python3.9/site-packages (from virtualenv->frappe-bench) (2.4.1)
Requirement already satisfied: filelock<4,>=3.2 in ./env/lib/python3.9/site-packages (from virtualenv->frappe-bench) (3.4.2)
Requirement already satisfied: smmap2>=2.0.0 in ./env/lib/python3.9/site-packages (from gitdb2<3,>=2->GitPython~=2.1.15->frappe-bench) (3.0.1)
Requirement already satisfied: smmap>=3.0.1 in ./env/lib/python3.9/site-packages (from smmap2>=2.0.0->gitdb2<3,>=2->GitPython~=2.1.15->frappe-bench) (4.0.
0)
erpnext@ded1 ~/erpnext $ ./env/bin/pip3 list | grep frappe
frappe 13.18.0 /home/erpnext/erpnext/apps/frappe
frappe-bench 5.7.5