Seem not to support the above theory, there this issue should IMHO only happen with broken python installations.
Before we had this error seen with manual custom python installations which we can impossibly fully cover, but the above might be a special upgrade situation between fully normal Ubuntu releases. Seems worth to spend a bit of time to have a second look.
Worst case (not sure this is feasible) it would become a general pattern of "if imports fail, graceful 'sorry your system python/deps are bad' error".
Other cases like: /errors. ubuntu. com/oops/ e70fba2e- ab46-11ed- 9e2a-fa163e9934 15
https:/
Seem not to support the above theory, there this issue should IMHO only happen with broken python installations.
Before we had this error seen with manual custom python installations which we can impossibly fully cover, but the above might be a special upgrade situation between fully normal Ubuntu releases. Seems worth to spend a bit of time to have a second look.
Worst case (not sure this is feasible) it would become a general pattern of "if imports fail, graceful 'sorry your system python/deps are bad' error".