I notice earlier in this issue, people were mentioning "pkg-
resources==0.0.0", whereas I'm seeing "pkg_resources==0.0.0". That's
interesting.
Also, this "pkg_resources==0.0.0" seems to show up specifically when
installing a *different version* of pip -- not necessarily the *latest*
version. Here
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
