Python worker for Azure Functions.
Перейти к файлу
AzureFunctionsPython 4c8527b85b Update Python SDK Version to 1.21.2 2024-10-09 15:45:08 +00:00
.ci/e2e_integration_test refactor: Added command line util for setting up tests (#1530) 2024-07-12 14:49:31 -05:00
.devcontainer refactor: Added command line util for setting up tests (#1530) 2024-07-12 14:49:31 -05:00
.github test: dev library testing based on branch name or variable (#1538) 2024-07-30 11:22:40 -05:00
azure_functions_worker build: update Python Worker Version to 4.33.0 (#1583) 2024-09-26 12:16:47 -05:00
docs Python 3.6 baggage code removal (#1419) 2024-02-13 13:08:40 -06:00
eng fix: code sign validation for setuptools (#1570) 2024-08-29 13:09:47 -05:00
pack remove unnecessary files from worker package (#1571) 2024-08-30 14:53:14 -05:00
python test: dev library testing based on branch name or variable (#1538) 2024-07-30 11:22:40 -05:00
tests fix: Fixed default threadpool count for pyver> 3.9 (#1575) 2024-09-18 09:42:20 -05:00
.artifactignore fix: changed target path for builds (#1544) 2024-07-24 14:38:08 -05:00
.coveragerc Adding new task in CI to report code-coverage in branches and PRs. (#668) 2020-05-01 15:24:13 -07:00
.flake8 Configure Precommit hooks with black and isort (#1416) 2024-01-31 16:16:14 -06:00
.gitignore Setting up dev as V4 branch for PyWorker (#936) 2022-02-04 14:35:36 -08:00
.pre-commit-config.yaml Configure Precommit hooks with black and isort (#1416) 2024-01-31 16:16:14 -06:00
CODEOWNERS python specific app setting logs added (#1353) 2023-11-14 15:32:30 -06:00
LICENSE Initial commit 2018-01-16 11:23:59 -08:00
MANIFEST.in CI fixes 2018-08-27 19:01:30 -04:00
README.md Docker tests updates (#1457) 2024-04-02 15:26:16 -05:00
SECURITY.md Microsoft mandatory file (#1053) 2022-06-21 16:44:51 -07:00
codecov.yml Docker e2e test fixes (#1192) 2023-04-26 23:02:11 -05:00
pyproject.toml Update Python SDK Version to 1.21.2 2024-10-09 15:45:08 +00:00
requirements.txt Simplify installation process 2018-03-05 09:25:04 -08:00
setup.cfg refactor: Added command line util for setting up tests (#1530) 2024-07-12 14:49:31 -05:00

README.md

Functions Header Image - Lightning Logo Azure Functions Python Worker

Branch Status CodeCov Unittests E2E tests
main Build Status codecov CI Unit tests CI E2E tests
dev Build Status codecov CI Unit tests CI E2E tests

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?

Get Started

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:

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 opencode@microsoft.com with any additional questions or comments.