Module 2: Python Fundamentals

In the picture above, it shows the code I wrote for this module running and working. The first line displays my last name. The lines under that is a dice game from pre-written code that I had to figure out the two errors in the code in order for the game to work properly. It rolls some dice and lets you know if you win, lose, or tie. 

The list underneath the dice game in the first picture is a randomized list the spits out 20 random numbers between 0 and 10. The flow chart for this code is located in the picture above. The code for this only goes to the first instance of print(luckyList). The rest of the flow chart displays the rest of the code for the last list in the first picture. This code removes a chosen integer (I choose 7) and will print out how many times the chosen number will be removed from the list. It then prints out the new list with the chosen integer removed from the list.

Notes:

1         Import math and random should be at the top of code to work correctly.

2         Indexing is very useful to find certain words or letters in a statement.

3         Breaks can end loops when they reach certain conditions designated in your code.

4         Str(var)+, +str(var)+ is how to add strings to statements that hold variables.

Module 1

 The output for 3 radians to degrees is 171.9745222929936 degrees.

My interpretation of Zen python by Tim Peters:

These are the principles of python by Tim Peters. Code needs to be easy to read. Your code needs to be understandable to someone who knows nothing about your program. Don’t overcomplicate your code. Keep your code as simple and readable as possible, even when working with complex problems. Stick to a flat code structure with minimal nesting. It’s preferable to have several easy-to-follow lines of code than a dense one-liner. In Python, there are lots of best practices that make your code more readable for other programmers follow these practices instead of doing it your way. If it’s more practical to solve a problem “your way” and it keeps code readable and easy-to-follow, you may sometimes deviate from established best practices. Deal with errors when they occur rather than letting them silently pass by, not dealing with errors could lead to bigger issues (unless you explicitly silenced the error). Apply critical thinking to understand the problem and then find an appropriate solution. If you can’t explain the implementation of your code to friends or coworkers it’s a bad code and probably over complicated the code. If you can easily explain the implementation of your code to friends and coworkers the code might be good. In Python, you can have isolated namespaces or a collection of names that allow each and every object in your program to have a unique name. Namespaces create a system where names in one of your modules are not conflicting with names in another making them very useful.

Process Summary Notes:

• CreateModFolders.py script creates 6 module folders each containing sub folders data, script, and results for this class to keep folders organized. (I ran it accidentally before starting the lab and noticed the folders before I started and just figured UWF added them to my folder somehow, but after reading through the lab I realized that it was me.)
• Print(“hello world”)- to print words you need “__” . 
• Print (sum)- variables do not need “__”
•  Flowcharts use certain symbols for each process of your code. 
• Pi is not known by computer so you must assign its value first before assuming the program knows pi.