test-worker 1.0.0a37

Python Language Worker for Azure Functions Runtime

Azure Functions Python Worker

Branch	Status	CodeCov	Unittests	E2E tests
main
dev

Python support for Azure Functions is based on Python 3.6, 3.7, 3.8, 3.9, and 3.10 serverless hosting on Linux and the Functions 2.0, 3.0 and 4.0 runtime.

Here is the current status of Python in Azure Functions:

What are the supported Python versions?

Azure Functions Runtime	Python 3.6	Python 3.7	Python 3.8	Python 3.9	Python 3.10	Python 3.11
Azure Functions 2.0 (deprecated)	✔	✔	-	-	-	-
Azure Functions 3.0 (deprecated)	✔	✔	✔	✔	-	-
Azure Functions 4.0	-	-	✔	✔	✔	✔

For information about Azure Functions Runtime, please refer to Azure Functions runtime versions overview page.

What's available?

• Build, test, debug and publish using Azure Functions Core Tools (CLI) or Visual Studio Code
• Deploy Python Function project onto consumption, dedicated, or elastic premium plan.
• Deploy Python Function project in a custom docker image onto dedicated, or elastic premium plan.
• Triggers / Bindings : HTTP, Blob, Queue, Timer, Cosmos DB, Event Grid, Event Hubs and Service Bus
• Triggers / Bindings : Custom binding support

What's coming?

• Durable Functions For Python

Get Started

• Create your first Python function
• Developer guide
• Binding API reference
• Develop using VS Code
• Create a Python Function on Linux using a custom docker image

Give Feedback

Issues and feature requests are tracked in a variety of places. To report this feedback, please file an issue to the relevant repository below:

Item	Description	Link
Python Worker	Programming Model, Triggers & Bindings	File an Issue
Linux	Base Docker Images	File an Issue
Runtime	Script Host & Language Extensibility	File an Issue
VSCode	VSCode Extension for Azure Functions	File an Issue
Core Tools	Command Line Interface for Local Development	File an Issue
Portal	User Interface or Experience Issue	File an Issue
Templates	Code Issues with Creation Template	File an Issue

Contribute

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

Here are some pointers to get started:

• Language worker architecture
• Setting up the development environment
• Adding support for a new binding
• Release instructions

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [e-mail] with any additional questions or comments.