Hi Justin,
On Tue, Sep 23, 2014 at 7:10 AM, Justin Holmes
wrote:
> Currently, we perform a sanity check to provide a useful error message
> if a view returns None:
>
>
> https://github.com/django/django/blob/1101467ce0756272a54f4c7bc65c4c335a94111b/django/core/handlers/base.py#L138
>
> However,
Currently, we perform a sanity check to provide a useful error message
if a view returns None:
https://github.com/django/django/blob/1101467ce0756272a54f4c7bc65c4c335a94111b/django/core/handlers/base.py#L138
However, if a view returns a different object (say, a string), we
don't have a similarly
On Saturday, September 20, 2014 12:25:02 PM UTC-4, Ryan Hiebert wrote:
>
> Being the idealist I am, I hope we can find a way to rid ourselves of the
> pain of cgi. I'd be more than willing to help, but my help would probably
> be more of a hindrance because of the limited exposure I've had with
Replying to myself:
On Sunday 21 September 2014 20:59:46 Shai Berger wrote:
> Hi,
>
> I'm looking into the details of migrations a little, and I ran into this
> issue.
>
> I have two migrations: The first creates a model, the second adds another
> model and a field to the first model. I'd expect
