Thank you @gianfaProm and @kamil_b for the clarification.
This is a new problem, resulting from a change we made in how we resolve semantic information for specific Python versions. Due to this, Python versions that are set to “3” without minor information, as well as all versions that are “3.5” or lower, are affected.
Explicitly setting a Python version that is 3.6 or higher should fix the issue.
We have a ticket for this. Most likely we can release a fix next week.