Python is a programming language that lets you work quickly and integrate systems more effectively, but creating a web-based application is not an easy task, as anyone who has written a web based application which make use of programmed CGIs in Perl or PHP can attest to that. So you’re here in search of a simpler approach, you’re here, in search of Pylon!
Pylons is a web framework coded in Python, which provides a strong foundation for your web applications. Any kind of information you need about the Pylons web framework can be found on Pylons HQ and you just need some basic knowledge of HTML and Python and a free-thinking mind to learn everything we have to offer.
When Pylons first started, it was referred to as, just Pylons framework and that was before the merger occurred that finally resulted in the Pylons Project. The course of events below begins with the Pylons framework, giving the foundation to how the pylons Project reached its final state and the events that led to the merger and the previous projects.
Pylons 0.8 (2005 – 2006)
Pylons was first introduced when more than 30 Python systems were competing for attention, and that was the point Ben Bangert had noticed another Python system, Bricks which had the same goals and decided to merge his work with James Gardner to develop on the web-based framework that eventually led to Pylons.
In September 2015, Pylons first appeared and was a customization of the Myghty Python Templating Framework, which gave an MVC situated web framework due to its page handler customization. As opposed to operating under mod-python as was normal for Myghty, but instead, Pylons operated using Myghty’s WSGI handler under Paste.
Pylons concentrated on using WSGI specification for an adaptable component based way to deal with web application stack, unlike a majority of the Python frameworks at that time. Myghty takes care of the caching, session handling, default templating language, and the request/response objects, while the application was operated and loaded using Paste and Routes, was made to deal with URL dispatching and generation. It was around this time that Phil Jenvey was introduced to the development team and started working effectively on Pylons.
Pylons 0.9 (2006 – 2009)
During the O’Reilly OSCON, a lot of key changes to the internal structure were made due to the release of Pylons 0.9, it was no longer a good option for Pylons to operate as a Myghty page handler customization, so Pylons made a reasonable distinction by operating as a WSGI application leaving Myghty to take care of only templates. A new third party, Beaker which was predicated on the caching/session handling subsystem used by Myghty, was now responsible for handling its own session handling and caching.
Pylons 1.0 (2010 – present)
Pylons 1.0 is an advanced version which serves as a lightweight web frame that specializes in adaptability and fast development above all, for now, the Pylons 1.0 is in maintenance mode only.
Pylons was heavily inspired by the likes of Ruby, Python, and Perl, as it gives an incredibly adaptable Python web framework which is also organized, and its likewise one of the first projects to use the developing WSGI standard, which permits broad adaptability and continued use, but only if it is required.
In Conclusion, Pylons is committed to making web development quick, adaptable and very simple.