Well, having started looking over the flup source, I can see a lot of useful code to crib, as well as a few critical path bits that can be optimised [without even reducing readability!]
So, if you feel like helping out with django-fastcgi ... I'm happy for the help :) -- Curtis On 23 July 2013 03:25, Some Developer <[email protected]> wrote: > On 22/07/13 10:00, Russell Keith-Magee wrote: > >> The hope is to start accelerating the release cycle slightly; however, >> this also depends on someone actually doing the work :-) >> > > Sounds good. I'd love to start helping with Django myself but I feel a bit > lost when it comes to useful things to do. Maybe I'll start checking out > the bug tracker and seeing what I can do there. > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > django-developers+unsubscribe@**googlegroups.com<django-developers%[email protected]> > . > To post to this group, send email to > django-developers@**googlegroups.com<[email protected]> > . > Visit this group at > http://groups.google.com/**group/django-developers<http://groups.google.com/group/django-developers> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
