This should be mentioned too:
import ipdb; ipdb.set_trace()
If you didn't already, then go ahead and mess with it.
--
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/m
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
> u
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
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
Op 7 jan. 2013, om 05:57 heeft Mayur Patil
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
Hello there,
I want to understand how to get deep insight into Django code?
Thank You.
--
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/-/CcvuN
