For testability reasons, we’ve begun using a lot of dependency injection in our Python projects. Imagine that I have a function that does some work and then ultimately calls an API over-the-wire: import simplejson from google.appengine.api import urlfetch # App Engine example def my_method(user_id):   url = ‘http://www.example.com/lookup-user/%d.json’ % user_id   result = urlfetch.fetch(url)   if result.status_code == [...]

One of the great things about templating systems is the ability to encapsulate repeatable chunks of code. One of the tough things about templating systems is management of a global “state” to ensure the the overall document that is emitted is as efficient as possible – especially in the HTML world were bandwidth is a [...]

Google App Engine doesn’t have a unique constraint in the classical sense of relational databases. This is a favourite construct of application developers and it’s unfortunate that it’s not present. At the same time, a basic understanding of the underlying datastore points to why it’s tough, or at least inefficient. There are places where you’re [...]

Recently, I discovered something surprising about Google App Engine’s datastore and ReferenceProperty. Imagine I have a class like the following:   from google.appengine.ext import db   class Home(db.Model):     address = db.StringProperty()     room = db.ReferenceProperty(Room) where Room is also a db.Model. Datastore uses a proxying technique such that db.Model objects are created lightly (i.e., with only their key) [...]

We have a templatetag, called scurl, that needs to look at the HttpRequest object. Django’s templating system provides a straight-forward, yet wordy, mechanism to pass the request object in to the template:   def my_view(request):     return render_to_response(“myview.html”, context_instance=RequestContext(request)) The render method of our scurl templatetag gets access to this context and thus access to the HttpRequest. [...]

So, here we sit, uncertain of our first steps…. Here at VendAsta, we’ve just kicked off our Friday afternoon jam sessions. Starting at noon, we bring in lunch and all get together in adhoc groups and work on projects of interest. Anything. Well, anything software. It’s an odd feeling though to have all constraints lifted [...]

Code review is a vital mechanism for ensuring conventions and patterns, as well as spreading knowledge of solutions and technologies throughout a team. We have been evaluating Crucible as a formal tool for tracking comments and laying the comments alongside the actual code. The cool thing is that it integrates (somewhat) with Fisheye, Jira, and [...]