When a user SSHes in and does pip install foo, our pip.conf tells pip to install the package in /var/user-packages/usr/lib/python3.10/site-packages.
The other half of that is that Python needs to be configured separately to look for packages there. We've historically done that with a magic .pth file. But we dropped that file in the Python 3.7 -> Python 3.10 migration, since it didn't look like it was doing anything.
This restores the load-bearing .pth file. Other than updating it for Python 3.10, it works the same way it did before.
Test plan
[x] Push a build to an OT-2 and follow the steps to reproduce in EXEC-390.
This fixes EXEC-390.
When a user SSHes in and does
pip install foo
, our pip.conf tells pip to install the package in/var/user-packages/usr/lib/python3.10/site-packages
.The other half of that is that Python needs to be configured separately to look for packages there. We've historically done that with a magic
.pth
file. But we dropped that file in the Python 3.7 -> Python 3.10 migration, since it didn't look like it was doing anything.This restores the load-bearing .pth file. Other than updating it for Python 3.10, it works the same way it did before.
Test plan