Python2: Logs in UI don't populate when there is an incompatible Python version on the server

[kgartland-rstudio]

When deploying from a python 2.7.12 environment to a server with a 2.7.9 environment, the deploy fails as expected; but no information is captured in the UI. The logs in the UI continue to display Deploying... while the the error Failed to deploy successfully is displayed in the form.

This doesn't seem to occur with Python3, for example:
Deploying from python 3.7.0 to Python 3.5.2 the following error is displayed in the UI logs:

Building Jupyter notebook...
Build error: Unable to find a compatible version of Python: No known installation matching major.minor version of 3.7.0

Found while testing #146
This likely just impacts Pyhon2.

[joncfoo]

This is a known issue and is a result of how we gather logs for a deployment. In short, we begin gathering logs when associated builders are run and not before.

I've marked this as wontfix for the time being.

[slopp]

Have we considered showing logs prior? Eg we could tell the user when we are inspecting their environment, bundling, etc. And could we even do an API call to check for compatible versions before we upload? The chattier we are the better - even if it isn’t all streamed from RSC.

Otherwise we will end up having a lot of support tickets that are hard to diagnose!