worker extensions disabled for python 3.13

Open
#1,759 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
azure, python
Domain
backend

Research direction

Start by reviewing the documentation and code referenced in the issue to confirm how custom worker extensions behave under Python 3.13. Determine whether future support or an alternative mechanism is intended, and document a supported migration path or the absence of one.

Written by the indexing model from the issue text.

Description

area:python-functions feature python

From the docs and the code here I can see that the usage of custom worker extensions is not longer supported in python 3.13. All of our function apps are heavily dependent on these extensions, making a transition to python 3.13+ not as straightforward.

Is this feature going to be supported again in the future (in this form or another like middleware or hooks) or should we look for other solutions for our extensions? If the latter is true, is there any migration path that can be followed?

Dominant language
Python
Stars
357
Forks
116
Avg merge
32m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-functions-python-worker

All issues in Azure/azure-functions-python-worker

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.