The Pylons Project Documentation
The Pylons Project maintains the Pyramid web framework as well as additional packages intended for use with Pyramid. This is the home for the documentation for all of these projects.
Pyramid supports extensibility through add-ons. The following lists of add-ons are officially endorsed by the Pylons Project.
Pyramid Add-Ons Hosted Within Pylons Github Organization
The following add-ons have source code hosted within the collection of repositories related to the Pylons Project Github organization.
- pyramid_beaker, beaker session backend plug-in.
- pyramid_jinja2, Jinja2 template renderer for Pyramid
- pyramid_chameleon_genshi, template renderer for Chameleon's Genshi implementation.
- pyramid_rpc, RPC service add-on for Pyramid, supports XML-RPC in a more extensible manner than pyramid_xmlrpc with planned support for JSON-RPC and AMF.
- pyramid_xmlrpc, XML-RPC add-on for Pyramid
- pyramid_handlers, analogue of Pylons-style "controllers" for Pyramid.
- pyramid_zcml, Zope Configuration Markup Language configuration support for Pyramid.
Pyramid Add-Ons Hosted Outside Pylons Github Organization
The following packages are hosted in locations outside of the Pylons Project Github organization.
- pyramid_mailer, a package for the Pyramid framework to take the pain out of sending emails. Source: https://bitbucket.org/danjac/pyramid_mailer
Pyramid Resources (In-Progress)
The Pyramid Cookbook presents topical, practical usages of Pyramid. Unfinished.
Pyramid Tutorials presents tutorials dealing with Pyramid integrations with other technologies. Very unfinished.
Development questions related to Pylons projects can be discussed on the pylons-devel mail list.
On IRC, Pylons developers are generally available on the
on the Freenode IRC Network.
Using Support Wisely
Before asking a technical question on the maillist(s) or in IRC, please make sure to try the following things (paraphrased from Before You Ask):
- Try to find an answer by reading the manual.
- Try to find an answer by searching the maillist archives.
- Try to find an answer by searching the Web.
- Try to find an answer by inspection or experimentation.
- If you're a programmer, try to find an answer by reading the source code.
After exhausing these avenues, it's completely appropriate to ask a question on the Pylons-devel maillist or #pylons IRC channel. When you ask your question, please describe what you've learned from the efforts above, as it will help the developers focus on answering your question quickly. It also helps tremendously if you are able to provide a code or configuration snippet that makes the problem easily repeatable.
For Pylons users coming from Pylons 1 or repoze.bfg the change to a new core package might raise some questions regarding how to proceed, what it means for existing applications.
The Pylons Project welcomes contributors. Please read the following documentation about how the Pylons Project functions, coding styles expected for contributions, and the community standards we expect everyone to abide by.
Subscribe to the Pylons Podcasts. Pylons Podcasts are a series of audio podcasts from developers of the Pylons Project. You can either subscribe in iTunes or Rhythmbox (or your favorite audio client) using the Feed URL below, or listen to individual podcasts.
Episode 1: Q&A with Ben and Chris
In our inaugural episode, Chris McDonough and Ben Bangert talk about Pyramid, pyramid_deform, zc.buildout (aka "buildout"), Fabric, WebError, repoze.profile, Paste's errorcatcher, Arecibo, repoze.debug, Chris Davies' Pylons-to-Pyramid porting guide, Cucumber, Freshen, FormEncode, Formish, Deform, ZODB, repoze.folder, repoze.catalog, #pylons IRC channel, Paste, mod_wsgi, uwsgi, repoze.workflow, Colander, repoze.tm2, pyramid_routehelper, pyramid_beaker, the Pyramid todo list, zope.sqlalchemy, and the zope transaction module.
If you want to promote The Pylons Project and it's related technologies or your own work made with our tools.
Don't worry, none of these are actually true. We swear!