Thanks @chriswmackey, I’ll raise it with our IT team and see if they’ve got any ideas for a solution.
It only took us 3 years but a lot of us were finally able to recreate this issue and we have pushed a fix for it in the latest pollination installers that you can download now.
I really wish we could have fixed this sooner, @charliebrooker, but it’s clear to me that I would not have been able to come up with a good fix without the ability to recreate the issue. The solution that I had to implement was just strangely specific and almost feels like an oversight in Python’s pip installer implementation. Or maybe it’s a Python security patch for an equally specific vulnerability.
In any event, let me know if you get to test the new installer on your work machines. More information about the fix is here on the LBT forum: