You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: code/function/getting_started.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
# Getting Started with Azure Functions in Python
2
-
2
+
3
3
4
4
## Python Programming Model V2
5
5
6
-
The new programming model in Azure Functions Python delivers an experience that aligns with Python development principles, and subsequently with commonly used Python frameworks.
6
+
The new programming model in Azure Functions Python delivers an experience that aligns with Python development principles, and subsequently with commonly used Python frameworks.
7
7
8
8
The improved programming model requires fewer files than the default model, and specifically eliminates the need for a configuration file (`function.json`). Instead, triggers and bindings are represented in the `function_app.py` file as decorators. Moreover, functions can be logically organized with support for multiple functions to be stored in the same file. Functions within the same function application can also be stored in different files, and be referenced as blueprints.
9
9
@@ -28,21 +28,21 @@ The main project folder (<project_root>) can contain the following files:
28
28
**local.settings.json*: Used to store app settings and connection strings when running locally. This file doesn't get published to Azure.
29
29
**requirements.txt*: Contains the list of Python packages the system installs when publishing to Azure.
30
30
**host.json*: Contains configuration options that affect all functions in a function app instance. This file does get published to Azure. Not all options are supported when running locally.
31
-
**blueprint.py*: (Optional) Functions that are defined in a separate file for logical organization and grouping, that can be referenced in `function_app.py`.
31
+
**blueprint.py*: (Optional) Functions that are defined in a separate file for logical organization and grouping, that can be referenced in `function_app.py`.
32
32
**.vscode/*: (Optional) Contains store VSCode configuration.
33
33
**.venv/*: (Optional) Contains a Python virtual environment used by local development.
34
34
**Dockerfile*: (Optional) Used when publishing your project in a custom container.
35
35
**tests/*: (Optional) Contains the test cases of your function app.
36
36
**.funcignore*: (Optional) Declares files that shouldn't get published to Azure. Usually, this file contains `.vscode/` to ignore your editor setting, `.venv/` to ignore local Python virtual environment, `tests/` to ignore test cases, and `local.settings.json` to prevent local app settings being published.
37
-
37
+
38
38
## Developing your first Python function using VS Code
39
39
40
40
If you have not already, please checkout our [quickstart](https://aka.ms/fxpythonquickstart) to get you started with Azure Functions developments in Python.
41
41
42
42
## Publishing your function app to Azure
43
-
43
+
44
44
For more information on deployment options for Azure Functions, please visit this [guide](https://docs.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-python#publish-the-project-to-azure).
45
45
46
46
## Next Steps
47
-
48
-
To learn more specific guidance on developing Azure Functions with Python, please visit [Azure Functions Developer Python Guide](https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-python?tabs=asgi%2Capplication-level).
47
+
48
+
To learn more specific guidance on developing Azure Functions with Python, please visit [Azure Functions Developer Python Guide](https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-python?tabs=asgi%2Capplication-level).
0 commit comments