<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Django on Graeme&#39;s</title>
		<link>https://pietersz.co.uk/categories/django/</link>
		<description>Recent content in Django on Graeme&#39;s</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
		
		
		
			<lastBuildDate>Thu, 12 Oct 2017 14:20:52 +0000</lastBuildDate>
		
			<atom:link href="https://pietersz.co.uk/categories/django/rss.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Django signals are evil</title>
				<link>https://pietersz.co.uk/2017/10/django-signals/</link>
				<pubDate>Thu, 12 Oct 2017 14:20:52 +0000</pubDate>
				<guid>https://pietersz.co.uk/2017/10/django-signals/</guid>
				<description>I was trying to figure out what a Django app was doing today. It turned out that the original developer had decided to monkey patch a third party app. I hardly need say that monkey patching is evil (i.e. a last resort), but one of the things I needed to check along the way was that there was no code being triggered by a (Django) signal, and the problems it causes are very similar to monkey patching.</description>
			</item>
	</channel>
</rss>
