This repository has been archived by the owner on Oct 28, 2019. It is now read-only.
forked from pystar/pystar
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding PyStar Paris, ordering events on homepage by upcoming date.
- Loading branch information
Showing
228 changed files
with
20,076 additions
and
5 deletions.
There are no files selected for viewing
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# Sphinx build info version 1 | ||
# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done. | ||
config: 07ff5492808139c311743a18bf1195c2 | ||
tags: fbb0d17656682115ca4d033fb2f83ba1 |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
About | ||
=========== | ||
|
||
Goal | ||
---- | ||
|
||
The PyStar program is workshop designed to teach | ||
women (including trans women) and their friends | ||
who are looking to learn how to program in a friendly non-alpha-geek | ||
environment. The goal is to increase the number | ||
of women programming, especially in Python which is | ||
a very approachable language to get started with. | ||
|
||
Pedagogy | ||
--------------- | ||
|
||
The approach for this workshop is to have groups learning together | ||
with at least one guide or instructor who can lead where needed, | ||
and help out as requested while participants work through the | ||
tutorials. There are several "badges" a learner can earn by learning to | ||
do various programming tasks. The badges have various levels of difficulty | ||
and the goal is to have modules that meet the learner where they are at. | ||
|
||
Future | ||
--------- | ||
|
||
As these workshops begin to happen it is hoped that attendees will | ||
come back as teaching assistants and eventually teach future workshops with the end goal | ||
of having former participants become the organizers for | ||
future workshops. There may be a disproportionate number of | ||
male teachers at initial workshops which is why we're encouraging participants | ||
to come back and take the lead as soon as they feel ready. | ||
|
||
Planning | ||
----------- | ||
|
||
If you're interested in organizing a workshop, working on the modules, | ||
or other discussions about teaching Python & programming to women, please | ||
join our Google group http://groups.google.com/group/pystar | ||
|
||
Contribute | ||
------------- | ||
|
||
You may have noticed our "Fork me on GitHub" banner - please do it! We would love for you | ||
to contribute badges/modules/typos corrections - anything to help make this as engaging | ||
and useful as a distributed workshop planning site can be. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
Learn Python the Hard Way Badge: Part 1 | ||
======================================== | ||
|
||
Read the intro and go through the first four exercises in *Learn Python the Hard Way* by Zed Shaw. | ||
|
||
The pdf can be downloaded using this link: http://learnpythonthehardway.org/static/LearnPythonTheHardWay.pdf or there might be paper copies available. | ||
|
||
**REMEMBER** to type in all the text by hand - don't copy and paste! And ask questions! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
Learn Python the Hard Way Badge: Part 2 | ||
======================================== | ||
|
||
Continue to go through the exercises in *Learn Python the Hard Way* by Zed Shaw. You will almost certainly not complete all 52 exercise in one day. Do as many as you want or have time for. Have fun! Ask questions! | ||
|
||
**REMEMBER** to type in all the text by hand - don't copy and paste! | ||
|
||
The pdf can be downloaded using this link: http://learnpythonthehardway.org/static/LearnPythonTheHardWay.pdf or there might be paper copies available. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,121 @@ | ||
Command Line Navigation Badge | ||
================================ | ||
|
||
This badge is to learn how to navigate using the command line (CLI). | ||
|
||
.. note: | ||
|
||
The command line is case sensitive. | ||
|
||
Commands | ||
-------- | ||
|
||
Commands used when navigating in the CLI: | ||
|
||
* cd | ||
* ls | ||
* mkdir | ||
* pwd | ||
|
||
Concepts | ||
--------- | ||
|
||
Navigation requires an understanding of the above commands and of file system paths, both relative and absolute. | ||
|
||
Absolute power corrupts absolutely | ||
.................................... | ||
|
||
Absolute paths are the full name to a file or directory starting from root. | ||
|
||
If I want to navigate to a folder in my Documents folder (on a Mac), the absolute path would look something like:: | ||
|
||
$ cd /Users/Amanda/Documents/Thesis/ | ||
|
||
It's all relative | ||
.................. | ||
|
||
Relative paths are partial path names relative to where you are in the directory structure. | ||
|
||
If I am in ``/Users/Amanda``, then the way to get to my Thesis folder using the relative path would look something like:: | ||
|
||
$ cd Documents/Thesis | ||
|
||
If I am in my Thesis folder and I want to move to a different folder within my Documents directory, I would do something like:: | ||
|
||
$ cd ../IF | ||
|
||
The double dot notation is shorthand for "go up a directory," which is this case is Documents. From there, I can then go down into my IF directory (and play some text adventure games). | ||
|
||
Here is a more complicated example: from my IF directory, I could get to a folder of pictures in my Pictures directory (absolute path: /Users/Amanda/Pictures/atlanta) by typing:: | ||
|
||
$ cd ../../Pictures/atlanta/ | ||
|
||
The first ``..`` takes me up to Documents, the second ``..`` takes me up to my user directory (Amanda) and from there I can go down into Pictures and then into atlanta. | ||
|
||
Do | ||
-- | ||
|
||
Open a command line window. Explore your file system in the CLI using the following commands and using absolute and relative path names: | ||
|
||
* ls | ||
* pwd | ||
* cd | ||
|
||
``ls`` means "list" and it will show you the list of files in the directory you are in. Try using some optional arguments such as ``-a``, ``-p``, or ``-l``. What do they show you that just running ``ls`` without arguments doesn't? | ||
|
||
``pwd`` means "print working directory," which is fairly self explainitory. Try typing it in different directories. What does it return? | ||
|
||
``cd`` means "change directory," which is also fairly self explainitory. Try typing in ``cd`` by itself. Where does it bring you? Try navigating to a directory within your files system and list the files in that directory. Use absolute and relative paths to visit several different directories on your file system. | ||
|
||
Done | ||
---- | ||
|
||
Here's an example of what your CLI screen might look like after completing the above work: | ||
|
||
.. code-block:: bash | ||
|
||
amanda-nyrens-macbook-pro:~ Amanda$ pwd | ||
/Users/Amanda | ||
amanda-nyrens-macbook-pro:~ Amanda$ ls | ||
Calibre Library Documents Icon? Movies Pictures Sites VirtualBox VMs | ||
Desktop Downloads Library Music Public Speelies mydir | ||
amanda-nyrens-macbook-pro:~ Amanda$ cd Desktop/ | ||
amanda-nyrens-macbook-pro:Desktop Amanda$ ls | ||
command.txt git-amanda pystar python | ||
amanda-nyrens-macbook-pro:Desktop Amanda$ ls -l | ||
total 424 | ||
-rw-rw-rw- 1 Amanda staff 213063 Jul 27 1999 command.txt | ||
drwxr-xr-x 6 Amanda staff 204 Mar 22 16:18 git-amanda | ||
drwxr-xr-x 7 Amanda staff 238 Apr 9 09:31 pystar | ||
drwxr-xr-x 33 Amanda staff 1122 Apr 9 09:23 python | ||
amanda-nyrens-macbook-pro:Desktop Amanda$ cd git-amanda/pystar_amanda/ | ||
amanda-nyrens-macbook-pro:pystar_amanda Amanda$ ls -a | ||
. .. .DS_Store .git README.rst docs utils web | ||
amanda-nyrens-macbook-pro:pystar_amanda Amanda$ pwd | ||
/Users/Amanda/Desktop/git-amanda/pystar_amanda | ||
amanda-nyrens-macbook-pro:pystar_amanda Amanda$ cd ../../../Documents/Thesis/ | ||
amanda-nyrens-macbook-pro:Thesis Amanda$ ls -lrt | ||
total 86920 | ||
-rwxrwxrwx@ 1 Amanda staff 24576 Oct 4 2005 thesis proposal.doc | ||
-rw-r--r--@ 1 Amanda staff 12562780 Feb 15 2006 ES2e-CH18.pdf | ||
-rw-rw---- 1 Amanda staff 4197 Mar 8 2006 thesis references-Converted.txt | ||
-rw-r--r--@ 1 Amanda staff 3475730 Mar 9 2006 chester_2003.pdf | ||
-rw-r--r--@ 1 Amanda staff 908091 Mar 9 2006 evaluating sand and clay models.pdf | ||
-rw-r--r--@ 1 Amanda staff 34304 Mar 19 2006 thesis budget.xls | ||
-rw-r--r--@ 1 Amanda staff 0 Mar 24 2006 Icon? | ||
-rw-r--r--@ 1 Amanda staff 37376 Mar 29 2006 Manuscript preparation WORD.doc | ||
-rw-r--r--@ 1 Amanda staff 31744 Mar 29 2006 Remaining Important Dates for Departmental Honors Students 2005-06.doc | ||
-rw-r--r--@ 1 Amanda staff 3064448 Apr 9 2006 storti salvini mcclay.pdf | ||
-rwxrwxrwx@ 1 Amanda staff 39424 Apr 13 2006 thrust analysis.xls | ||
-rw-r--r--@ 1 Amanda staff 9557504 Apr 30 2006 Thesis.doc | ||
drwxr-xr-x 38 Amanda staff 1292 Apr 30 2006 Images | ||
-rw-r--r--@ 1 Amanda staff 14669824 May 7 2006 thesis.ppt | ||
amanda-nyrens-macbook-pro:Thesis Amanda$ pwd | ||
/Users/Amanda/Documents/Thesis | ||
amanda-nyrens-macbook-pro:Thesis Amanda$ | ||
|
||
|
||
|
||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,88 @@ | ||
.. _badge_colorwall: | ||
|
||
========================================== | ||
Color Wall | ||
========================================== | ||
|
||
The ColorWall is a framework for implementing and displaying | ||
effects for a wall of pixels. During this workshop, you will write | ||
your own ColorWall and design effects for it. | ||
|
||
.. image:: /images/rainbow.png | ||
.. image:: /images/matrix.png | ||
.. image:: /images/twinkle.png | ||
|
||
You can also see the ColorWall in action here: http://vimeo.com/16522975. | ||
|
||
Download the files you will need here: | ||
|
||
- Linux/Mac Users | ||
- :download:`ColorWall.tar.gz </resources/ColorWall.tar.gz>` | ||
- :download:`WorkshopExercises.tar.gz </resources/WorkshopExercises.tar.gz>` | ||
- Windows Users | ||
- :download:`ColorWall.zip </resources/ColorWall.zip>` | ||
- :download:`WorkshopExercises.zip </resources/WorkshopExercises.zip>` | ||
|
||
|
||
Basic Programming | ||
----------------------------- | ||
First let's work through some basic terminal exercises to learn how | ||
we use Python to work with numbers & text. | ||
|
||
:ref:`Data Types <badge_python_data_types>` | ||
|
||
Workshop Exercises | ||
------------------------------ | ||
Unzip/Untar the workshop exercises and go through them. | ||
|
||
Layout | ||
----------- | ||
|
||
The ColorWall code consists of 3 files: | ||
|
||
- ``run.py`` -- takes arguments from your environment (like a specified width and height for the wall), set up the wall and effects, and run them. | ||
- ``wall.py`` -- the logic behind the matrix of squares that make up the wall. This file has a comment block at the top that summarize the interface that you will use when programming your own effects. | ||
- ``effects.py`` -- where effects live. This is the main file that you'll be editing during the workshop. | ||
|
||
Run the ColorWall | ||
--------------------------- | ||
If you want to try doing a git clone, you can grab | ||
the ColorWall code from `Git Hub <https://github.com/jesstess/ColorWall>`_ | ||
and run it from there, otherwise go into the directory that was created when | ||
you unzipped/untarred the ColorWall download. | ||
|
||
Run the example effects: | ||
|
||
|
||
On Windows, assuming the ColorWall software was downloaded to ``C:\Users\yourusername\Desktop\ColorWall`` | ||
|
||
.. code-block:: bash | ||
|
||
run \Python27\python.exe "C:\Users\yourusername\Desktop\colorwall\ColorWall\run.py" | ||
|
||
On OS X, assuming the ColorWall software was downloaded to ``~/Desktop/colorwall/ColorWall`` run | ||
|
||
.. code-block:: bash | ||
|
||
python ~/Desktop/colorwall/ColorWall/run.py | ||
|
||
On Linux, assuming the ColorWall software was downloaded to ``~/Desktop/colorwall/ColorWall`` run | ||
|
||
.. code-block:: bash | ||
|
||
python ~/Desktop/colorwall/ColorWall/run.py | ||
|
||
Other Resources | ||
------------------------- | ||
|
||
http://openhatch.org/wiki/Boston_Python_workshop/Friday_handout#Setting_up_the_ColorWall | ||
|
||
https://lsblakk@github.com/lsblakk/ColorWall.git ColorWall code on GitHub | ||
|
||
http://en.wikipedia.org/wiki/HSL_and_HSV has the | ||
explanation for what HSV color space means. What it boils down | ||
to for the purposes of our project is this: each pixel gets 3 | ||
values: hue (e.g. am I red, green, or blue), saturation | ||
(am I pale or intense), and value (am I bright or dark). | ||
effects.py has example effects that | ||
exercise hue, saturation, and value independently. |
Oops, something went wrong.