Boston Python Workshop 5/Friday

Welcome to the Friday evening section of the Boston Python Workshop!

When you get to MIT, please start your laptop and get on the wireless network. Try to join the one called "MIT", not "MIT GUEST". Then work through the goals on this page in order; they should take between 2 and 3 hours. Lots of staff will be around to help troubleshoot and to answer questions -- don't hesitate to ask!

At the end, a staff member will go through a checklist with you to make sure you're all set for tomorrow.

So we've established what you're wiilnlg to pay for as a consumer; it's service'.To get your business in the first place, there has to be someone to press the Big Red Switch when needed; and to keep your business, there has to be someone to install the latest Python. You don't need a guarantee that the Python will actually work; you'll take your own chances with that.I get the feeling there's going to be a bit of a culture clash when the Microsoft salesman shows up and tries selling you software'. Do keep us posted.

Goal #2: prepare a text editor
In addition to being able to run Python, we are going to install a good text editor for writing and saving Python code during the workshop.

If you would like to use a different text editor from the recommendation for your operating system, please let a staff member know.


 * Windows
 * OS X
 * Linux

Goal #3: practice starting and exiting Python
We'll do a lot of learning and practicing at a Python prompt (this is "interactive" because you are typing the code and hitting enter to run it yourself, instead of running it from a file). So let's practice starting and exiting Python:


 * Windows
 * OS X
 * Linux

Goal #4: practice navigating the computer from a command prompt
We will be running files containing Python code (Python "scripts") from the command prompt. You'll need to be able to navigate to those scripts using the command prompt so you can run them. In this section, we'll practice using these navigation commands.


 * Windows
 * OS X
 * Linux

Goal #5: practice running Python code from a file
Interactive Python programming at a Python prompt is great for short pieces of code and for testing ideas. For longer code, it can be easier to save the code in a file, and execute the contents of that file (aka a Python script). In this section, we'll practice running Python scripts.


 * Windows
 * OS X
 * Linux

Goal #6: get dependencies installed for the Saturday projects

 * Windows
 * OS X
 * Linux

Goal #7: start learning Python!
It's time to start learning, reading, and writing some Python! Tonight, you'll work through a self-directed tutorial. Saturday morning, we'll have an interactive lecture to cover more Python basics.

Work through the tutorial

Goal #8: Checkoff
Tell a staff member that you are ready to be checked off. Together you will go through the following check-off steps:

  Start a command prompt, and from that command prompt start Python. Then quit Python.   Create a new Python file (with a .py extension). In that file, type

print "Hello World"

and save the file. From a command prompt, navigate to and execute that Python script.   Open your text editor, and press "Tab". Use the left arrow key to show the instructor that you are using spaces to indent, not tabs.   To test the ColorWall installation: navigate to the ColorWall directory and run :

python run.py -a   To test the Wordplay installation: navigate to the Wordplay directory and run :

python words1.py  To test the Twitter installlation, navigate to the Twitter directory and run :

python twitter_api.py --search=python 

 What was the hardest part of the tutorial? How were the CodingBat questions? Review these parts briefly. If you have any questions about them, now's a great time to ask them!  

Hey Brock,Seems there are a few small errors with your sircpt. The most important one is that you'll want to have lines 59 and 60 all the way to the left, with no whitespace in front of it. Right now python will think these lines are still part of your class.Then in line 21 you'll need to use curly braces {} for your bl_options, rather than parenthesis .After doing this, the sircpt will not return any errors but the button won't show. This is because on line 13 the operator should be between quotation marks so that it reads layout.operator( object.random_material )On line 48 you made a small typo (availabeMaterials, instead of availableMaterials).Lastly, on line 50 you'll want to use square brackets [] instead of parenthesis to access the randnum key.These are all minor mistakes though, so don't get discouraged! =)