Upgrading venv but not pip-cache

We are trying to upgrade the SDK, and we are noticing that while the virtual environment upgrades, the pip-cache does not and this is where the imports are taken from.
This means that the code works for me as i upgraded before using a virtual environment but not for my colleague, who upgrade afterwards. But also if I now upgrade I cant see new features.
Can you help?

1 Like

Hi Natalie, does this answer help you? Pycharm stubs not found - #2 by rdejonge

This works, but the documentation is misleading with saying to add pip-cache as a content root. This doesnt seem to be needed if the library is in the venv.

Good point, this should be updated. Thanks for noticing!