I can't really help you because I don't know the internal life cycle either. I'd just start with reading through the code, which isn't really that hard (and it is what I've been doing for my custom admin form behaviour).
If you have specific questions, you could post it here (or if it looks like you need to extend something that Django doesn't currently allow, maybe try the django-dev list). The members here might be able to offer better solutions if you let us know what you are trying to optimise, because someone here might have experienced the problem before (and done the digging that you're after). Also, I'm sure you've heard all the bad things that are said about premature optimisation. Write your code first according to Django conventions, then optimise. On 20 June 2010 19:56, Sameer Rahmani <[email protected]> wrote: > thanks for your consideration , i know that this is a painful matter > and need extra work > but i need to understand this cycle to write some peace of code for my > project that optimize > some actions also i really love to contribute to django, so please guide me :) > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
