Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/Azure/Azure-Functions/issues/1999 below:

Drop old language versions support in Functions v4 · Issue #1999 · Azure/Azure-Functions · GitHub

In Functions v4, drop support for the following language versions:

• Node.js
  • Version 10
    • Community EOL: April 30, 2021
  • Version 12
    • Community EOL: April 30, 2022
• PowerShell
  • Version 6
    • Community EOL: September 4, 2020
• Python
  • Version 3.6
    • Community EOL: December 23, 2021

All these versions are currently supported by Functions v3, and they must continue being supported until the date promised by Azure Functions, even if this date exceeds the community EOL date. This promise, however, does not imply that these language versions must be supported by Functions v4 as well. As long as Functions v3 is not deprecated, it serves the purpose of fulfilling the promise. So, it is important to make sure that Functions v3 is not deprecated earlier than the end of support dates for each mentioned language version.

Here is how the result will look like:

¹ Support of these versions in Azure Functions is expected by the end of 2021

When migrating Functions apps from v3 to v4, users will have to explicitly specify a new language version and review, test, and potentially modify their code.

See also:

• Azure Functions language runtime support policy | Microsoft Docs
• Supported languages in Azure Functions | Microsoft Docs
• Internal: Support and Deprecation Policies for Azure Functions.docx

• Reduce maintenance burden for Azure Functions engineers.
• Reduce the footprint of language workers to make them more effiecient.
• Encourage users to migrate to supported language versions.

Functions v3 stats:

• Node.js
  • Version 10: ~22% of apps
  • Version 12: ~37% of apps
• PowerShell
  • Version 6: ~34% of apps
• Python
  • Version 3.6: ~17% of apps

Introducing a feature flag to enable old language versions in Functions v4 would defeat the purpose of the change.

Keeping support for old language versions in Functions v4 would mean not getting the benefits described in Motivation.

Language owners frequently introduce breaking changes in newer language versions. As a result, some Functions app code is expected to either stop working or produce unexpected and undesired behavior. In order to attract users attention to this fact and invite them to review and test their code, we should make sure the language version upgrade is performed by users explicitly.

• Java
  • We cannot drop Java 8 as the vast majority of Functions Java apps use this version, and they are expected to use it for the foreseeable future.
• Node.js
  • We cannot drop Node.js 14 because its community EOL is April 30, 2023, which is later than the projected Functions v3 deprecation date.
• PowerShell
  • We cannot drop PowerShell 7.0 because PowerShell 7.2 support cannot be added by the expected Functions v4 GA release date, so dropping 7.0 would mean that Functions v4 would GA without any version of PowerShell.
• Python
  • We cannot drop Python 3.7 because its community EOL is June 27, 2023, which is later than the projected Functions v3 deprecation date.

• Functions Host and language workers already emit error messages on invalid language versions.
• We should also make sure we have detectors notifying of this error and providing migration guidance.

Support needs to be aware of the language version support matrix.

The following documentation will need to be updated:

• Supported languages in Azure Functions | Microsoft Docs
• Node version
• PowerShell versions
• Python version

• Language workers
• Stacks API definition
• Tooling
  • Az CLI
  • Az PowerShell

No performance impact.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4