Bump Default Python Version
https://github.com/microsoft/Oryx/blob/e9ed6812ff3f5a7047f33a46511e3b0ed6e6951b/platforms/python/versions/bullseye/defaultVersion.txt#L1
To my knowledge, all of the Azure App Services using Oryx support a higher PYTHON_VERSION.
Functions - 3.9 (with 3.10 in Beta) Web Apps - 3.10-3.11 Static Web Apps - 3.10-3.11
Should we bump our default version for python builds (bullseye and others) to at least 3.9?
@kjaymiller Hey Jay, thanks for the question -- the Oryx team actually chatted about this recently after we bumped the default version for a few other platforms (.NET, Go, Node, PHP) and settled on the following:
The default version for a platform will be the earliest version supported by Oryx that is also supported by the platform owner.
Note: the only current exception to this rule is Node as we bumped its default version to 16 despite 14 being supported for a few more months but wanted to get a jump on the update.
A few of the internal Microsoft teams that use Oryx have leveraged mechanisms we offer to set their own default version (e.g., Static Web Apps had been using Node 16 as their default for a couple of months while Oryx's default was 14), or the team requires the user to specify the version that they build with, bypassing the need for a default version (e.g., Azure Web Apps zip deploy requires the user to specify what minor version of Python they'd like to use).
With this in mind, do you have any thoughts as to what constitutes a "good" default version for a platform? We may decide to iron out our default version definition in the near future, and any additional feedback on the matter would be welcomed 😃
My current recommendation would be Python 3.9. Although all the services I'm aware of support 3.10. Azure function's support for 3.10 is still in Beta.
Current default seems to be 3.7 still.