Ed Morley eb6ee49dfe Emit metrics for how the Python version was chosen (#1069) ...

Currently an app's Python version can be set via a few different means:
- explicitly by the user (via `runtime.txt` or `Pipfile.lock`)
- implicitly via the sticky versions feature (for existing apps)
- implicitly via default version for new apps / those with empty cache

In order to determine the priority of features like automatic Python
patch version upgrades for sticky-versioned apps, it's useful to have
metrics for these.

There were previously no tests for either the sticky versions feature,
or changing the Python version by updating the `runtime.txt` file, so
I've added some now (given that I updated the conditional to add the
metrics, so useful to have coverage).

I've also removed the confusing overwrite of `DEFAULT_PYTHON_VERSION`
with the cached version, and kept them as two separate variables.

Closes @W-8099632@.
Closes @W-8099645@.

2020-09-18 18:48:57 +01:00

..

steps

Emit Python version metric events for all builds (#1066)

2020-09-16 12:28:15 +01:00

compile

Emit metrics for how the Python version was chosen (#1069)

2020-09-18 18:48:57 +01:00

default_pythons

Add support for Python 3.5.10 (#1062)

2020-09-07 13:01:09 +01:00

detect

Shellcheck Compliance (#438)

2017-08-03 17:36:23 -04:00

release

Shellcheck Compliance (#438)

2017-08-03 17:36:23 -04:00

test-compile

Pipenv development dependencies (ci) (#633)

2018-01-16 13:36:01 -05:00

utils

fix: drop broken version check

2018-11-08 16:14:05 -06:00

warnings

Shellcheck Compliance (#438)

2017-08-03 17:36:23 -04:00