Step 3: Conv r the s ud-Cod I..to Python You have your algorithm in pseudo-code and you have tested it on paper to confirm

Step 3: (:"I'IV r the T's ud-'--Cod I..to Python You have your algorithm in pseudocode and you have tested it on paper to conrm the API contract. Now. translate your pseudocode into Python. Create a Python le called I skip}: In this le, write a Python function called c overf_to_t3aesar0 which is the pseudocode translated to Python. Include internal documentation in your Python code as follows: ' at the top of your function, put in these comment lines: # Author: {you r name: # Date: {date that you wrote the code} ' Before the function. use comments to document the function's purpose and API. What does it do? What input[s} does it expect? What type of result does it retum? What will it do to the input{s}? What sorts of input count as had inputs? What will the function do with had inputs? ' Put comments before each main section of your function's Python code. Remember: a useful comment explains what you are doing and why. not how this is being done. A programmer can read the code and see how the code works, but they can't understand why you are doing it

Step 3: Conv r the s ud-Cod I..to Python You have your algorithm in pseudo-code and you have tested it on paper to confirm the API contract. Now, translate your pseudo-code into Python. Create a Python file called tisk1.py. In this file, write a Python function called c nvert_to_Caesar() which is the pseudo-code translated to Python. Include internal documentation in your Python code as follows: At the top of your function, put in these comment lines: #Author: # Date: Before the function, use comments to document the function's purpose and API. What does it do? What input(s) does it expect? What type of result does it return? What will it do to the input(s)? What sorts of input count as bad inputs? What will the function do with bad inputs? Put comments before each main section of your function's Python code. Remember: a useful comment explains what you are doing and why, not how this is being done. A programmer can read the code and see how the code works, but they can't understand why you are doing it.