/
The Python venv is no longer bundled with the build and instead is automatically set up on the end-user side. The change should reduce the number of potential issues with system compatibility. However, this change has the consequence of lengthening the package installation time. In my experience, it is now 10-15 minutes as opposed to the 5 minutes before this change. Additionally, this change seems to introduce a Windows Security pop-up asking to allow the Python exe to access the network. Minimal testing shows that clicking Allow or Cancel has no effect on the server.
