PageRenderTime 92ms CodeModel.GetById 40ms app.highlight 13ms RepoModel.GetById 37ms app.codeStats 0ms

/kai/templates/home/history.mako

https://bitbucket.org/bbangert/kai/
Mako | 43 lines | 41 code | 2 blank | 0 comment | 2 complexity | 452eb33728ca8f7fdbaf5ff57516ec7c MD5 | raw file
 1<div class="yui-b content">
 2    <h1>History of Pylons</h1>
 3    <h2>Pylons 0.8 (2005 - 2006)</h2>
 4    <p>Developed at a time when many Python frameworks (30+ of them) were vying for
 5        users, Ben Bangert, noticed that another Python
 6        framework, <a href="http://pythonweb.org/doc/bricks.doc.html">Bricks</a> had
 7        a similar goal and merged development efforts with James Gardner to work
 8        on the web development framework that became Pylons.</p>
 9    <p>Pylons first came into existence in September, 2005. Initially it was a
10        customization of the <a href="http://www.myghty.org/">Myghty</a> Python
11        Templating Framework, utilizing page handler customization to provide
12        a MVC oriented web framework. Rather than running under mod_python as
13        was common for Myghty, Pylons ran using Myghty's WSGI handler under
14        <a href="http://pythonpaste.org/">Paste</a>.</p>
15    <p>Unlike most other Python frameworks at the time, Pylons focused heavily
16        on utilizing the <a href="http://www.python.org/dev/peps/pep-0333/">WSGI specification</a>
17        for a flexible component based approach to a web application stack. Session handling, caching,
18        the default templating language, and the request/response objects were all handled by Myghty,
19        while Paste was used to load and run the application.</p>
20    
21    <h2>Pylons 0.9 - 0.9.7 (2006 - 2009)</h2>
22    <p>Pylons 0.9 was released during <a href="http://conferences.oreillynet.com/os2006/">O'Reilly's 2006 OSCON</a>
23        and brought some major changes to the internal architecture.</p>
24    <p>Running as a Myghty page handler customization became a less than optimal design
25        decision, and Pylons 0.9 made a clear break by running entirely as a WSGI application
26        that then used Myghty as needed for templates only. Session handling and caching were
27        handled by a new 3rd party package called Beaker that was based on the caching/session
28        handling subsystem used by Myghty. Request and response objects were provided by light-weight
29        WSGI wrappers in Paste, which was also still used to run and load the web application.</p>
30    <p>During the development of the 0.9 series, several features of Paste were extracted into smaller,
31        more focused packages. The testing suite became WebTest, the WSGI wrappers became WebOb, and
32        the interactive debugging environment became WebError. Pylons 0.9 follows these developments
33        by switching from using Paste to the new packages which provide more functionality with
34        little to no backwards incompatibility issues.</p>
35    
36    <h2>Pylons 1.0 and beyond (2010-)</h2>
37    <p>Pylons 1.0 aims to be a finished and polished web application framework utilizing the
38        newly extracted, and mature Python packages developed in the past few years symbiotically
39        with Pylons.</p>
40    <p>Current projections are for a Pylons 1.0 release in early 2010.</p>
41</div>
42<%def name="title()">${parent.title()} - History</%def>
43<%inherit file="../layout.mako" />