About Understanding of source code

[Mayur Patil]

Hello there,

  I want to understand how to get deep insight into Django code?

  Thank You.

[Rohan Jain]

I would suggest you to start by looking into the contrib apps. This would give you great insights onto writing Django apps. Now that you are already in the source code, you can stumble into the rest of it or even the core. This way has been particularly helpful to me.

Also, you might want to look into this great talk by James Bennett, titled "Django in Depth": http://www.youtube.com/watch?v=t_ziKY1ayCo

--

Rohan Jain

--
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/-/CcvuNeLYrJsJ.
To post to this group, send email to django-d...@googlegroups.com.
To unsubscribe from this group, send email to django-develop...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.

[Diederik van der Boor]

Hi,

What I find really valuable is using a editor/tool that allows you to jump to class/method/function definitions.

I'm using PyCharm for Django development and it really helps me to dive into Django code (Cmd+Click on a symbol).

Greetings,

Diederik

[ptone]

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.

FWIW,

-Preston

[Amirouche B.]

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, you can also precise a component for instance if you are interested in the ORM.

Also one way to learn little by little while still keeping an eye on what is coming is to watch django on github (or subscribe using a feed reader). Also there is mailling list for the tickets (prefered)

Regards,

Amirouche

[is_null]

This should be mentioned too:

    import ipdb; ipdb.set_trace()

If you didn't already, then go ahead and mess with it.