Boston Python Workshop 3/Friday/Tutorial: Difference between revisions

Content added Content deleted
imported>Jesstess
imported>Jesstess
Line 693: Line 693:
A <b>function signature</b> tells you how the function will be called. It starts with the keyword <code>def</code>, which tells Python that you are defining a function. Then comes a space, the name of your function, an open parenthesis, the comma-separated input <b>parameters</b> for your function, a close parenthesis, and a colon. Here's what a function signature looks like for a function that takes no arguments:
A <b>function signature</b> tells you how the function will be called. It starts with the keyword <code>def</code>, which tells Python that you are defining a function. Then comes a space, the name of your function, an open parenthesis, the comma-separated input <b>parameters</b> for your function, a close parenthesis, and a colon. Here's what a function signature looks like for a function that takes no arguments:


⚫
<code>def myFunction():</code>
<pre>
⚫
def myFunction():
</pre>


Here's what a function signature looks like for a function that takes one argument called <code>string</code>:
Here's what a function signature looks like for a function that takes one argument called <code>string</code>:


⚫
<code>def myFunction(string):</code>
<pre>
⚫
def myFunction(string):
</pre>


And one for a function that takes two arguments:
And one for a function that takes two arguments:


⚫
<code>def myFunction(myList, myInteger):</code>
<pre>
⚫
def myFunction(myList, myInteger):
</pre>


Parameters should have names that usefully describe what they are used for in the function.
Parameters should have names that usefully describe what they are used for in the function.
Retrieved from "https://wiki.openhatch.org/wiki/Boston_Python_Workshop_3/Friday/Tutorial"