Re: Improving Class based views names

Hi Benny, On 03/19/2011 05:41 PM, daonb wrote: > Migration to the beta was quite smooth except for two names that broke > my code: `pk` & `get_context_data`. The first comes from `models` and > is now used instead of `object_id` in urls and views. It also broke > compatibility with

Re: Default project layout / directory structure

> I think, it's a good idea to add new option to startapp command There is django-extensions which has a create_app command that takes a --template switch. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email

Re: Improving Class based views names

On Sunday, March 20, 2011, daonb wrote: > Hi, > > I'm in the middle of re-factoring a pretty active open parliament > project into 1.3. I've been an early adaptor of class based views, > using it of Jacob's fork. > > Migration to the beta was quite smooth except for two names

Re: State of X-Sendfile support?

On Sunday, March 20, 2011, Pascal Germroth wrote: > Hi, > > I want to use X-Sendfile to serve some medium-sized files. There > doesn't seem to be built-in support for this, although the soc2009/ > http-wsgi-improvements branch looks like somebody attempted to > implement

dumpdata, json, management commands and utf8

./manage.py dumpdata --format=json command produces unreadable output for non-ascii symbols now (they are encoded as \u ). Such encoding is not required according to http://www.ietf.org/rfc/rfc4627.txt (section 2.5): "All Unicode characters may be placed within the quotation marks except for

State of X-Sendfile support?

Hi, I want to use X-Sendfile to serve some medium-sized files. There doesn't seem to be built-in support for this, although the soc2009/ http-wsgi-improvements branch looks like somebody attempted to implement HttpResponseSendFile (although it seems to use the slow path). Building a proper

Improving Class based views names

Hi, I'm in the middle of re-factoring a pretty active open parliament project into 1.3. I've been an early adaptor of class based views, using it of Jacob's fork. Migration to the beta was quite smooth except for two names that broke my code: `pk` & `get_context_data`. The first comes from

Re: Homogenization of User and UserProfile

On 03/18/2011 07:22 AM, Carl Meyer wrote: Don't use AUTH_PROFILE_MODULE or .get_profile(). As far as I'm concerned they bring almost nothing to the table except for the "there can be only one" restriction +1 Just use OneToOneField and the regular ORM access descriptors, and you can have as