Boston Python Workshop 3/Friday: Difference between revisions
imported>Jesstess (Created page with 'Welcome to the Friday evening section of the Boston Python Workshop! Setup hours are from 6pm-9pm at [http://www.hubspot.com/company/contact/ HubSpot]. When you get to HubSpot, …') |
imported>Jesstess m (Protected "Boston Python Workshop 3/Friday" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))) |
||
| (24 intermediate revisions by 11 users not shown) | |||
Line 1:
Welcome to the Friday evening section of the Boston Python Workshop!
When you get to
At the end, a staff member will go through a checklist with you to make sure you're all set for tomorrow.
Line 9:
This section has instructions for installing Python and running Python from a command prompt.
* [[Boston Python
* [[Boston Python
* [[Boston Python
== Goal #2:
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.<br />
Line 19:
If you would like to use a different text editor from the recommendation for your operating system, please let a staff member know.
* [[Boston Python
* [[Boston Python
* [[Boston Python
== Goal #3: practice starting and exiting Python ==
Line 27:
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:
* [[Boston Python
* [[Boston Python
* [[Boston Python
== Goal #4: practice navigating the computer from a command prompt ==
Line 35:
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.
* [[Boston Python
* [[Boston Python
* [[Boston Python
== 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.
* [[Boston Python
* [[Boston Python
* [[Boston Python
== Goal #6: get dependencies installed for the Saturday projects ==
* [[Boston Python
* [[Boston Python
* [[Boston Python
== Goal #7: start learning Python! ==
Line 57 ⟶ 56:
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.
[[Boston Python
== Goal #8: Checkoff ==
Line 80 ⟶ 79:
<pre>
python run.py -a
</pre>
</li>
<li>
To test the Wordplay installation: navigate to the Wordplay directory and run <code>
<pre>
python
</pre>
</li>
Line 104 ⟶ 103:
If you have any questions, comments, or feedback on tonight's material, don't hesitate to let a staff member know.
[[Boston Python
| |||
Latest revision as of 12:59, 24 September 2011
Welcome to the Friday evening section of the Boston Python Workshop!
When you get to Google, please start your laptop and get on the wireless network. 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.
Goal #1: set up Python
This section has instructions for installing Python and running Python from a command prompt.
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.
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:
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.
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.
Goal #6: get dependencies installed for the Saturday projects
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.
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.
-
To test the ColorWall installation: navigate to the ColorWall directory and run
run.py:python run.py -a
-
To test the Wordplay installation: navigate to the Wordplay directory and run
words1.py:python words1.py
- To test the Twitter installlation, navigate to the Twitter directory and run
twitter_api.py:python twitter_api.py --search=python
Congratulations!
You are done with the Friday portion of this Workshop. We'll see you at 9:45am tomorrow back here at HubSpot! Please bring the laptop you used tonight.
If you have any questions, comments, or feedback on tonight's material, don't hesitate to let a staff member know.