Skip to content

Support for Python 3.13 #1588

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

Open
pykong opened this issue Oct 8, 2024 · 9 comments
Open

Support for Python 3.13 #1588

pykong opened this issue Oct 8, 2024 · 9 comments
Assignees

Comments

@pykong
Copy link

pykong commented Oct 8, 2024

Describe the request: A clear and concise description.
Well, make Azure Functions compatible with Python 3.13 :)

Also, see #1397

@Goldziher
Copy link

please do. we are still waiting for 3.12, so it would be good if this is on your radar as well.

@stevesimmons
Copy link

@hallvictoria Now that Python 3.12 support is done (#1397, thank you!), please can you indicate the target date for supporting Python 3.13?

@hallvictoria
Copy link
Contributor

@stevesimmons we are currently targeting this March.

@TJKlein
Copy link

TJKlein commented Apr 4, 2025

@stevesimmons we are currently targeting this March.

@hallvictoria : Any update on this?

@hallvictoria
Copy link
Contributor

We've hit some delays, and our updated preview target date is now May - June.

@polys
Copy link

polys commented Apr 9, 2025

@hallvictoria
Please, don't take this as criticism because I really do appreciate all the work done on Azure Functions, but could you explain why adding support for new Python versions is so difficult? This doesn't seem to be an issue with .NET, Node.js, etc.
It would be really helpful to understand any drawbacks with using Python on Azure Functions, just so we can make better decisions on language choice going forward.

@hallvictoria
Copy link
Contributor

Hi @polys, supporting a new Python version involves updating multiple components of our product, many of which depend on each other. These components have to be released in a specific order, and each follows its own schedule and can take a month+ to fully rollout. Even if our main worker code is ready on time, any delays or urgent fixes in other parts can hold up the overall release.

We completely understand how important it is to have access to the latest language versions, and we apologize for any inconvenience this delay may cause. We do prioritize this work, and our team is actively exploring ways to streamline the process and reduce wait times in the future.

Thanks for your patience and for continuing to share your feedback—it helps us improve.

@guimatheus92
Copy link

Any news on this one?

@hallvictoria
Copy link
Contributor

@guimatheus92 we are targeting mid-June for preview.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants