3. Briefly introduce the tutorial.

4. Learn about Pyramid.

5. Write a simple application.

6. Improve our application in stages.

7. Get answers to some Pyramid questions.

8. Hopefully, have some fun.

10. If not, grab a CD, install and pass it on.

11. Anyway, all the code is at: https://github.com/cguardia/Pyramid-Tutorial

12. Tutorial survey.

13. Pyramid book winners.

14. Tutorial structure.

16. We'll have four stages, where we'll first learn a few Pyramid concepts, then start looking at the code for that stage.

17. Throughout the tutorial, I will answer any questions that may come up.

19. I live in Mexico, but work for Boston based web development consulting firm Jazkarta.

20. I've been doing web stuff since 1994.

21. I'm a Pyramid contributor since the days of repoze.bfg (that means 2008 or so).

22. I love Pyramid so much that I was willing to leave the side of my lovely three children and beautiful wife for a couple of days just to teach you about it.

24. At least some familiarity with Python. We'll not do anything complex here, but you should be able to look at some code and have some idea what's going on.

25. Real interest in writing a real web application sometime.

27. It's an umbrella name, similar to how the Apache name is used today

28. Pylons 1 is a stable and maintained web framework, but no further enhancements to it will be done.

29. Pyramid is the current and future embodiment of Pylons-Style web development

30. There will be other projects under this umbrella, like TurboGears.

32. Minimalism

33. Documentation

34. Openness

35. Speed

36. Reliability Pyramid is primarily inspired by Django, Zope and Pylons.

38. New features include better support for scripting, caching and testing tools.

39. Supports Python versions 2.5 to 2.7.

40. Python 3 support is being worked on.

41. We keep adding new documentation in the form of how-to's and tutorials.

42. Many people have begun contributing Pyramid add-ons and applications.

44. If you like to have control of all the parts of your application.

45. If you need a truly pluggable framework.

46. if you enjoy 'doing it yourself' when you need something special.

47. Certainly it's a great option if you want to use Python.

49. The installation procedure is very similar in the three major OS versions.

50. Pyramid best practice suggests the use of virtualenv for development.

51. A “real” development environment is required, which in linux meand C compiler and in Mac OSX means Xcode. On Windows you will require the Python for Windows Extensions

53. pyramid_zodb

54. pyramid_routesalchemy

55. pyramid_alchemy In addition there are some third party scaffolds available. In particular Akhet might be useful for Pylons legacy users.

57. It's a good idea to try to keep that structure when developing using a scaffold.

58. They include development and production configurations.

59. They all use paster as a WSGI server.

61. Most new users will not start there.

62. A typical project might use routes and a relational database. We recommend but do not enforce using SQLAlchemy.

63. There are two templating languages. Most documentation uses ZPT, but you can use Make out of the box as well. There are also third paty bindings.

65. Uses a transaction manager

66. Uses routes (URL dispatch)

67. Uses ZPT

68. Let's take a look at the code.

70. This method creates a configuration object to hold Pyramid's routing and view configuration.

71. Then a WSGI application is created, which is a router that uses the configuration to decide how to handle request.

72. Pyramid also offers sessions, authorization, authentication and templating.

74. When the user visits our application in a browser, the PATH_INFO part of the URL is used to decide which of the application's routes apply.

75. The pattern syntax allows URL parameters, which are passed on a matchdict variable when a route matches.

76. Order is important when declaring routes.

78. Views are registered at application start up.

79. A particular view can be associated with a route and is called when the route matches and passed any parameters that it has.

80. Views can be registered also for exceptions, allowing us to customize responses.

82. Context

83. route_name

84. Request type

85. Request method

87. Xhr

88. Accept

89. Header

90. Path info

91. custom

94. Json

95. Jsonp

97. It's easy to create custom renderers if needed.

98. You can still alter the response by using request.response to set headers.

100. A static resource is any file that's not Python code.

101. The name of the static view represents a URL path to get the resources.

102. Static resources can be overridden from other packages.

104. At this point it has a single route.

105. It has two views which use the same route.

106. The view predicates are the difference.

107. Note the use of renderers.

108. We also have a static view.

110. It also provides a simple authentication policy to handle custom logins.

111. The next stage of our sample application adds such a system to our Birdie app.

113. Pyramid also offers another configuration mode which allows us to have the view defined right beside the code it uses.

114. For larger systems, this might be a better strategy.

116. Get a list of probable views for a given URL: bin/paster pviews development.ini /join

117. Get a shell with the Pyramid configuration: bin/paster pshell development.ini

119. All the views defined one after the other is known as imperative configuration.

120. The other system is known as declarative configuration.

121. Note that the decorators that Pyramid uses for views do not have side effects at import time, so it's necessary to use the scan function.

124. Events

125. Sessions

126. Scripting

127. Hooks

128. Deployment

130. It's conceptually similar to navigating a filesystem tree.

131. It's also very useful when you need row level security (different permissions per content object).

132. Instead of looking views using routes, we traverse to a content object and then pick one of its views.

134. Most importantly, we can be notified when the request is created and when the response is prepared.

135. We can have our callbacks execute before these events.

137. We also have one of the most friendly live support channels on IRC. Please visit.

138. More information at: http://www.pylonsproject.org

140. Find us in IRC, channel #pyramid