<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: argparse</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/argparse.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2009-12-09T08:41:02+00:00</updated><author><name>Simon Willison</name></author><entry><title>Fixing Django Management Commands</title><link href="https://simonwillison.net/2009/Dec/9/zachary/#atom-tag" rel="alternate"/><published>2009-12-09T08:41:02+00:00</published><updated>2009-12-09T08:41:02+00:00</updated><id>https://simonwillison.net/2009/Dec/9/zachary/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://blog.zacharyvoase.com/post/275566873"&gt;Fixing Django Management Commands&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Zachary Voase proposes dramatically improving Django’s management command API for Django 1.3. I’m in favour—management commands are one of the only APIs in Django that I have to look up every single time I use. My optfunc library was written partially with management commands in mind—Zachary favours the argparse library.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/argparse"&gt;argparse&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/managementcommands"&gt;managementcommands&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/optfunc"&gt;optfunc&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/zachary-voase"&gt;zachary-voase&lt;/a&gt;&lt;/p&gt;



</summary><category term="argparse"/><category term="django"/><category term="managementcommands"/><category term="optfunc"/><category term="python"/><category term="zachary-voase"/></entry></feed>