The document discusses Pyramid, a Python web framework. It denies claims that Pyramid was built by aliens or that its code is thousands of years old. It then provides explanations and defenses for some of Pyramid's design decisions and recommendations for those considering using Pyramid for new projects.

2. Not built by aliens

3. It's not, really Pyramid is not built by aliens.

4. These aliens are not telepathic. They do not look like human babies.

5. The Pyramid developers do not worship an ancient crocodile god.

6. The source code for Pyramid is not over 5,000 years old.

7. For complete and emphatic denials see: http://docs.pylonsproject.org/denials/pyramid.html

8. Listening to your users IRC channels (#pyramid, #pylons).

9. Mailing lists (pylons-discuss, pylons-devel).

10. Twitter, Convore, etc.

11. Reddit, Ycombinator, etc.

12. Blogs.

13. Different kinds of FAQs What?

14. Where?

15. How?

16. Why?

17. Critiques

18. I hate...

19. Why I love Pyramid?

20. “ Pyramid is a "Pylons Project" term shall lead to confusion to many People.” “ Hello, I want to know exactly what is the relation b/w these web frameworks.” “ I've had some projects in mind for a while and I was just seeking some clarification regarding frameworks. Pylons, Pyramid, Turbogears and Web2Py in particular.”

21. The Pylons Project The aim of the project is to develop a related set of web technologies

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

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

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

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

26. “ Pyramid Provides More Than One Way to Do It” “ Pyramid Does Traversal, And I Don’t Like that” “ Pyramid Has Too Many Dependencies” “ Pyramid Uses A Zope Component Architecture (“ZCA”) Registry”

27. Design decisions Like all software, Pyramid's developers made design decisions that you may not like.

28. Still, there was some thinking behind them.

29. We know we can't convince you, but we can at least explain why those decisions were made.

30. Pyramid design defense: http://docs.pylonsproject.org/projects/pyramid/1.0/designdefense.html

32. “ Do you recommend Pyramid even to those without zope background ?” “ However I still believe the better solution would have been a complete rewrite than merging with repoze with all its Zope baggage .” “ seems to be some zope legacy , I puke every time i see the ZCML or the template language from plone or the zopedb and it's orm”

33. Pyramid's Zope “baggage”

34. Zope baggage Pyramid depends directly on zope.component.

35. There is an optional ZCML package.

36. Traversal and other Zope concepts can be used or not.

37. Pyramid doesn't hate Zope, but Pyramid is not Zope.

38. “ The first impression was, that the whole documentation is very complete, but quite abstract ” “ Pyramid is well documented...it has a lot of coverage, but the editing and organization is still quite lacking.” “ I think the problem currently is that people start by going into the main documentation, and then get overwhelmed .”

39. Pyramid Documentation We are proud of Pyramid's extensive documentation (around 700 printed pages and counting).

40. But we admit that docs need work.

41. We are sprinting on it, specially beginner documentation.

42. That said, do you know about: Pyramid cookbook: http://docs.pylonsproject.org/projects/pyramid_cookbook/dev/index.html

43. Pyramid tutorials: http://docs.pylonsproject.org/projects/pyramid/1.0/#tutorials

44. “ Why doesn't Pyramid give me more rails?”

46. Opinionated Pyramids Khufu, by Rocky Burt https://github.com/serverzen/khufu_opinion

47. Akhet, by Mike Orr https://bitbucket.org/sluggo/akhet

48. Stay tuned for contributions from TurboGears' team

49. Other opinionated packages will turn up in due time

50. “ Pyramid or Pylons” “ for someone unfamiliar with either of them, which one, Pyramid or Pylons, would be the best one to begin learning and creating projects with?” “ do you all suggest starting with Pyramids ? Or shall I wait for some more months ?”

51. New project: Pyramid or Pylons? Pyramid.

52. Although it's 1.0, remember it existed as repoze.bfg for some years.

53. If you need to migrate from a Pylons project, you can use both at the same time.

54. If you are very familiar with Pylons and are unsure how to use Pyramid, we are working on ways to help you

55. “ I would like to move from Pylons 1.0 to Pyramid, but I'm not going to be able manage a wholesale port any time soon. So, I'm wondering if it would be practical to start using some parts of Pyramid within an existing Pylons project.”

56. From webob.exc import NotFound class LegacyView(object): def __init__(self, app): self.app = app # app is the legacy Pylons app def __call__(self, request): return request.get_response(self.app) if __name__ == '__main__': pylonsapp = ... obtain pylons WSGI application object ... legacy_view = LegacyView(pylonsapp) config = Configurator() config.add_view(context=NotFound, view=legacy_view) Running a Pylons application “inside” a Pyramid application

57. "The Pyramid manual is overwhelming." "How to migrate from Pylons" "What's the equivalent of Pylons ``h``?" "How do I port my Pylons controllers to Pyramid?"

59. Akhet Pyramid application templates inspired by Pylons 1 style.

60. Makes the transition from Pylons easier.

61. Almost at beta 1.

62. Mike's working on it as we speak.

63. https://bitbucket.org/sluggo/akhet

64. Current features of Akhet application template: pyramid_sqla or akhet

65. complete documentation

66. SQLAlchemy model using pyamid_sqla or SQLAHelper, similar to Pylons

67. SQLAlchemy transaction management via repoze.tm2

68. Static files served under "/" overlayed with dynamic URLs, as in Pylons

69. A helpers.py module tied to an ``h`` variable in templates

70. URL dispatch and view handlers, similar to Pylons

71. Current features of Akhet (II) Templates ending in .html are passed to Mako (or to your desired template engine)

72. Listen on localhost:5000 by default, as in Pylons

73. A logger for the application package is configured .

74. A command-line script to create your database, replacing "paster setup-app" in Pylons

75. Pyramid Migration FAQ Overview of Pyramid from a Pylons perspective

76. Differences between the frameworks

77. (Mostly) finished

78. Will be part of the official documentation

79. http://www.google.com/url?sa=D&q=https://bytebucket.org/sluggo/pyramid-docs/wiki/html/migration.html

80. “ Traversal seems more powerful than URL dispatch even though I can't fully yet appreciate/comprehend using traversal” “ The traversal approach from the documentation sounded interesting...I took a look...and had no clue how the different pages were addressed” “ Why provide two ways of doing the same thing?”

81. What is traversal Think of it as serving an old (really old) style web application.

82. We serve files from a path, '/get/some/file.html'

83. Some actions may depend on extensions (.cgi, .php, etc.)

84. What is Traversal (II) But instead of serving files, we serve python objects (resources).

85. The object (resource) that traversal finds is called the context.

86. A resource can have several views which are looked up in a registry.

87. Rob Miller explained this so perfectly in a blog post that it was added to the docs: http://docs.pylonsproject.org/projects/pyramid/1.0/narr/muchadoabouttraversal.html

89. When to use traversal Your URL tree is deeply nested or can't be known in advance.

90. You want an easy way to set row level security.

91. When to not use traversal You are writing your first Pyramid app and you come from Pylons, Django, etc.

92. Your URL tree can be known in advance.

93. You have am “square” data set.

94. You don't need row level security.

95. Not built by aliens