This bug looks like a duplicate of bug 1763844. My last comment there was:
py3clean is only executed if which tells us it exists:
if which py3clean >/dev/null 2>&1; then
py3clean -p python3-apt
else
hence it's quite strange.
I don't see how that code can fail (py3clean is in the same package as python3, hence the interpreter exists if py3clean exists), but if it does, _all_ python packages are affected.
This bug looks like a duplicate of bug 1763844. My last comment there was:
py3clean is only executed if which tells us it exists:
if which py3clean >/dev/null 2>&1; then
py3clean -p python3-apt
else
hence it's quite strange.
I don't see how that code can fail (py3clean is in the same package as python3, hence the interpreter exists if py3clean exists), but if it does, _all_ python packages are affected.