On 19 oct. 2011, at 00:21, Rich Jones wrote:
> Here's some of what I propose. I'm not suggesting this be a canonical
> list of features by any means, I'm just suggesting that django have
> more convenient default settings. We should look at the most common
> conventions and best practices and shape
Thanks for the suggestions, Rich... I'll try not to repeat what others have
said, but have a couple notes to add:
should create ./static, ./uploads and ./newproj and ./newproj/
> templates
>
I could get behind static, and *maybe* even templates, but absolutely not
uploads. I would argue again
Hi all,
On Wed, Oct 19, 2011 at 5:50 AM, Gabriel Hurley wrote:
> Thanks for the suggestions, Rich... I'll try not to repeat what others have
> said, but have a couple notes to add:
>
> ()
>
> As for the rest: I don't believe in adding magic in order to save a couple
> lines of typing (explic
I've opened a ticket for improving the NoReverseMatch error:
https://code.djangoproject.com/ticket/17076
However, I'd still like to improve the documentation regarding which
patterns can be reversed. I don't fully understand the limitations
myself yet.
1. Can we provide an example of a pattern co
I think there is sufficient interest in the idea of a "how to organize your
Django project" page in the documentation that it would be worth beginning
work on a patch for one, much in the way that the "How to contribute to
Django"/"Spirit of contributing" page got started.
That means:
1. Ope
