|
| 1 | +# <img src="https://raw.githubusercontent.com/Azure/azure-functions-python-worker/dev/docs/Azure.Functions.svg" width = "30" alt="Functions Header Image - Lightning Logo"> Azure Functions Python Worker |
| 2 | + |
| 3 | +| Branch | Build Status | CodeCov | Test Status | |
| 4 | +|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
| 5 | +| dev | [](https://azfunc.visualstudio.com/public/_build/latest?definitionId=658&branchName=dev) | [](https://codecov.io/gh/Azure/azure-functions-python-worker) | [](https://azfunc.visualstudio.com/public/_build/latest?definitionId=658&branchName=dev) | |
| 6 | + |
| 7 | +Python support for Azure Functions is based on Python 3.13 serverless hosting on Linux and the Functions 4.0 runtime. |
| 8 | + |
| 9 | +Here is the current status of Python in Azure Functions: |
| 10 | + |
| 11 | +What are the supported Python versions? |
| 12 | + |
| 13 | +| Azure Functions Runtime | Python 3.13 | |
| 14 | +|----------------------------------|-------------| |
| 15 | +| Azure Functions 4.0 | ✔ | |
| 16 | + |
| 17 | +For information about Azure Functions Runtime, please refer to [Azure Functions runtime versions overview](https://docs.microsoft.com/en-us/azure/azure-functions/functions-versions) page. |
| 18 | + |
| 19 | +### What's available? |
| 20 | + |
| 21 | +- Build, test, debug, and publish using Azure Functions Core Tools (CLI) or Visual Studio Code |
| 22 | +- Deploy Python Function project onto consumption, dedicated, elastic premium, or flex consumption plan. |
| 23 | +- Deploy Python Function project in a custom docker image onto dedicated or elastic premium plan. |
| 24 | +- Triggers / Bindings : Blob, Cosmos DB, Event Grid, Event Hub, HTTP, Kafka, MySQL, Queue, ServiceBus, SQL, Timer, and Warmup |
| 25 | +- Triggers / Bindings : Custom binding support |
| 26 | + |
| 27 | +### What's new? |
| 28 | + |
| 29 | +- [SDK Type Bindings for Blob](https://techcommunity.microsoft.com/t5/azure-compute-blog/azure-functions-sdk-type-bindings-for-azure-blob-storage-with/ba-p/4146744) |
| 30 | +- [HTTP Streaming](https://techcommunity.microsoft.com/t5/azure-compute-blog/azure-functions-support-for-http-streams-in-python-is-now-in/ba-p/4146697) |
| 31 | + |
| 32 | +### Get Started |
| 33 | + |
| 34 | +- [Create your first Python function](https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-python) |
| 35 | +- [Developer guide](https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-python) |
| 36 | +- [Binding API reference](https://docs.microsoft.com/en-us/python/api/azure-functions/azure.functions?view=azure-python) |
| 37 | +- [Develop using VS Code](https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-vs-code) |
| 38 | +- [Create a Python Function on Linux using a custom docker image](https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-linux-custom-image) |
| 39 | + |
| 40 | +# Give Feedback |
| 41 | + |
| 42 | +Issues and feature requests are tracked in a variety of places. To report this feedback, please file an issue to the relevant repository below: |
| 43 | + |
| 44 | +| Item | Description | Link | |
| 45 | +|---------------|----------------------------------------------|--------------------------------------------------------------------------------| |
| 46 | +| Python Worker | Programming Model, Triggers & Bindings | [File an Issue](https://github.com/Azure/azure-functions-python-worker/issues) | |
| 47 | +| Runtime | Script Host & Language Extensibility | [File an Issue](https://github.com/Azure/azure-functions-host/issues) | |
| 48 | +| VSCode | VSCode Extension for Azure Functions | [File an Issue](https://github.com/microsoft/vscode-azurefunctions/issues) | |
| 49 | +| Core Tools | Command Line Interface for Local Development | [File an Issue](https://github.com/Azure/azure-functions-core-tools/issues) | |
| 50 | +| Templates | Code Issues with Creation Template | [File an Issue](https://github.com/Azure/azure-functions-templates/issues) | |
| 51 | + |
| 52 | +# Contribute |
| 53 | + |
| 54 | +This project welcomes contributions and suggestions. Most contributions require you to agree to a |
| 55 | +Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us |
| 56 | +the rights to use your contribution. For details, visit https://cla.microsoft.com. |
| 57 | + |
| 58 | +Here are some pointers to get started: |
| 59 | + |
| 60 | +- [Language worker architecture](https://github.com/Azure/azure-functions-python-worker/wiki/Worker-Architecture) |
| 61 | +- [Setting up the development environment](https://github.com/Azure/azure-functions-python-worker/wiki/Contributor-Guide) |
| 62 | +- [Adding support for a new binding](https://github.com/Azure/azure-functions-python-worker/wiki/Adding-support-for-a-new-binding-type) |
| 63 | +- [Release instructions](https://github.com/Azure/azure-functions-python-worker/wiki/Release-Instructions) |
| 64 | + |
| 65 | +When you submit a pull request, a CLA-bot will automatically determine whether you need to provide |
| 66 | +a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions |
| 67 | +provided by the bot. You will only need to do this once across all repos using our CLA. |
| 68 | + |
| 69 | +This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). |
| 70 | +For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or |
| 71 | +contact [[email protected]](mailto:[email protected]) with any additional questions or comments. |
0 commit comments