Your ezCol.py does not start with a shebang (#!/usr/bin/env python3).
Instead, the first line is just:

programName = 'ezCol250313a.py'

➜ That means Linux has no idea which Python interpreter to use.

So when you run:

python ezCol.py

or:

./ezCol.py

it may be using the system Python, not your virtual environment — which explains why it can’t find pkg_resources.

---

✅ What to do next (quick fix)

Option 1 — run it with your venv’s python explicitly

This avoids all interpreter confusion:

/path/to/ezra-env/bin/python ../ezRA/ezCol.py

or, if you’re inside the venv already:

source ezra-env/bin/activate
python ../ezRA/ezCol.py

If pkg_resources is installed in the venv, this should now work.

---

✅ Option 2 — add the correct shebang to the script

Edit ezCol.py and add as the first line:

#!/usr/bin/env python3

So the top of the file becomes:

#!/usr/bin/env python3
programName = 'ezCol250313a.py'

Then make it executable:

chmod +x ezCol.py

Now it will run with your default python3 (which should be from the venv if activated).

---

⚠️ One more important check

Make sure setuptools is installed inside the venv:

source ezra-env/bin/activate
pip install --upgrade setuptools

Then confirm:

python -c "import pkg_resources; print('OK')"

---