Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated Python 3.12 Version Support and EOL Dates in Azure Functions #125964

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

baku2san
Copy link

This update includes the addition of Python 3.12 to the list of supported versions in Azure, with its General Availability (GA) and expected community End of Life (EOL) date. The updated support matrix is as follows: https://azure.microsoft.com/en-us/updates?id=481333

Supported version Support level Expected community EOL date
Python 3.12 GA October 2028

The EOL dates are based on the official Python release schedule, which can be verified at https://devguide.python.org/versions/.

This update includes the addition of Python 3.12 to the list of supported versions in Azure, with its General Availability (GA) and expected community End of Life (EOL) date. The updated support matrix is as follows:
https://azure.microsoft.com/en-us/updates?id=481333

Supported version	Support level	Expected community EOL date
Python 3.12	GA	October 2028

The EOL dates are based on the official Python release schedule, which can be verified at https://devguide.python.org/versions/.
Copy link
Contributor

@baku2san : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit c58afe6:

✅ Validation status: passed

File Status Preview URL Details
includes/functions-supported-languages.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@ttorble
Copy link
Contributor

ttorble commented Feb 28, 2025

@ggailey777

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants