29 |
30 | The slides are available [here](https://speakerdeck.com/pycon2017/amjith-ramanujam-awesome-command-line-tools).
31 |
32 | ### What is a Team Project
33 | Glad you asked! A team project is an hour long problem solving session where each team
34 | consists of four members of different expertise level. The teams are formed from the
35 | list of attendees of the project night.
36 |
37 |
38 | ### The Objective
39 | Our objective is to build an awesome command line application in Python3 that
40 | - allows creating list of people who want to participate in a team project
41 | - once the list is created, the program automatically creates teams of four
42 |
43 | ### A Balanced Team
44 | To keep the team composition balanced in terms of experience, we want every team
45 | to have two members with more experience than the other two.
46 | Measuring experience is very subjective and difficult, but we will keep it simple.
47 | We will rely on a (not very scientific) metic - lines of code written till date.
48 |
49 | We will create a list by taking names of people from tonight's RSVP list. Along with their name we will also include the number of lines of code that person has written till date in Python or an equivalent language. Imagine this as a tool that one of the organizers uses to checkin attendees as they start coming in on the day of Project Night.
50 |
51 | And yeah, this number of lines can be just a rough estimate. As a
52 | reference, the linux kernel is over 23 million lines of code!
53 |
54 | ### Bootstrap
55 | - If you are familiar with `git`, run
56 |
57 | git clone https://github.com/chicagopython/CodingWorkshops.git
58 |
59 | - If not, go to https://github.com/chicagopython/CodingWorkshops
60 | - Click on the Download Zip and unzip the file that gets downloaded
61 | - From your command line, change directory to the path where you have downloaded it.
62 | - On linux or OS X
63 |
64 | > cd path/to/CodingWorkshops/problems/py101/python_team_project/
65 |
66 | - On Windows
67 |
68 | > cd path\to\CodingWorkshops\problems\py101\python_team_project
69 |
70 |
71 | Here you will find the basic skeleton of the app under `app.py`. (after September 21, 2017)
72 |
73 | ### Set up virtualenv
74 | If you are using Linux or OS X, run the following to create a new virtualenv
75 |
76 | python3 -m venv venv
77 | source venv/bin/activate
78 | pip install -r requirements.txt
79 | python app.py
80 |
81 | On Windows, run the following
82 |
83 | python3 -m venv venv
84 | venv\Scripts\activate
85 | pip install -r requirements.txt
86 | python app.py
87 |
88 | [](https://asciinema.org/a/M1hP91h153PuOPEjVYbot6jPj)
89 |
90 | Next let's get started by looking into the code.
91 |
92 | ## Feature 0: Look into app.py
93 | app.py is the script contains some code to get you started.
94 | We will be using two external libraries for this
95 | program.
96 |
97 | python_prompt_toolkit
98 | meetup-api
99 |
100 | - `prompt_toolkit` makes it easy for building awesome command line apps
101 | - `meetup-api` provides us with the data for the meetup
102 | - `asciinema` which is also in the `requirements.txt` isn't strictly necessary and we'll talk about it last
103 |
104 | `execute` function is where you would be writing your application logic.
105 |
106 | You should not require to make changes to `main` and `get_names` functions. In an upcoming project nights we will dig into `get_names` and make changes to it.
107 |
108 | Next let's run app.py
109 |
110 | python3 app.py
111 |
112 | This should drop you to a prompt.
113 |
114 | >
115 |
116 | Type in something to that prompt.
117 |
118 | > Hola amigo
119 | > You issued: Hola amigo
120 |
121 | Try a few more
122 |
123 | > Gracias
124 | > You issued:Gracias
125 |
126 | You can now press the up arrow key and access the history of the commands you have issued. To exit out of the program, you can type Ctrl-D.
127 |
128 | >
129 | GoodBye!
130 |
131 | ### Feature 1: Implement the Add command
132 | Next let's create a command where the user of the program can register new participants to build up the list of users from whom teams will be formed.
133 |
134 | The command should look like the following
135 |
136 | add Attendee Edit
5 | 6 | 12 | 13 | 14 | {% endblock content %} -------------------------------------------------------------------------------- /problems/webdev/django_pn_tracker/django_pn_tracker/apps/challenges/templates/challenges/edit.html: -------------------------------------------------------------------------------- 1 | {% extends "base.html" %} 2 | 3 | {% block content %} 4 |Attendee Edit
5 | 6 | 12 | 13 | 14 | {% endblock content %} -------------------------------------------------------------------------------- /problems/webdev/django_pn_tracker/django_pn_tracker/apps/challenges/templates/challenges/list.html: -------------------------------------------------------------------------------- 1 | '{% extends "base.html" %} 2 | 3 | {% block content %} 4 |
5 |
34 | {% endblock content %}
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/apps/challenges/tests.py:
--------------------------------------------------------------------------------
1 | from django.test import TestCase
2 |
3 | # Create your tests here.
4 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/apps/challenges/urls.py:
--------------------------------------------------------------------------------
1 | from django.contrib import admin
2 | from django.urls import path
3 | from . import views
4 |
5 | ###################################
6 | # Add URLs to `urlpatterns` below #
7 | ###################################
8 | urlpatterns = [
9 |
10 | ]
11 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/apps/challenges/views.py:
--------------------------------------------------------------------------------
1 | from django.shortcuts import render, redirect, get_object_or_404
2 | from . import models, forms
3 |
4 |
5 | ########################################
6 | # Fill in all ###s in the views below. #
7 | # Uncomment the funcs when complete. #
8 | ########################################
9 |
10 | # def challenge_list(request):
11 | # template_name = ###
12 | # attendees = ###
13 | # context = ###
14 |
15 | # return render(request, template_name, context=context)
16 |
17 |
18 | # def challenge_add(request):
19 | # template_name = ###
20 | # form = forms.AttendeeEditForm()
21 | # #############################################
22 | # # Logic for capturing submitted information #
23 | # #############################################
24 | # context = {"form": form}
25 |
26 | # return render(request, template_name, context=context)
27 |
28 |
29 | # def challenge_edit(request, id):
30 | # attendee = get_object_or_404(models.AttendeeInfo, id=id)
31 | # template_name = ###
32 | # form = ###
33 | # #############################
34 | # # Logic for capturing edits #
35 | # #############################
36 | # context = {"form": form}
37 |
38 | # return render(request, template_name, context=context)
39 |
40 |
41 | # def challenge_delete(request, id):
42 | # attendee = ###
43 | # template_name = ###
44 | # form = ###
45 | # ######################################
46 | # # Logic for capturing delete request #
47 | # ######################################
48 | # context = ###
49 |
50 | # return ###
51 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/settings.py:
--------------------------------------------------------------------------------
1 | """
2 | Django settings for regcounter project.
3 |
4 | Generated by 'django-admin startproject' using Django 2.1.
5 |
6 | For more information on this file, see
7 | https://docs.djangoproject.com/en/2.1/topics/settings/
8 |
9 | For the full list of settings and their values, see
10 | https://docs.djangoproject.com/en/2.1/ref/settings/
11 | """
12 |
13 | import os
14 |
15 | # Build paths inside the project like this: os.path.join(BASE_DIR, ...)
16 | BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
17 |
18 |
19 | # Quick-start development settings - unsuitable for production
20 | # See https://docs.djangoproject.com/en/2.1/howto/deployment/checklist/
21 |
22 | # SECURITY WARNING: keep the secret key used in production secret!
23 | SECRET_KEY = 'l#_95to^c9ga0f5g$#j8t$j8ykrpk^&o=18qnj(!8i#dgrc3)_'
24 |
25 | # SECURITY WARNING: don't run with debug turned on in production!
26 | DEBUG = True
27 |
28 | ALLOWED_HOSTS = []
29 |
30 | #############################################################
31 | # Add 'django_pn_tracker.apps.challenges' to INSTALLED_APPS #
32 | #############################################################
33 |
34 | INSTALLED_APPS = [
35 | 'django.contrib.admin',
36 | 'django.contrib.auth',
37 | 'django.contrib.contenttypes',
38 | 'django.contrib.sessions',
39 | 'django.contrib.messages',
40 | 'django.contrib.staticfiles',
41 |
42 | 'django_pn_tracker.apps.challenges'
43 | ]
44 |
45 | MIDDLEWARE = [
46 | 'django.middleware.security.SecurityMiddleware',
47 | 'django.contrib.sessions.middleware.SessionMiddleware',
48 | 'django.middleware.common.CommonMiddleware',
49 | 'django.middleware.csrf.CsrfViewMiddleware',
50 | 'django.contrib.auth.middleware.AuthenticationMiddleware',
51 | 'django.contrib.messages.middleware.MessageMiddleware',
52 | 'django.middleware.clickjacking.XFrameOptionsMiddleware',
53 | ]
54 |
55 | ROOT_URLCONF = 'django_pn_tracker.urls'
56 |
57 | TEMPLATE_PATH = os.path.abspath(
58 | os.path.join(BASE_DIR, 'django_pn_tracker', 'templates'))
59 |
60 | TEMPLATES = [
61 | {
62 | 'BACKEND': 'django.template.backends.django.DjangoTemplates',
63 | 'DIRS': [TEMPLATE_PATH],
64 | 'APP_DIRS': True,
65 | 'OPTIONS': {
66 | 'context_processors': [
67 | 'django.template.context_processors.debug',
68 | 'django.template.context_processors.request',
69 | 'django.contrib.auth.context_processors.auth',
70 | 'django.contrib.messages.context_processors.messages',
71 | ],
72 | },
73 | },
74 | ]
75 |
76 | WSGI_APPLICATION = 'django_pn_tracker.wsgi.application'
77 |
78 | ##############################
79 | # Add database settings here #
80 | ##############################
81 | # https://docs.djangoproject.com/en/2.1/ref/settings/#databases for help
82 |
83 | ################################
84 | # Add password validation here #
85 | ################################
86 | # https://docs.djangoproject.com/en/2.1/ref/settings/#auth-password-validators
87 |
88 | ################################
89 | # Add Internationalization here #
90 | ################################
91 | # https://docs.djangoproject.com/en/2.1/topics/i18n/
92 |
93 | LANGUAGE_CODE = 'en-us'
94 |
95 | TIME_ZONE = 'UTC'
96 |
97 | USE_I18N = True
98 |
99 | USE_L10N = True
100 |
101 | USE_TZ = True
102 |
103 |
104 | # Static files (CSS, JavaScript, Images)
105 | # https://docs.djangoproject.com/en/2.1/howto/static-files/
106 |
107 | STATIC_URL = '/static/'
108 |
109 | STATIC_PATH = os.path.abspath(
110 | os.path.join(BASE_DIR, 'django_pn_tracker', 'static'))
111 |
112 | STATICFILES_DIRS = [
113 | STATIC_PATH,
114 | ]
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/static/js/main.js:
--------------------------------------------------------------------------------
1 | (function ($, win, UNDEFINED) {
2 |
3 | $(".nav-list-expandable.nav-list-expanded > ul:eq(0)").show();
4 |
5 | $(".nav-list-expandable > a").click(function() {
6 | var a = $(this),
7 | li = a.parent(),
8 | ul = li.children('ul').first();
9 |
10 | if (ul.length > 0) {
11 | if (ul.is(":visible")) {
12 | li.removeClass("nav-list-expanded");
13 | ul.slideUp(150);
14 | }
15 | else {
16 | li.addClass("nav-list-expanded");
17 | ul.slideDown(250);
18 | }
19 | }
20 | });
21 |
22 | })(jQuery, this);
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/templates/base.html:
--------------------------------------------------------------------------------
1 | {% load staticfiles %}
2 |
3 |
4 |
5 |
6 |
9 |
33 |
10 | Add
11 |
12 |
13 |
27 |
31 |
32 | | Date | 15 |Participant Name | 16 |Challenge | 17 |Skill Level | 18 |Actions | 19 |
|---|---|---|---|---|
27 |
62 |
63 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
97 |
98 |
99 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/templates/index.html:
--------------------------------------------------------------------------------
1 | {% extends "base.html" %}
2 |
3 | {% block content %}
4 |
64 |
71 |
72 |
65 |
66 | {% block content %} {% endblock %}
67 |
68 |
69 |
70 |
5 |
13 |
14 | {% endblock content %}
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/urls.py:
--------------------------------------------------------------------------------
1 | """regcounter URL Configuration
2 |
3 | The `urlpatterns` list routes URLs to views. For more information please see:
4 | https://docs.djangoproject.com/en/2.1/topics/http/urls/
5 | Examples:
6 | Function views
7 | 1. Add an import: from my_app import views
8 | 2. Add a URL to urlpatterns: path('', views.home, name='home')
9 | Class-based views
10 | 1. Add an import: from other_app.views import Home
11 | 2. Add a URL to urlpatterns: path('', Home.as_view(), name='home')
12 | Including another URLconf
13 | 1. Import the include() function: from django.urls import include, path
14 | 2. Add a URL to urlpatterns: path('blog/', include('blog.urls'))
15 | """
16 | from django.contrib import admin
17 | from django.urls import path, include
18 | from django_pn_tracker import views
19 |
20 |
21 | urlpatterns = [
22 | path('admin/', admin.site.urls),
23 | path('', views.index, name='index'),
24 | path('challenges/', include('django_pn_tracker.apps.challenges.urls')),
25 | ]
26 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/views.py:
--------------------------------------------------------------------------------
1 | from django.shortcuts import render
2 |
3 | def index(request):
4 | template_name = "index.html"
5 | context = {}
6 | return render(request, template_name, context=context)
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/django_pn_tracker/wsgi.py:
--------------------------------------------------------------------------------
1 | """
2 | WSGI config for regcounter project.
3 |
4 | It exposes the WSGI callable as a module-level variable named ``application``.
5 |
6 | For more information on this file, see
7 | https://docs.djangoproject.com/en/2.1/howto/deployment/wsgi/
8 | """
9 |
10 | import os
11 |
12 | from django.core.wsgi import get_wsgi_application
13 |
14 | os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'regcounter.settings')
15 |
16 | application = get_wsgi_application()
17 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/manage.py:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env python
2 | import os
3 | import sys
4 |
5 | if __name__ == '__main__':
6 | os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'django_pn_tracker.settings')
7 | try:
8 | from django.core.management import execute_from_command_line
9 | except ImportError as exc:
10 | raise ImportError(
11 | "Couldn't import Django. Are you sure it's installed and "
12 | "available on your PYTHONPATH environment variable? Did you "
13 | "forget to activate a virtual environment?"
14 | ) from exc
15 | execute_from_command_line(sys.argv)
16 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/requirements.txt:
--------------------------------------------------------------------------------
1 | django==2.1
2 |
--------------------------------------------------------------------------------
/problems/webdev/django_pn_tracker/setup.cfg:
--------------------------------------------------------------------------------
1 | [flake8]
2 | ignore = D203
3 | exclude = .git,__pycache__,docs/source/conf.py,old,build,dist,*/migrations/*
4 | max-complexity = 10
5 | max-line-length=99
6 |
--------------------------------------------------------------------------------
/problems/webdev/django_rest_framework_api/Pipfile:
--------------------------------------------------------------------------------
1 | [[source]]
2 | name = "pypi"
3 | url = "https://pypi.org/simple"
4 | verify_ssl = true
5 |
6 | [dev-packages]
7 |
8 | [packages]
9 | Django = "~=2.2.6"
10 | djangorestframework = "~=3.10.3"
11 |
12 |
13 | [requires]
14 | python_version = "3.7"
--------------------------------------------------------------------------------
/problems/webdev/django_rest_framework_api/Pipfile.lock:
--------------------------------------------------------------------------------
1 | {
2 | "_meta": {
3 | "hash": {
4 | "sha256": "170332a1bcaeaed6de494dfff1768c99e7787199909f96206652f2ce0f2f2bc8"
5 | },
6 | "pipfile-spec": 6,
7 | "requires": {
8 | "python_version": "3.7"
9 | },
10 | "sources": [
11 | {
12 | "name": "pypi",
13 | "url": "https://pypi.org/simple",
14 | "verify_ssl": true
15 | }
16 | ]
17 | },
18 | "default": {
19 | "django": {
20 | "hashes": [
21 | "sha256:16040e1288c6c9f68c6da2fe75ebde83c0a158f6f5d54f4c5177b0c1478c5b86",
22 | "sha256:89c2007ca4fa5b351a51a279eccff298520783b713bf28efb89dfb81c80ea49b"
23 | ],
24 | "index": "pypi",
25 | "version": "==2.2.7"
26 | },
27 | "djangorestframework": {
28 | "hashes": [
29 | "sha256:5488aed8f8df5ec1d70f04b2114abc52ae6729748a176c453313834a9ee179c8",
30 | "sha256:dc81cbf9775c6898a580f6f1f387c4777d12bd87abf0f5406018d32ccae71090"
31 | ],
32 | "index": "pypi",
33 | "version": "==3.10.3"
34 | },
35 | "pytz": {
36 | "hashes": [
37 | "sha256:1c557d7d0e871de1f5ccd5833f60fb2550652da6be2693c1e02300743d21500d",
38 | "sha256:b02c06db6cf09c12dd25137e563b31700d3b80fcc4ad23abb7a315f2789819be"
39 | ],
40 | "version": "==2019.3"
41 | },
42 | "sqlparse": {
43 | "hashes": [
44 | "sha256:40afe6b8d4b1117e7dff5504d7a8ce07d9a1b15aeeade8a2d10f130a834f8177",
45 | "sha256:7c3dca29c022744e95b547e867cee89f4fce4373f3549ccd8797d8eb52cdb873"
46 | ],
47 | "version": "==0.3.0"
48 | }
49 | },
50 | "develop": {}
51 | }
52 |
--------------------------------------------------------------------------------
/problems/webdev/django_rest_framework_api/README.md:
--------------------------------------------------------------------------------
1 | # Build an API with Django REST Framework
2 |
3 | ## Overview
4 | For this project, we will be creating a functioning REST API. REST APIs can help distribute useful information via GET requests, as well as post and alter databases in a user friendly fashion.
5 |
6 | This project will revolve around using Django and Django's REST framework to build an API for the dataset of your choice. Django is a full web framework capable of handling both back and front end portions of a web app; and the Django team has created great resources to make setting up a Django app quick and easy.
7 |
8 | While the project is structured around Django, feel free to use flask instead, if you're more comfortable.
9 |
10 | ## Environment Setup
11 | To avoid bloating of your primary working environment, we strongly recommend creating a virtual environment. The requirements.txt file includes the required packages, and the included versions have been tested for our needs - use different versions at your own risk.
12 |
13 | We also strong recommend using [Atom](https://atom.io/) or [Sublime Text](https://www.sublimetext.com/3) as your text editor. This project has also NOT been tested using Jupyter Notebook, PyCharm,
14 | Spider, or any other ide/text editor/programming environment.
15 |
16 | 1. For this challenge you will need Python 3.7, pipenv, and git installed. If you're not familiar with pipenv, it's a packaing tool for Python that effectively replaced the pip+virtualenv+requirements.txt workflow. If you already have pip installed, the easiest way to install pipenv is with `pip install --user pipenv`; however, a better way for Mac/Linux Homebrew users is to instead run `brew install pipenv`. More options can be found [here](https://pipenv-fork.readthedocs.io/en/latest/install.html#installing-pipenv).
17 |
18 | 2. The project is in the ChiPy project night repo. If you do not have the repository already, run
19 |
20 | ```
21 | git clone https://github.com/chicagopython/CodingWorkshops.git
22 | ```
23 |
24 | 3. Navigate to the folder for this challenge:
25 |
26 | ```
27 | cd CodingWorkshops/problems/webdev/django_rest_framework_api
28 | ```
29 |
30 | 4. Run `pipenv install`, which will install all of the libraries we have recommended for this exercise.
31 | 5. After you've installed all of the libraries, run `pipenv shell`, which will turn on a virtual environment running Python 3.7.
32 | 6. To exit the pipenv shell when you are done, simply type `exit`.
33 |
34 | ## Instructions
35 |
36 | ### Find a Database
37 | - Before advancing, find a database that you wish to use for a REST API. It helps if the data is something you are interested in, but don't waste too much time on this part. [Kaggle](https://www.kaggle.com/tags/databases) has a great selection of publicly available databases. If you are looking for something specific, Google has a stellar [database search](https://toolbox.google.com/datasetsearch) feature.
38 |
39 | ### Create Your First App
40 |
41 | - Create a Django app in a local directory of your choosing. Feel free to use the [Django tutorial]((https://docs.djangoproject.com/en/2.2/intro/tutorial01/)) to accomplish this, but please don't call your app the standard Polls App. Create a unique application inside of your Django directory to handle your database and models. Make sure the application is configured in your settings.py file!
42 |
43 | ### Create a Django Model
44 | - Create a Django model custom to your database. Feel free to take liberties like creating relational databases for your models. The model field types should match the intended fields of your database. Make sure to migrate your Django model when you are finished!
45 |
46 | ### Configure the REST framework
47 | - Make sure you appropriately configure Django REST Framework in your settings.py file. If you forget this step, Django to recognize the add on.
48 |
49 | ### Serialization
50 | - Before creating a url or view, serialize your data. This allows Django to render data into a JSON format. Make sure you designate the table (model) and fields (features) you wish to include in your REST API.
51 |
52 | ### Create a View
53 | - Use the standard Django REST framework to create your Django view. Django REST framework allows you to interact with your API in both JSON and a preset interactive template. If you feel like going the extra mile, make your database queryable to gather the information you need.
54 |
55 | ### Designating a URL
56 | - Finally, designate url addresses where your page views can be found. Make sure to create a URL scheme that makes sense to how the intended user will interact with your API.
57 |
58 | ### Running your Server
59 | - At this point it is time to test your API. This can be accomplished by the manage.py runserver command. Django's default location is localhost:8000/. From there, follow the naming scheme you created in your urls. Feel free to play with your API by using those filterable features you created!
60 |
61 |
62 | ## Useful Weblinks
63 |
64 |
65 | - Django Startup and Features
66 |
67 | https://docs.djangoproject.com/en/2.2/intro/tutorial01/
68 |
69 | https://docs.djangoproject.com/en/2.2/ref/applications/
70 |
71 | - Django Models
72 |
73 | https://docs.djangoproject.com/en/2.2/ref/models/fields/
74 |
75 | https://docs.djangoproject.com/en/2.2/topics/db/models/#automatic-primary-key-fields
76 |
77 | - Django REST Framework
78 |
79 | https://www.django-rest-framework.org/#installation
80 |
81 | - Serialization
82 |
83 | https://www.django-rest-framework.org/api-guide/serializers/#modelserializer
84 |
85 | https://www.django-rest-framework.org/api-guide/serializers/#specifying-read-only-fields
86 |
87 | - Views and URLS
88 |
89 | https://www.django-rest-framework.org/tutorial/quickstart/#views
90 |
91 | https://www.django-rest-framework.org/tutorial/quickstart/#urls
--------------------------------------------------------------------------------
/problems/webdev/flask_collage/README.md:
--------------------------------------------------------------------------------
1 | Build a small web app using Flask which accepts the meetup.com event id for tonight
2 | as a parameter and would fetch the profile pictures of all the attendees to create a
3 | collage. [Here](https://twitter.com/Tathagata/status/746302962830540801) is an example
4 | of such a collage.
5 |
6 | You'll need:
7 |
8 | - `pip install flask`
9 | - `pip install Flask-WTF`
10 | - `pip install meetup-api`
11 |
12 | How to create a basic Flask app:
13 | Follow the instructions [here](http://flask.pocoo.org/docs/0.11/quickstart/)
14 |
15 | ```python
16 | from flask import Flask
17 | app = Flask(__name__)
18 |
19 | @app.route('/')
20 | def hello_world():
21 | return 'Hello World!'
22 |
23 | if __name__ == '__main__':
24 | app.run(debug=True)
25 | ```
26 | `python testflask.py`
27 |
28 | To get you started, the following piece of code will help you fetch the thumbnail
29 | images from meetup.com.
30 |
31 | ```python
32 | import meetup.api
33 | client = meetup.api.Client('your_key')
34 |
35 | rsvps=client.GetRsvps(event_id='235484841', urlname='_ChiPy_')
36 | member_id = ','.join([str(i['member']['member_id']) for i in rsvps.results])
37 | members = client.GetMembers(member_id=member_id)
38 |
39 | for member in members.results:
40 | try:
41 | print '{0},{1},{2}'.format(member['name'], member['id'], member['photo']['thumb_link'])
42 | except:
43 | pass # ignore those who do not have a complete profile
44 | ```
45 |
46 | 1. Can you include the name along with the images in your collage?
47 |
48 | 2. Add a search box to your collage, where you can search some one by name.
49 | On a successful search, it should display that person and their name. On failure, it should give a proper error message.
50 |
51 | 3. Add the following list of questions to your search result page that collects feedback on what an attendee would like to do
52 |
53 | Choices:
54 | - Help others with Python 101 questions
55 | - Help others with Python Data Science questions
56 | - Help others with Python Web Dev questions
57 | - Python 101 course (Beginner)
58 | - Attend Coding Workshop (Intermediate)
59 | - Attend RasberryPi Lab (Intermediate)
60 | - Work on my own project, get help from others
61 |
62 | 4. Deploy your app to a public hosting, share the link with the world!
63 |
64 | 5. Currently we are accepting RSVPs on both ChiPy's site and Chicago Pythonista's
65 | meetup page. Can you fetch the thumbnails from both the pages, eliminate the
66 | duplicates, and merge them to generate the collage?
67 |
68 |
--------------------------------------------------------------------------------
/problems/webdev/flask_collage/solutions/dormamu_bargain/README.md:
--------------------------------------------------------------------------------
1 | Team Name: Dormamu I've come to bargain
2 | =======================================
3 | * Dr. Strange
4 | * The Ancient One
5 | * Dormammu
6 | * Thanos
7 |
8 | Our Solution
9 | ============
10 | Take over.
11 |
12 |
--------------------------------------------------------------------------------
/problems/webdev/flask_collage/solutions/testflask.py:
--------------------------------------------------------------------------------
1 | from flask import Flask
2 | app = Flask(__name__)
3 | import meetup.api
4 |
5 | def get_names():
6 | client = meetup.api.Client('3f6d3275d3b6314e73453c4aa27')
7 |
8 | rsvps=client.GetRsvps(event_id='235484841', urlname='_ChiPy_')
9 | member_id = ','.join([str(i['member']['member_id']) for i in rsvps.results])
10 | members = client.GetMembers(member_id=member_id)
11 |
12 | foo=''
13 | for member in members.results:
14 | try:
15 |
16 | foo+='''17 | {0}
18 | Solo
19 | Team
20 | Line count: 21 |
'''.format(member['name'], member['id'], member['photo']['thumb_link']) 22 | except: 23 | pass # ignore those who do not have a complete profile 24 | 25 | return foo 26 | 27 | @app.route('/') 28 | def hello_world(): 29 | html = '' 30 | return html 31 | 32 | if __name__ == '__main__': 33 | app.run(debug=True) 34 | 35 | 36 | 37 | 38 | -------------------------------------------------------------------------------- /problems/webdev/flask_exchange_rates/README.md: -------------------------------------------------------------------------------- 1 | # Mentorship Program Web Project 2 | 3 | ## Objective 4 | All developers in the modern day need to understand web technologies at some level. Whether you're interacting with a Jupyter notebook or querying a web api, understanding how a CLIENT requests information from a SERVER and to see how the SERVER produces its response is incredibly valuable. 5 | 6 | 7 | ## Overview 8 | We will make a web app that serves as both a CLIENT to an external api (exchangeratesapi.io). This app will show conversion rates for currencies, and then add some more complex data. 9 | 10 | 11 | ## Prerequisites 12 | For this project we recommend all use Atom (or Sublime) to write code and a shell/terminal to execute the program. All instructions will be given assuming a Python 3.6 install. 13 | 14 | You should probably have the [Flask documentation](http://flask.pocoo.org/docs/1.0/quickstart/) up as we go through the exercise. 15 | 16 | 17 | ## Initial Setup 18 | 19 | Create a folder for this project: `mkdir mentorship_web && cd mentorship_web` 20 | 21 | If you are using Linux or OS X, run the following to create a new virtualenv 22 | 23 | ``` 24 | python3 -m venv venv 25 | source venv/bin/activate 26 | ``` 27 | 28 | On Windows, run the following 29 | 30 | ``` 31 | python3 -m venv venv 32 | venv\Scripts\activate 33 | ``` 34 | 35 | Install Flask, our main web-app: `pip install flask` 36 | 37 | Create a new file called `app.py` 38 | 39 | ``` 40 | from flask import Flask 41 | app = Flask(__name__) 42 | 43 | 44 | @app.route('/') 45 | def hello_world(): 46 | return "Hello World!" 47 | 48 | if __name__ == '__main__': 49 | app.run(debug=True) 50 | ``` 51 | 52 | Run your flask app: `python app.py` 53 | 54 | It should display a link, paste that in your browser to see the running code. 55 | 56 | 57 | ## Display some Exchange Rates 58 | 59 | Define a dictionary with three entries like the following inside your hello route: 60 | 61 | ``` 62 | exchange_rates = { 63 | 'EUR': '...', 64 | 'GBP': '...', 65 | ' 66 | ``` 67 | 68 | Pick any currencies you want! We'll display the values as they convert to USD (because we are in Chicago). Better specify that now for clarity. Add this line just bellow your `app =` definition, we'll use it later: 69 | 70 | ``` 71 | BASE_CURRENCY = 'USD' 72 | ``` 73 | 74 | Of course, fill in the `...` with real currency values, otherwise our site is pointless! Use a tool like [X-Rates](https://www.x-rates.com/table/?from=USD&amount=1) to look up the currency conversions. 75 | 76 | Now update the return string in the hello route to include the information about these currencies. 77 | 78 | 79 | ## Make it Beautiful 80 | Returning strings is fine...I suppose. But I want big, beautiful HTML! Research Flask's [`render_template` function](http://flask.pocoo.org/docs/1.0/quickstart/#rendering-templates) and add some beautiful looking HTML to format your. Hint: You'll want to create a `templates/` folder in the same directory as your `app.py`, and if you aren't using a kind of loop in your template...it's going to get real tough for you later! 81 | 82 | Test your work by adding another currency to your `exchange_rates` dictionary and watch how your page changes. 83 | 84 | ## Refactor 85 | Define a function right under your `BASE_CURRENCY` definition that looks like the following: 86 | 87 | ``` 88 | def exchange_rates(): 89 | return # Move your dictionary here 90 | ``` 91 | 92 | Then replace any references in your code to use the function instead of defining the dictionary in your route! 93 | 94 | ## Automatic Data 95 | Now comes the fun part. What if we could get the exchange rates on a live feed from a third party service? We can with [ExchangeRatesAPI.io](http://exchangeratesapi.io). This is a free api that runs over simple HTTPS! We'll have something like the following: 96 | 97 | ``` 98 | def exchange_rates(): 99 | response = requests.get('https://api.exchangeratesapi.io/latest') 100 | return # What are we going to put here now? 101 | ``` 102 | 103 | Read up on [Requests' built in JSON Parsing](http://docs.python-requests.org/en/master/user/quickstart/#json-response-content) and try to extract the data from the API response. Your end goal is to return all of the 104 | currencies from this function. 105 | 106 | Hint: This problem is a great time to use the Python debugger ([`pdb`](https://docs.python.org/3/library/pdb.html))! Insert the following line before the `return` command and interact with your server on the command line. So cool! 107 | 108 | ``` 109 | import pdb; pdb.set_trace() 110 | ``` 111 | 112 | ### Correct Currency 113 | Are we sure the previous step is getting us the currency in our `BASE_CURRENCY` variable? Investigate the [api docs](http://exchangeratesapi.io) to find out how you can change the base currency to the one we want. 114 | 115 | 116 | # You DID it! Now what? 117 | From here on out we are trusting that you can use the documentation, look for resources on your own, and come up with clever solutions to these problems. Try each one, and if you get stuck, move on to a different one! Ask for help if you want more clarification or can't think of a way to do it. 118 | 119 | 120 | ## Information Overload 121 | Could we provide a form that would let people get only the currency they want? I don't need every currency. We'd probably use some kind of html form. And I bet Flask has some documentation on receiving requests from the client. 122 | 123 | e.g. Instead of `JPY->*` I only want to see `USD->GBP` or I only want to see `USD->JPY`. 124 | 125 | 126 | ## Order by Value 127 | How could we order the currencies by the value of the currency? 128 | 129 | e.g. If something is `.00001 USD`, lets list that last, and if something is `987654321 USD` lets list that first. 130 | 131 | 132 | ## User-Specified Base Currency 133 | Some users of our product have complained, rightfully, that they can only get the currency listed in `USD`. We should let them specify what currency they want. 134 | 135 | e.g. Instead of `USD->*` I want to see `CNY->*` 136 | 137 | ### Bonus: Links to each user-specified currency from the currency list 138 | Wouldn't it be great if each currency as it appeared would link to its own currency conversion? 139 | 140 | e.g. From the home page I could click on `JPY` to find out all of the conversions from `JPY->*`. 141 | 142 | 143 | ## Caching 144 | Do we really need to use an API request every time we do a call? How could we store the results of each run to avoid API abuse. -------------------------------------------------------------------------------- /problems/webdev/flask_team_project/README.md: -------------------------------------------------------------------------------- 1 | In this project we will be building a fully functional web app using 2 | Flask. 3 | 4 | ### The project 5 | In the [team project command line application](https://github.com/chicagopython/CodingWorkshops/tree/master/problems/py101/python_team_project), we built an awesome command line 6 | application for creating teams out of people who have RSVP-ed for a Python Project 7 | Night. However, it is much easier to give a link of your app to someone 8 | than asking them to use a command line. So, we will create a web app, that allows 9 | forming teams from the list of RSVP-s from meetup.com. We 10 | will ask for the number of lines of code that a person has written in 11 | Python or an equivalent language and use it for putting them in a team. The number of lines is just a rough estimate. As a reference, the linux kernel is over 23 million lines of code! 12 | 13 | In short, imagine this as a tool that one of the 14 | organizers uses to checkin attendees as they start coming in on the day of 15 | Project Night. 16 | 17 | Short url for this page: **https://git.io/vdQj6** 18 | 19 | ### Is this project for you 20 | Before you progress further, let's check if we are ready to solve this. You should 21 | - Have a personal computer with working wifi and power cord 22 | - Have Python 3 installed on your computer. Yep, Python 3 only. 23 | - Have [Atom](https://atom.io/) or [Sublime Text](https://www.sublimetext.com/3) installed in your computer. 24 | - Have written & ran programs in Python from the command line 25 | - Have some idea about lists, dictionaries and functions 26 | - Have created a virtual environment and installing packages with `pip` 27 | - You have read the [flask quick introduction](http://flask.pocoo.org/docs/0.12/quickstart/) 28 | 29 | ### What is not supported 30 | This project is not tested using Jupyter Notebook, PyCharm, 31 | Spider, or any other ide/text editor/programming environment for that matter. 32 | Atom or Sublime Text and the command line are the only supported development 33 | environment for this project. 34 | 35 | Sounds good? Then let's dive into building a fully functional web app using flask. 36 | 37 | ### Minimum Viable Product 38 | Our objective is to build an web based interface using Flask that 39 | - Shows a list of people who have RSVP-ed for the project Night 40 | - Each entry in the list should have 41 | - The name of the person 42 | - The meetup.com profile image of the person 43 | - An input text box that allows entering lines of code 44 | - On hitting the submit button we should get teams of four 45 | 46 | 47 | ### Flask 48 | For building the web interface, we will be using Flask. 49 | Flask is a micro web framework - it takes care of handling of the HTTP 50 | protocol for you and allows you focus on your application. It is flexible, 51 | lightweight yet powerful. 52 | 53 | ### Setup your environment 54 | #### Get the source code 55 | - If you are familiar with `git`, run 56 | 57 | git clone https://github.com/chicagopython/CodingWorkshops.git 58 | 59 | - If not, go to https://github.com/chicagopython/CodingWorkshops 60 | - Click on the Download Zip and unzip the file that gets downloaded 61 | - From your command line, change directory to the path where you have downloaded it. 62 | - On linux or OS X 63 | 64 | > cd path/to/CodingWorkshops/problems/webdev/flask_team_project/ 65 | 66 | - On Windows 67 | 68 | > cd path\to\CodingWorkshops\problems\webdev\flask_team_project 69 | 70 | 71 | Here you will find the basic skeleton of the app under `app.py`. 72 | 73 | ### Set up virtualenv 74 | If you are using Linux or OS X, run the following to create a new virtualenv 75 | 76 | python3 -m venv venv 77 | source venv/bin/activate 78 | pip install -r requirements.txt 79 | export FLASK_APP=app.py 80 | 81 | On Windows, run the following 82 | 83 | python3 -m venv venv 84 | venv\Scripts\activate 85 | pip install -r requirements.txt 86 | set %FLASK_APP%=app.py 87 | 88 | [](https://asciinema.org/a/M1hP91h153PuOPEjVYbot6jPj) 89 | 90 | ### Feature 0: run app.py 91 | With your environment now set up run 92 | 93 | flask run 94 | 95 | And you'll see 🔥. 96 | 97 | The reason is there is a string in the `app.py` file that allows meetup.com to identify who is trying to get data from them. It is called the API key. The one currently in the code is one of my old ones. You need to get one for your team from [here](https://secure.meetup.com/meetup_api/key/) - obviously, you'll have to be logged into meetup.com to get the key. 98 | Plug in your key whereever most relevant in `app.py` and run the above command again. 99 | 100 | This will start a [web server](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_is_a_web_server) on port 5000. 101 | Next load up http://locahost:5000/rsvps in your web browser. 102 | 103 | This will show you the list of people who RSVPed for a previous meetup. 104 | Goto tonight's meetup page and get the meetup id from the url. 105 | 106 | https://www.meetup.com/_ChiPy_/events/244121900/ 107 | 108 | The last section of the url is the `event_id`. 109 | 110 | ### Feature 1: Read app.py 111 | `app.py` is the script is where the magic happens. 112 | 113 | Lets start at the routes: 114 | 115 | @app.route('/rsvps') 116 | def rsvps(): 117 | 118 | 119 | @app.route('/teams', methods=['GET', 'POST']) 120 | def teams(): 121 | 122 | Discuss among the team how render_template function is used in rsvps and teams 123 | function. 124 | 125 | Two useful tools are pretty print and `pdb` 126 | 127 | #### Pretty print 128 | 129 | >> from pprint import pprint as pp 130 | >> pp(member_rsvps) 131 | 132 | This will give you a better view of what the function `get_names()` returns. 133 | 134 | #### pdb 135 | Python comes with a debugger `pdb`. Here's a [cheat sheet](https://appletree.or.kr/quick_reference_cards/Python/Python%20Debugger%20Cheatsheet.pdf) 136 | 137 | You can stick the following line anywhere in the code and make it halt so that you can better inspect the data and flow. 138 | 139 | import pdb; pdb.set_trace() 140 | 141 | ### Feature 2: Show profile images in rsvps 142 | Make changes to rsvps.html (inside templates) to show images of next to the 143 | names of the people. 144 | 145 | ### Feature 3: Add a text box next for lines of code 146 | Add an input type textbox that will take a number as input 147 | 148 | ### Feature 4: Display the lines of code 149 | On hitting submit, the numbers you entered against each person should show up 150 | on the `/teams` page. 151 | 152 | ### Feature 5: Display teams 153 | As of now, everybody is listed under one team: Team 1. 154 | Split the list of people selected into teams of 4 155 | 156 | Your display of each team should include 157 | 158 | Team Number: XYZ 159 | Name of team member1, Lines of code, (pic) 160 | Name of team member2, Lines of code, (pic) 161 | Name of team member3, Lines of code, (pic) 162 | Name of team member4, Lines of code, (pic) 163 | (Total lines of code:) 164 | 165 | where things in () are optional. 166 | There is no specific criteria for creating the teams as of now. We handle that 167 | next. 168 | 169 | ### Feature 6: Tell the world 170 | Record a gif of your app in motion and tweet tweet the link to @chicagopython with "Python Project Night Mentorship". Include the twitter handles of your team members. 171 | 172 | ### Feature 7: Integrate team creating logic (optional) 173 | Code reuse is a hallmark well written code base. Of course, we are 174 | not talking about copy pasting the code, but using the abstractions that a 175 | programming language provides so that there is minimum duplication of code. 176 | 177 | Use the code that you wrote in the team project command line application. The logic 178 | that you have implemented earlier for grouping your list of people into teams 179 | should now be used for creating your teams. 180 | 181 | Thanks! Thats all folks! 182 | If you found a bug or think you some instructions are missing - just open a issue in this repository. 183 | -------------------------------------------------------------------------------- /problems/webdev/flask_team_project/app.py: -------------------------------------------------------------------------------- 1 | from flask import Flask, render_template, request 2 | from flask_debugtoolbar import DebugToolbarExtension 3 | 4 | app = Flask(__name__) 5 | app.debug = True 6 | import meetup.api 7 | app.config['SECRET_KEY'] = 'foobar' 8 | 9 | toolbar = DebugToolbarExtension(app) 10 | 11 | def get_names(): 12 | client = meetup.api.Client("3f6d3275d3b6314e73453c4aa27") 13 | 14 | rsvps=client.GetRsvps(event_id='235484841', urlname='_ChiPy_') 15 | member_id = ','.join([str(i['member']['member_id']) for i in rsvps.results]) 16 | members = client.GetMembers(member_id=member_id) 17 | 18 | foo={} 19 | for member in members.results: 20 | try: 21 | foo[member['name']] = member['photo']['thumb_link'] 22 | except: 23 | pass # ignore those who do not have a complete profile 24 | return foo 25 | 26 | member_rsvps=get_names() 27 | 28 | @app.route('/rsvps') 29 | def rsvps(): 30 | return render_template('rsvps.html', rsvps=member_rsvps) 31 | 32 | 33 | @app.route('/teams', methods=['GET', 'POST']) 34 | def teams(): 35 | results = request.form.to_dict() 36 | return render_template('teams.html', teams=[results]) 37 | 38 | if __name__ == '__main__': 39 | app.run(debug=True) 40 | -------------------------------------------------------------------------------- /problems/webdev/flask_team_project/requirements.txt: -------------------------------------------------------------------------------- 1 | Flask==0.12.2 2 | meetup-api==0.1.1 3 | Flask-WTF==0.14.2 4 | flask-debugtoolbar==0.10.1 5 | -------------------------------------------------------------------------------- /problems/webdev/flask_team_project/templates/rsvps.html: -------------------------------------------------------------------------------- 1 | 2 | 3 |
| {{name}} |
24 |
50 |
51 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
64 |
65 |
66 |
67 |
96 |
97 |
98 |
--------------------------------------------------------------------------------
Tasks
25 |
26 |
27 |
28 |
48 |
49 | | # | 30 |task | 31 |description | 32 |mins | 33 |timestamp | 34 |done | 35 |
|---|---|---|---|---|---|
| {{loop.index}} | 40 |{{t.task}} 41 | | {{t.description}} | 42 |{{t.mins}} | 43 |{{t.timestamp}} | 44 |{{t.done}} | 45 |