Figuring out the necessary changes is actually a quite good exercise in getting to know Django, but if you get stuck or feel lazy feel free to consult below:

Chapter 2 p. 13:

The lines to uncomment are:

# from django.contrib import admin
# admin.autodiscover()

and

# (r'^admin/(.*)', admin.site.root),

You might want to uncomment the following line too, which will activate the documentation in the admin site:

# (r'^admin/doc/', include('django.contrib.admindocs.urls')),

Chapter 2 p. 15:

In addition to filling out the fields in the bulleted list you also need to select the “127.0.0.1:8000″ entry  in the “Sites” list at the bottom of the form as this field is required.

Chapter 3. p.23:

Make sure to add the (r’^… line before the (r”… line you added on p. 16. Otherwise the first “catch all” pattern will match your attempt to load the tiny_mce.js script and the script will fail to load.

Chapter 3. p34:

Leave out the following lines:

class Admin:
   pass

Instead do the following. In the search directory create a new fil admin.py with the followin contents:

from cms.search.models import SearchKeyword
from django.contrib.flatpages.models import FlatPage
from django.contrib import admin

class SearchKeywordInline(admin.StackedInline):
   model = SearchKeyword

class FlatPageAdmin(admin.ModelAdmin):
   inlines = [SearchKeywordInline,]

admin.site.register(SearchKeyword)
admin.site.unregister(FlatPage)
admin.site.register(FlatPage, FlatPageAdmin)

Chapter 3. p36:

Don’t add the core=True, edit_inline=models.STACKED, min_num_in_admin=3 and num_extra_on_change=1 options. The features added by these options are all handled by the admin.py file introduced above.

PJ = ESR ?

server’s current state: “My current state is fifty boxes of paper clips in inventory.”

client one: “Hi server. Last time I contacted you, you had seventy boxes of paper clips in inventory. I am placing an order for sixty. I will accept a smaller quantity if you have >= forty in inventory. Bye!”

client two: “Hi server. I need twenty boxes of paper clips. I have no clue how many you had in inventory last time I contacted you, and I don’t really care. Fulfill this exact order or cancel it, no exceptions. Smell ya later.”

server: “Received client two’s request. Hi client two, you are properly authenticated, so I’ll look at your state. You want exactly twenty boxes of paper clips. You will make no exceptions. I currently have fifty boxes. I don’t care how many you have, I only care about how many you need. Your order is fulfilled, and I have thirty left. Bye.”

server: “Received client one’s request. Hi client one, you are properly authenticated, so I’ll look at your state. You want sixty boxes of paper clips. You will settle for a minimum of forty. My current state is only thirty in inventory. Your order is not fulfilled, and I have thirty left. Bye.”

Compare this to non-RESTful chatter between client and server:
client two:”Hi server.”

server: “Hi client two. You are authenticated, so I’ll continue to talk to you.” (server stores the state of talking to client two, properly authenticated.)

client one:”Hi server.”

server :”Hi client one. You are authenticated, so I’ll continue to talk to you.” (server stores the state of talking to client one, properly authenticated.)

client one:*BOOM* (crashed, blue screen of death, user restarts session once machine reboots)

client two: “server, hook me up with twenty boxes of paper clips.”

client two: *WHOMP* (browser crashes, user restarts browser)

server: “done, server two….hey wait, I can’t respond to you. How strange.”

client one: “Hi server.”

server: “Client one, you just authenticated, and you’re trying to authenticate again? I have to reject your request. Bye.”

client two: “Hi server.”

server: “client two: you have an outstanding transaction, but now your session ID is different. Are you trying to trick me? Get out of here. Bye.”

client two: “Huh? I just loaded, and have no idea what you’re talking about.”

server: “You are in a messed up state. Your authentication is rejected. Call customer support at 1-800-….”
client two: “????”

The very helpful reply from the non-RESTful server is an especially nice twist.

The Comet architecture is based on long-lived http connections and pushes data to the client without an explicit request.

The above example uses Orbited and Django to build a simple chat web application.

http://advocacy.python.org/podcasts/

http://rubyconf2007.confreaks.com/

No contest. I love Python but we have a lot to learn in the PR department.