> I've started to write an application for Google Summer of
> Code, and I would LOVE any feedback you can possibly give me.
> Please comment on both language and content.
I guess my first concern/interest/question would be "what makes
your proposal different from {{revision_control_system}}?" Since
Django is pure Python (with perhaps a slight dependency on PIL),
using Subversion has worked for the Django project, the Django
site, and has worked for applications we do at work.
I must say, when I just installed Django on my iBook this
afternoon ('bout time :) it was as easy as a SVN checkout (okay,
with a small detour to get Subversion and both MySQL and
SQLite3). Then I installed one of my test projects from my SVN
repository. Another simple "svn co" and I was up and running.
Perhaps you're proposing a dependency-tracking component to
distribute projects/apps? Ways to specify that module X relies
on module Y, or app Z (and perhaps auto-fetch those dependencies
during installation)? And how does it differ from Eggs (or
setup-tools)?
I don't mean to rain on your parade, so perhaps you envision
something I missed in my understanding? But clarifying the value
your project brings (or what hole it fills in current
capabilities) would greatly strengthen your proposal.
Just my first impressions and ramblings...
-tkc
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
