Python worker for Azure Functions.
Перейти к файлу
Hanzhang Zeng a3c047bb01
Categorize SDK logs as system logs (#850)
* Add testing for cases

* Amend expected behavior
2021-06-02 10:22:27 -07:00
.ci Generate E2E integration test report in Azure DevOps (#845) 2021-05-03 12:25:42 -07:00
.github Generate E2E integration test report in Azure DevOps (#845) 2021-05-03 12:25:42 -07:00
azure_functions_worker Categorize SDK logs as system logs (#850) 2021-06-02 10:22:27 -07:00
docs Add functions logo to readme 2019-09-04 12:05:22 -06:00
pack Add support for Windows Python 3.9 (#784) 2020-11-23 14:51:42 -08:00
python Changes for 3.9 along with nit fixes (pydoc comments, flaky tests) (#751) 2020-10-06 14:31:20 -07:00
tests Categorize SDK logs as system logs (#850) 2021-06-02 10:22:27 -07: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 Reduce logging for fn invocations (#749) 2020-10-02 12:46:36 -07:00
.gitignore Add E2E integration test pipeline (#829) 2021-03-17 14:17:25 -07:00
CODEOWNERS Add anatoli as code owner (#809) 2021-01-21 22:00:09 -08: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 Add python 3.9 to preview. Fix pipeline badges (#825) 2021-02-23 16:05:22 -08:00
azure-pipelines.yml [Integration Test] Generate worker artifact to AzureFunctionsPreRelease feed (#824) 2021-02-23 14:08:37 -08:00
requirements.txt Simplify installation process 2018-03-05 09:25:04 -08:00
setup.cfg Adding new task in CI to report code-coverage in branches and PRs. (#668) 2020-05-01 15:24:13 -07:00
setup.py [HotFix] Add shared_memory_data_transfer in setup.py 2021-04-05 13:18:07 -07:00

README.md

Functions Header Image - Lightning Logo Azure Functions Python Worker

Branch Status CodeCov Unittests E2E tests
master 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, Python 3.7, and Python 3.8, serverless hosting on Linux and the Functions 2.0 and 3.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
Azure Functions 2.0 - -
Azure Functions 3.0 (preview)

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.