Comment 16 for bug 1635463

This is an issue for me as well, on Pop_OS.
I created a virtualenv from the python3 I got from `apt install python3`, using `-m venv`.
Inside that virtualenv, `pip freeze` does not show `pkg_resources==0.0.0` until I upgrade pip (in my case, from `pip-20.0.2` to `pip-22.0.4`).

$ uname -a
Linux noo-lappy 5.16.11-76051611-generic #202202230823~1646248261~20.04~2b22243~dev-Ubuntu SMP PREEMPT Th x86_64 x86_64 x86_64 GNU/Linux
$ python3 --version
Python 3.8.10
$ which python3
/usr/bin/python3
$ python3 -m venv test_env
. test$ . test_env/bin/activate
(test_env) $ pip freeze
pip(test_env) $ pip install -U pip
Collecting pip
  Using cached pip-22.0.4-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 20.0.2
    Uninstalling pip-20.0.2:
      Successfully uninstalled pip-20.0.2
Successfully installed pip-22.0.4
(test_env) $ pip freeze
pkg_resources==0.0.0