Skip to content

Commit 9a36afc

Browse files
authored
1 parent bef4557 commit 9a36afc

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/azure-functions/functions-reference-python.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -76,16 +76,16 @@ The recommended folder structure for a Python Functions project looks like the f
7676

7777
```
7878
__app__
79-
| - MyFirstFunction
79+
| - my_first_function
8080
| | - __init__.py
8181
| | - function.json
8282
| | - example.py
83-
| - MySecondFunction
83+
| - my_second_function
8484
| | - __init__.py
8585
| | - function.json
86-
| - SharedCode
87-
| | - myFirstHelperFunction.py
88-
| | - mySecondHelperFunction.py
86+
| - shared_code
87+
| | - my_first_helper_function.py
88+
| | - my_second_helper_function.py
8989
| - host.json
9090
| - requirements.txt
9191
tests
@@ -100,10 +100,10 @@ The main project folder (\_\_app\_\_) can contain the following files:
100100

101101
Each function has its own code file and binding configuration file (function.json).
102102

103-
Shared code should be kept in a separate folder in \_\_app\_\_. To reference modules in the SharedCode folder, you can use the following syntax:
103+
Shared code should be kept in a separate folder in \_\_app\_\_. To reference modules in the shared\_code folder, you can use the following syntax:
104104

105105
```python
106-
from __app__.SharedCode import myFirstHelperFunction
106+
from __app__.shared_code import my_first_helper_function
107107
```
108108

109109
To reference modules local to a function, you can use the relative import syntax as follows:
@@ -112,7 +112,7 @@ To reference modules local to a function, you can use the relative import syntax
112112
from . import example
113113
```
114114

115-
When deploying your project to a function app in Azure, the entire content of the *FunctionApp* folder should be included in the package, but not the folder itself. We recommend that you maintain your tests in a folder separate from the project folder, in this example `tests`. This keeps you from deploying test code with your app. For more information, see [Unit Testing](#unit-testing).
115+
When deploying your project to a function app in Azure, the entire content of the *function\_app* folder should be included in the package, but not the folder itself. We recommend that you maintain your tests in a folder separate from the project folder, in this example `tests`. This keeps you from deploying test code with your app. For more information, see [Unit Testing](#unit-testing).
116116

117117
## Triggers and Inputs
118118

0 commit comments

Comments
 (0)