e507a984a4
* Generate worker.py from different host config * Use worker path * Update proto packages with identity and shared * Add workerPath to parameters Co-authored-by: Maheer Iqbal <42051041+maiqbal11@users.noreply.github.com> |
||
|---|---|---|
| .ci | ||
| azure_functions_worker | ||
| docs | ||
| pack | ||
| python | ||
| tests | ||
| .flake8 | ||
| .gitignore | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.md | ||
| azure-pipelines-e2e.yml | ||
| azure-pipelines-nightly.yml | ||
| azure-pipelines.yml | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
README.md
| Branch | Status |
|---|---|
| master | |
| dev |
Overview
Python support for Azure Functions is based on Python3.6, serverless hosting on Linux and the Functions 2.0 runtime.
Here is the current status of Python in Azure Functions:
What's available?
- Build, test, debug and publish using Azure Functions Core Tools (CLI) or Visual Studio Code
- Triggers / Bindings : HTTP, Blob, Queue, Timer, Cosmos DB, Event Grid, Event Hubs and Service Bus
- Create a Python Function on Linux using a custom docker image
- Triggers / Bindings : Custom binding support
What's coming?
- Python 3.7 support
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 |
| 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
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.