On Tuesday, January 8, 2013 6:54:41 PM UTC+1, ptone wrote: > > You might want to attempt to write a patch for an open issue - reading the > source code is one thing and you may learn a bit. But dissecting the source > code when you have the purpose to fix a problem, gives you a much better > understanding of how things are working - as you NEED to understand them in > order to properly fix/extend them. Just reading through it allows you to > too easily skip over things you don't really understand.
Also you can read the discussions that lead to the code, here is those that I know of: - https://code.djangoproject.com/wiki/NewformsAdminBranch - https://code.djangoproject.com/wiki/ClassBasedViews To find easy bugs, check easy picking in trac custom query<https://code.djangoproject.com/query?status=assigned&status=new&easy=1&col=id&col=summary&col=status&col=owner&col=type&col=component&order=priority>, you can also precise a component for instance if you are interested in the ORM<https://code.djangoproject.com/query?status=assigned&status=new&component=Database+layer+(models%2C+ORM)&easy=1&col=id&col=summary&col=status&col=owner&col=type&col=component&order=priority> . Also one way to learn little by little while still keeping an eye on what is coming is to watch django on github <https://github.com/django/django/> (or subscribe using a feed reader<https://github.com/django/django/commits/master.atom> ). Also there is mailling list for the tickets<https://groups.google.com/forum/?fromgroups#!forum/django-updates> (prefered) Regards, Amirouche -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/142VK7-i_hkJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
