Django community: RSS
This page, updated regularly, aggregates Community blog posts from the Django community.
-
Using Sentry to log exceptions and logging messages from Django projects
sentry is something like an logs aggregation application. It can be used to log exceptions and other log messages from Django or other framework/programming languages (including JavaScript). Instead of sending a lot of emails to a project admin Django will send them to Sentry which will aggregate them and present in a readable form. Sentry is actually a Django application that can be launched setup on your local computer - perfect for testing. In this article I'll show you how to run Sentry on your local computer (basic setup) and how to configure Django and other parts of the Python code for optimal Sentry logging results. -
Making your Django app more pluggable
This blog post is about ways of doing things in your Django app, and pitfalls to avoid, so your app is easier to plug in to other sites. Introduction One of the most enticing promises of Django is that you’ll be able to add features to your site by just downloading apps and plugging them in. That’s one of the many reasons we use Django here at Caktus: we can build useful web sites for our clients more quickly by not having to re-invent the same building blocks all the time, and focusing on the unique value-add for each client. This is also one of the attractions of building and releasing open-source Django apps: they’re easy for other people to use, and having other people use your code is very satisfying. But Django apps don’t become easily pluggable automatically, and it’s easy to do things in a way that make it much harder for other sites to use an app. A book could be written about this topic. This post just gives examples of some areas that can cause problems, and might stimulate some thought when designing your app. Not everything needs to be an app Does your package have … -
Making your Django app more pluggable
This blog post is about ways of doing things in your Django app, and pitfalls to avoid, so your app is easier to plug in to other sites. -
Using mysql load data infile with django
Using mysql load data infile with django -
Using Fabric to update a remote svn checkout with ssh public key authentication
Using Fabric to update a remote svn checkout with ssh public key authentication -
Allow squid/mod_wsgi to pass the HTTP_AUTHORIZATION header to Apache
Allow squid/mod_wsgi to pass the HTTP_AUTHORIZATION header to Apache -
Django "view-permissions" for related objects
Django "view-permissions" for related objects -
Nested resources in Tastypie
Nested resources in Tastypie -
Custom choices in Django admin
Custom choices in Django admin -
RestORM - The client side of REST
RestORM - The client side of REST -
Customizing Django startproject with templates
Customizing Django startproject with templates -
Django cookie consent application
django-cookie-consent is a reusable application for managing various cookies and visitors consent for their use in Django project. Features: cookies and cookie groups are stored in models for easy management through Django admin interface support for both opt-in and opt-out cookie consent schemes removing declined cookies (or non accepted when opt-in scheme is used) logging user actions when they accept and decline various cookies easy adding new cookies and seamlessly re-asking for consent for new cookies Source code and example app are available on GitHub: https://github.com/bmihelac/django-cookie-consent Documentation: https://django-cookie-consent.readthedocs.org/en/latest/ -
Using Templates for Sending Emails
Sending nice pretty emails en-mass, or at regular intervals requires work so they look good. Fortunately Django's templates offers a great way to email uniform looking emails to your users. This video shows you how to do it, and keep it simple.Watch Now... -
MVC is not a helpful analogy for Django
Sometimes Django is described as MVC — Model-View-Controller. The problem with that is that people will either: come with baggage from existing MVC frameworks, which might be nothing like Django, or end up at something like the wikipedia page on MVC, which describes an architecture which is very unlike Django’s. The classic MVC architecture is about managing state. Suppose you have a GUI that allows you to, say, view and edit a drawing: You’ve got to store the drawing in memory somewhere. You’ve got to display the drawing on the screen. You have controls that allow you modify the drawing e.g. change the colour of a shape. And you’ve got to display the changes when that happens. The controller tells the model to change, and the model notifies the view in some way (preferably by some kind of pub/sub mechanism that allows the view to be fairly decoupled from the model). MVC is primarily about managing the changes in state so that everything is kept in sync. Model, View and Controller are all things that exist at the same time in memory (possibly running in different threads or processes), for extended periods, with their own state, and have to interact … -
(Don't) Do The Right Thing
In other fields they call it "analysis paralysis" but I'm not sure if it has a name in the world of software development. What I do know is that I tend to spend way too much time trying to do the "right" thing and I don't get down to just coding! The symptoms are easy enough to recognize when I'm starting a new project: Spending far too long just thinking about the project layout before I even create a single file. Doing "documentation driven development" to a fault (which means when combined with problem #1, I've just spent an hour fiddling with the layout of my documentation files) [1]. Worrying about what CSS framework to use. I really admire developers who can simply dive in and start writing code (test first of course!) without worrying about this stuff, whether because they have a workflow that they're comfortable with and can use consistently or simply because they don't worry about it. I think that when I was a younger coder I was one of those who could just sit down and mindlessly bang out PHP code just as fast as anybody else -- and I think the change has two main … -
A rich python console and more in Kate editor
I have done some improvements in the plugins: python_console_ipython, python_autocomplete, python_utils, js_utils, xml_pretty and django_utils. These plugins I added a month and a half ago (except python_console_ipython) to the kate repository. I have done two improvements and a new feature: Now they work with Python2 and Python3 (except python_autocomplete, this only works with Python2, due pysmell dependence) Now they have a configuration page (except python_autocomplete, this should not have configuration parameters) Page Config Plugins The new feature is the integration of the python_autocomplete and python_console_ipython plugins with the project plugin. The behaviour of these plugins depends of the loaded project. That is to say, the python_autocomplete plugin autocompletes with our project modules. Currently the kate community is working to add a new python autocomplete using jedi (this will work with Python2 and Python3). Python Autocomplete (with our modules) And the python_console_ipython plugin has something that we can name the project console. A ipython shell with the python path of our project and with the environments variables that the project plugin needs. IPython Console (converted in a django shell) To use this we need to add in the project file (.kateproject) a new attribute named “python”, with this structure: { "name": … -
What an Operation
This week sees django.db.migrations gain Operations, an Executor, and new command plans. Much of the work on migrations so far has been laying a good bit of groundwork, but now everything is starting to come together into a working whole. The most important thing to land this week is Operations - the things which migrations will be structured around. Here's an example of what a migration would look like: from django.db import migrations, models class Migration(migrations.Migration): dependencies = [("myapp", "0001_initial")] operations = [ migrations.AddField("Author", "rating", models.IntegerField(default=0)), migrations.CreateModel( "Book", [ ("id", models.AutoField(primary_key=True)), ("author", models.ForeignKey("migrations.Author", null=True)), ], ) ] As you can see, the Operations define what the migration does, and serve as the top-level element that allows more declarative migrations - as opposed to those in South, which were an opaque block of procedural code. What's in a name? But what exactly do Operations do? That's a relatively easy question to answer - they have an interface of exactly three methods. The first, state_forwards, takes a project state (that's an in-memory representation of all of your models and fields at a point in time) and modifies it to reflect the type of change it makes - AddField, for example, would add … -
Basic Ajax
Ajax is essential these days, and fortunately Django provides some good mechanism for doing AJAX well. This video goes over some of the basics you need to do and know when doing AJAX in Django.Watch Now... -
Basic Ajax
Ajax is essential these days, and fortunately Django provides some good mechanism for doing AJAX well. This video goes over some of the basics you need to do and know when doing AJAX in Django.Watch Now... -
Mysql too slow in tests ? ramdisk it !
Suppose you're doing it wrong: you're using MySQL and your test suite is slow very slow. MySQL is very slow at DDL statements so creating/clearing/loading that test database all the time is going to be very slow. People have worked out some solutions like: Using TRUNCATE instead of DROP/CREATE and/or other tricks [1]. Fine tunning mysql ... just for development ?!? [2], [3]. Use TransactionTestCase Use sqlite in :memory: - very bad idea, lots of subtle bugs won't be catched in the test suite. And finally there's one solution that doesn't have the code trade-offs but it's a pain to get it set up: MySQL running on ramdisk (known as tmpfs). I've seen some solutions [4], [5], [6], none worked on Ubuntu (12.04) very well for me thus I've cooked up my own version. It's largely based on [6] but with cleanup code in case you already ran it and added the missing database setup part (you might want to edit the passwords and database names). #!/bin/bash -xEe i=$1 if [ -z "$i" ]; then echo "Missing argument: instance number." exit 1 fi port=$[3306+$i] pid=`cat "/var/run/mysqld/mysqld$i.pid" || true` if [ -n "$pid" ]; then kill -9 $pid while kill -0 … -
Mysql too slow in tests ? ramdisk it !
Suppose you're doing it wrong: you're using MySQL and your test suite is slow very slow. MySQL is very slow at DDL statements so creating/clearing/loading that test database all the time is going to be very slow. People have worked out some solutions like: Using TRUNCATE instead of DROP/CREATE and/or other tricks [1]. Fine tunning mysql ... just for development ?!? [2], [3]. Use TransactionTestCase Use sqlite in :memory: - very bad idea, lots of subtle bugs won't be catched in the test suite. And finally there's one solution that doesn't have the code trade-offs but it's a pain to get it set up: MySQL running on ramdisk (known as tmpfs). I've seen some solutions [4], [5], [6], none worked on Ubuntu (12.04) very well for me thus I've cooked up my own version. It's largely based on [6] but with cleanup code in case you already ran it and added the missing database setup part (you might want to edit the passwords and database names). #!/bin/bash -xEe i=$1 if [ -z "$i" ]; then echo "Missing argument: instance number." exit 1 fi port=$[3306+$i] pid=`cat "/var/run/mysqld/mysqld$i.pid" || true` if [ -n "$pid" ]; then kill -9 $pid while kill -0 … -
A Short Summary on Sybase SQL Anywhere and Python
As some of my older rage-filled articles indicated, we’re still running some services on Sybase’s SQL Anywhere. Since it cost me many hours and sanity wrangling, I think it may be helpful to others to summarize the current situation for Python developers. Abstract It hurts a little bit less now. We’re using the official sqlanydb driver in production. Options There are four ways known to me to access a SQL Anywhere database in Python: Their official sqlanydb driver that requires their client libraries. Used by sqlany-django which gives you Django’s ORM with SQL Anywhere. Their official ODBC drivers via pyodbc. The python-sybase module which also needs a pretty complete SQL Anywhere installation to build. Supported by SQLAlchemy. FreeTDS via pyodbc. Problems Historically, there have been problems with all of them: sqlanydb crashed. Their ODBC drivers leaked semaphores which led to a denial of service eventually. sqlanydb seems to leak prepared statements on exceptions which leads to Resource Governor errors. I never got python-sybase working and it seems abandonware. FreeTDS randomly hangs in queries, doesn’t get a lot of attention either. In our experience so far, it seems like the first two problems have been remedied as of sqlanydb 1.0.5 (which … -
Non-trusted mercurial .hgrc on a Vagrant virtualbox
I use Vagrant and virtualbox for developing inside ubuntu on OSX. I have a couple of mercurial (hg) checkouts and they were giving me grief: $ hg up Not trusting file /some-repo/.hg/hgrc from untrusted user 501, group dialout The .hg/hgrc file contains the remote repo URL, so pulling even won't work. The problem is apparently the interaction between virtualbox and OSX if you use NFS to mount part of your OSX's harddisk. The solution/workaround is quite simple. Tell mercurial to trust that 501 user in your ~/.hgrc: .... [trusted] users = 501 Now it works! -
Continuous integration of webapps with Buildbot
Buildbot, the Continuous Integration Framework Buildbot is an excellent tool used by many well known products like Firefox and Google Chrome. Although it is used to build complex projects from code compilation to packaging it can also be used to do continuous integration of smaller projects and apps. Buildbot can get notifications from services like GitHub and BitBucket, and from in-house hosted repositories. It can be set up to trigger builds on results of other builds and allows full service control through IRC among many other features. In this story I show how to set up Buildbot to do continuous integration of a sample web app and a sample dependent web project. I focus on using Git repositories, hosted in both Github and your own location. -
Continuous integration of webapps with Buildbot
Buildbot is a powerful and flexible tool used by many sophisticated products like Python, Firefox, Webkit, Google Chrome, Twisted, Node.js and [many more](http://trac.buildbot.net/wiki/SuccessStories). Buildbot, the Continuous Integration Framework Buildbot is primarily used to build software for different architectures covering the process from code compilation to packaging, but it can also be used to do continuous integration of less sophisticated projects where tools and services like [Jenkins](http://jenkins-ci.org/) and [Travis-CI](https://travis-ci.org/) are more popular but less flexible. In this story I introduce Buildbot to run test suites for two products, a sample web application and a sample dependent web project. The web app is a fully functional open source example of a Django pluggable application. While the project is an implementation of the Django [tutorial](https://docs.djangoproject.com/en/1.5/intro/tutorial01/) plus a few simple test cases. Source code for the [app](https://github.com/danirus/django-sample-app) and the [project](https://github.com/danirus/django-sample-project) as long as the configuration files for Buildbot are available in GitHub. #### 1. The scenario The configuration will face the following final scenario: 1. Test suites for both the app and the project will run under several versions of Django and Python in order to be sure that the app is usable for every supported Django release and that the project might be …
