After a few days' consideration, I've got some more crystalized
details about my proposal.
Here are the target result if this proposal is implementated:
1. User could configure serialization for each model.
2. In fact, user could configure the serialization details down to
each field of each mod
I've got some more crystalized details about my proposal.
Here are the target result if this proposal is implementated:
1. User could configure serialization for each model.
2. In fact, user could configure the serialization details down to
each field
of each model. That means:
3. The key n
On Sat, Apr 2, 2011 at 10:45 PM, Russell Keith-Magee
wrote:
> Secondly, it may be possible to play a trick on the template compiler.
> Jonas Obrist suggested this trick to me at Djangocon (US) last year;
> however, I haven't had a chance to dig into it any more.
>
> The trick goes something like t
On Fri, Apr 1, 2011 at 11:57 PM, Gregor Müllegger wrote:
> I suggest reading this proposal online: https://gist.github.com/898375
> It's exactly the same as below but formated nicely.
>
>
> GSoC 2011 Proposal - Revised form rendering
>
>
> Hi my name is
On Sat, Apr 2, 2011 at 17:04, Marti Raudsepp wrote:
> The patch is quite simple and so far has worked with all queries
> generated by Django, for a few different applications. It added a
> noticeable speed boost
Oh, I forgot to mention, I'm using the patch together with the
persistent connections
2011/4/2 Russell Keith-Magee :
> I think this would be a good way to structure the project -- i.e.,
> keep a clear conceptual separation between hooks and configuration
> options that need to be added to Django in order to make an external
> form rendering library possible, and the library that act
Hi,
Now 1.3's out the door, I'd like this to be looked at again, if possible.
http://code.djangoproject.com/ticket/2705
I'll re-apply Ramiro's patch locally and make sure everything still checks out
for me, and report back.
The latest version of the patch still applied cleanly for me and
On 2 April 2011 13:23, James Pic wrote:
> Hello everybody,
>
> Do you think uWSGI deserves a place in the official django documentation ?
>
> I think it should because it's easier, safer, faster and more secure
> than flup or mod_wsgi. Also, it made my sysadmin life really easy and
> that's someth
On Sat, Apr 2, 2011 at 5:20 AM, Carl Meyer wrote:
>
> On 04/01/2011 05:09 PM, Mikhail Korobov wrote:
>> Implementation:
>> https://bitbucket.org/kmike/django-widget-tweaks/src/0e9bac3c71bd/widget_tweaks/templatetags/widget_tweaks.py
>
> That's quite a neat app - I have some similar template filte
Hi list,
I wrote a proof of concept patch to add prepared statement support to
Django for the PostgreSQL backend. Note that it's just a hack to see
if this approach could work at all, I know it's badly written. :)
The patch is quite simple and so far has worked with all queries
generated by Djang
Hello everybody,
Do you think uWSGI deserves a place in the official django documentation ?
I think it should because it's easier, safer, faster and more secure
than flup or mod_wsgi. Also, it made my sysadmin life really easy and
that's something cool to share with the community.
In this case,
Hi, thanks for your fast feedback. I was really looking forward to your input,
I haven't reached you in IRC before.
2011/4/1 Carl Meyer :
> Hi Gregor,
>
> As you've probably seen in past threads, this is an area where I'm quite
> motivated to see some improvement. I think you've got quite a strong
12 matches
Mail list logo
