Slide 1
Slide 1 text
Responder:
A Familiar
HTTP Service
Framework
Kenneth Reitz
Slide 2
Slide 2 text
Hi.
Slide 3
Slide 3 text
@kennethreitz
Slide 4
Slide 4 text
No content
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
github.com/kennethreitz
• Requests
• Responder
• Maya
• Records
• Tablib
• httpbin.org
• Python-Guide.org
• SayThanks.io
• 'Import This' Podcast
• Em Keyboard
• Certifi
• Autoenv
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
Pipenv is the porcelain I always
wanted to build for pip. It fits my brain
and mostly replaces
virtualenvwrapper and manual pip
calls for me. Use it.
— Jannis Leidel
(former pip maintainer)
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
Requests:
HTTP for Humans
Slide 11
Slide 11 text
Requests is the perfect example how
beautiful an API can be with the right
level of abstraction.
— Armin Roncher (Flask, etc)
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
History Time!
Slide 14
Slide 14 text
1999: Zope + Plone.
- Established Python early-on as a serious
contender for web development, used
heavily in government.
- Python 1.5.2 was released in 1999.
- Other community tools, like buildout.
Slide 15
Slide 15 text
1999: Zope + Plone.
Slide 16
Slide 16 text
The Rest of the World:
Classic ASP, PHP, Perl, and
CGI Scripts.
Slide 17
Slide 17 text
WSGI
2003
Slide 18
Slide 18 text
2005: Django.
- Sort of a response to Ruby on Rails.
- A serious web development framework.
- Originally built for a small newspaper in Kansas, it
excels greatly at content-driven applications.
- Makes a lot of decisions for you (architecture, etc).
- Was the de-facto web framework for Python for a
long time.
Slide 19
Slide 19 text
2006: Pylons.
- Took the energy of Zope + Plone.
- A serious contender to Django.
- Allowed you to build things with a
more component-oriented
architecture than Django.
Slide 20
Slide 20 text
The Rest of the World:
The Classics + Ruby on Rails.
Slide 21
Slide 21 text
2007: Webob
Slide 22
Slide 22 text
Honorable Mention:
Pyramid.
The reasonable alternative to Django.
Slide 23
Slide 23 text
Flask.
- Everyone’s favorite framework.
- Started out as an April Fool’s joke (denied).
- “a single file”
- Directly inspired by Ruby’s Sinatra.
- Grew on popularity due to user-friendliness.
- Simple API presented; rarely need to
reference the documentation when using it.
Slide 24
Slide 24 text
The Future
2019+
Slide 25
Slide 25 text
vs.
Flask
Django
Choosing your next project’s web framework…
Slide 26
Slide 26 text
Less necessary than you think.
Webockets?
Sever-Sent Events (SSE).
Slide 27
Slide 27 text
Django Channels
Falcon
Hug
Slide 28
Slide 28 text
ASGI
Slide 29
Slide 29 text
No content
Slide 30
Slide 30 text
Responder Intentions…
- Include Requests as a standard HTTP client.
- Base the Request/Response objects very similar to
Requests’ own objects.
- See if anyone is interested (they seem to be).
- Take ourselves seriously.
- Make “the world’s best web framework”.
Slide 31
Slide 31 text
DEMO (Q&A)
Slide 32
Slide 32 text
Thank you!
Slide 33
Slide 33 text
No content