Personal tools
Skip to content. | Skip to navigation
Python bindings for the iwlib kernel interface, that provides functions to examine the wireless network devices installed on the system.
Jinja is a sandboxed template engine written in pure Python. It provides a Django-like non-XML syntax and compiles templates into executable python code. It's basically a combination of Django templates and python code.
Jinja2 is a template engine written in pure Python. It provides a Django inspired non-XML syntax but supports inline expressions and an optional sandboxed environment. If you have any exposure to other text-based template languages, such as Smarty or Django, you should feel right at home with Jinja2. It's both designer and developer friendly by sticking to Python's principles and adding functionality useful for templating environments.
Kegbot is a hardware and software system to record and monitor access to a beer kegerator. For more information and documentation, see http://kegbot.org/ Keg and Tap Management: Add and configure taps, assign kegs to taps, track remaining volume on active kegs, and mark empty kegs as finished. Kegbot has been designed with multi-tap systems in mind; a single install can support as many taps as you have. Account System: Full username/password account system, supporting registration, login, and password recovery. Drinker Authentication: Drinkers can be given physical tokens, such as RFIDs, to authenticate to the server during a pour. Pour Authorization and Shutoff: Optionally, your system can require that the server authorize each pour, only allowing access (by opening a valve) after the drinker is approved. Stats and Charts: Comprehensive statistics are calculated and recorded at each pour, and the web interface draws colorful charts. Drinking Sessions: As each drink is recorded, Kegbot assigns it to a discrete “drinking session” along with nearby drinks, and the server displays these sessions at a stable URL. Did you throw a party? Share a single URL that shows all the people and activity from that session. Database Backend: All Kegbot data, from basic drink information to derived statistics and user accounts, gets stored in a database (MySQL, or any other database supported by Django). JSON API: You can build your own frontend or other client interface using the Kegbot API. Drinks, tap status, user information, and almost every other interesting object in Kegbot is exposed this way. The same API is used for recording drinks. Web Hooks: The server can notify an arbitrary URL whenever there is activity such as a pour or new keg. You can bridge Kegbot to external services this way. Image Support: Users can upload profile pictures, and photos can be attached to drinks (something the Kegtab Android App does automatically). Sound Support: Assign short mp3s to play during certain events, such as when a user taps his RFID or pours more than 16oz. It’s fun! Twitter, Facebook, Foursquare, and more: Kegbot has hooks for a growing number of external/social sites. Users can link their Twitter, Facebook, Foursquare, or Untappd accounts, and configure automatic posting for each drink poured (or just at the start of a new session). Beer Database: A built-in database lets tag kegs by brewer and beer type. You can add entries for commercial or homebrew beers.
Kegbot API client library.
Library of miscellaneous utilities used within Kegbot.
This Python package is a high-level wrapper for Kerberos (GSSAPI) operations. The goal is to avoid having to build a module that wraps the entire Kerberos.framework, and instead offer a limited set of functions that do what is needed for client/serverKerberos authentication based on <http://www.ietf.org/rfc/rfc4559.txt>. Much of the C-code here is adapted from Apache's mod_auth_kerb-5.0rc7.