On Jun 6, 12:30 pm, "Amit Upadhyay" <
upadh...@gmail.com> wrote:
> Hey Shabda,
>
> Those are nice tips indeed. One of the things that you may have to worry
> about when a project starts growing large over time is django trunk. There
> is just too much happening in trunk that you would not want to base your new
> projects on Django-0.96, last official release, so will base off from some
> revision of trunk. And while django developers are careful in not breaking
> trunk and announce backward incompatible changes, you may still find
> yourself using particular revisions of django trunk. Another thing is many
> times you will find that neat patch that does exactly what you want to do
> but have not been checked in in django yet, and it may make perfect sense to
> just apply them. Managing all this will become an issue, and in my pre git
> era I just checked in django along with my rest of the code. Today I would
> just use django's git [
http://repo.or.cz/w/django.git/] and maintain my own
> django branch, doing control updates and checking in my selected patches for
> django. You may have to do this or similar for a few other django or
> otherwise external libraries too, I had to make some changes in twitter
> module and pyfacebook etc to support my website, all checked in along with
> my project.
>
>
>
> On Thu, Jun 5, 2008 at 9:48 PM, shabda raaj <
shabda.r...@gmail.com> wrote:
>
> > 1. Break your project into logical areas. Let each logical area be a
> > django app.
> > 2. Readhttp://
> > Make each app a reusable app. This is going to save you a lot of
> > headaches 2 months down the line.
> > 3. Readhttp://