Eopkg breaking up like that is a good sign that something is wrong in the system python toolchain, and more often then not that happens after a pip install (tl;dr: never pip install anything, always use virtualenvs for python packages)
You could try to fix things by running sudo eopkg install --reinstall python3, but if eopkg itself is not responding the easiest and fastest way to fix the mess is to backup and reinstall.
