I found that the problem was solved only after adding a new Python Environment. So, this sort of “bug” was shown only with one single python environment in the list. Sometime the package list still ...