I’ve recently started a new Python project called BiosBase. It’s intended to be something of a quickstart template for new Pylons web projects. This is a very broad overview however a working user auth system and general examples of best practices (Or at least the best I can figure out.) for handling users, forms and so forth will be included.
My reason for this project is that I currently have around 3 Pylons powered projects, all of which in various states of completion (or more accurately, lack thereof). This is in part because I finesse and finagle every tiny bit of the code to keep things as ‘perfect’ as humanly possible. The more major problems come when I start working on integrating repoze.what into things. repoze.what is basically a user auth system from the zope project. From what I understand, it’s generally considered a very solid library and the primary choice for Pylons projects. The only catch however is that there are only a few somewhat poor and outdated examples of using it with Pylons.
And from this problem comes BiosBase. Most of my work is reading through all the examples that are out there, reading the repoze.what docs and working in the best parts from everything I find. I’m working to keep the system as generic as possible and am trying to keep the controllers as self-explanatory as possible.
In summery, there is currently a prototype of BiosBase over at github.com/BiosElement/BiosBase. Currently you have to read the source to figure things out however user registration and login/logout is currently working (mostly) as intended. I’m very much intrested in community input as this is the first time I’ve worked somewhat in-depth with a user auth system and would like to continue this project as something of a “thank you” to the community.
