django-restapi's Introduction

~jflatow

To bootstrap on a machine w/ my Dropbox:

cd ~/Dropbox/Code/stencil/users/jflatow

Otherwise, if not using Dropbox:

cd /usr/local/src/etc/users/jflatow

Then:

git clone [email protected]:jflatow/jflatow.git
cd jflatow
./install

To make a change to emacs prefs:

emacs .emacs
./install

Notes to future self

On the occasion of my next reboot, there should be no ambiguity about how to recover my session.

All my instructions to myself for bootstrapping packages should live in this repo. Notes for emacs are in .emacs itself.

TODO: macbook from scratch: /usr/local/{src,etc} /usr/local/src/lang/{C,JavaScript,Python,Plato,...} /usr/local/src/scratch/{emacs,web,...} latest emacs, Emacs.app Python3 matplotlib ipython + Jupyter + notebeook setup? Chrome canary + React dev tools?

django-restapi's People

Watchers

django-restapi's Issues

Root XML node of error response reveals that django is in use

1. Create a simple model based resource
2. Issue a get request for an xml response, passing invalid primary key
3. In the response, the Root xml node is <django-error>. This is hard coded 
on lines 152 and 160 in responder.py

It seems to me that there is no need for the error XML to expose the fact 
that django (or django-restapi) is in use - it should simply represent the 
error. I'm far from an expert in XML conventions, so I have no idea whether 
something generic like 'error' would be appropriate.

In order to not break existing applications, could it be changed to default 
to 'django-error' but otherwise be override-able, such as in the attached 
patch?

Original issue reported on code.google.com by [email protected] on 31 May 2010 at 7:00

Attachments: