On 7/8/07, James Bennett <[EMAIL PROTECTED]> wrote:
> 1. Expand the default application skeleton, or differentiate somehow
> between a minimal, "traditional" app skeleton and a more robust one
> which includes files and directories oriented at a distributable
> application.
>
> 2. Spend a lot more
On 7/9/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 7/8/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > 1. Expand the default application skeleton, or differentiate somehow
> > between a minimal, "traditional" app skeleton and a more robust one
> > which includes files and directories or
On 7/9/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> A fair number of the questions asked regularly on the users list could
> be avoided if the point was made that Django code is just Python code
I think a fair number of people start learning Python at the same time
the start learning Djan
I thought you guys might appreciate some feedback from a total newbie.
I am trying to learn Django and Python and the same time, and greatly
appreciate the documentation available on Djangoproject and in the
Django Book. They are clearly one of Django's greatest strengths.
I have worked through
I definitely agree that some additional documentation is in order.
Over the past few months, I've released a couple apps that used to be
tied specifically to a project, and I had quite a bit of
back-and-forth on this list trying to figure out the best practices
for releasing them.
I think the sin
On 7/9/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I don't know if this is what Adrian was referring to, but I would
> think an ideal "project" would be nothing more than settings.py,
> urls.py (which might be split into multiple files), a set of templates
> and static media content. Essentially
On 7/9/07, James Bennett <[EMAIL PROTECTED]> wrote:
> That's pretty much what I've been doing for a good long while now;
> djangosnippets.org, for example, is a project that has a settings
> file, root URLConf and templates, and everything else lives inside the
> apps it uses.
Good to know I was
On Jul 9, 3:21 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On 7/9/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> > A fair number of the questions asked regularly on the users list could
> > be avoided if the point was made that Django code is just Python code
>
> I think a fair number
For each new site I work on I have a root folder which contains a copy
of Django, other 3rd party libs I need, and a Django project for my
site. I do this so I can upgrade or customise Django for each site
individually without breaking other sites. I'll probably switch back
to a common Django afte
On 7/9/07, cjl <[EMAIL PROTECTED]> wrote:
> Thanks again for all the hard work, and sorry for jumping in on this
> discussion.
For the record, there's absolutely no need to apologize for jumping
in! Your comments were very insightful -- I wish more relative
newcomers would participate in these so
10 matches
Mail list logo
