Hello,
since version 1.2, there has been no changes about this issue, which still
bothers me:
https://code.djangoproject.com/ticket/14916
In summary, the django dev server loads models.py of every INSTALLED_APP,
and thus (somehow) ensures proper initialization of models and signals.
But in p
After reading that ticket, I'm not sure what Alex and I are
disagreeing on. I was suggesting using django.utils.simplejson
internally until it's removed, so that at least people could be
consistent with django itself. That way, DjangoJSONEncoder would be a
simplejson.JSONEncoder (if simplejson is
On 13 avr. 2013, at 22:13, Jeremy Dunck wrote:
> After reading that ticket, I'm not sure what Alex and I are
> disagreeing on. I was suggesting using django.utils.simplejson
> internally until it's removed, so that at least people could be
> consistent with django itself. That way, DjangoJSONEn
There's a line in the django URL Dispatcher documentation that is pretty
weird:
The URLconf doesn’t look at the request method. In other words, all request
> methods – POST, GET, HEAD, etc. – will be routed to the same function for
> the same URL.
Well, why? Most modern web frameworks allow
On Sat, Apr 13, 2013 at 11:53 PM, Pakal wrote:
> Hello,
>
> since version 1.2, there has been no changes about this issue, which still
> bothers me:
> https://code.djangoproject.com/ticket/14916
>
> In summary, the django dev server loads models.py of every INSTALLED_APP,
> and thus (somehow) ens
This problem was gonna have to be eventually sorted through no matter what:
the endgame was decided to be "json from the standard library everywhere"
which means any projects doing simplejson.dumps([django internals]) would
inevitably be affected sooner or later. In theory it's just as distasteful
