On 01/05/12 22:58, Ramiro Morales wrote:
> On Tue, May 1, 2012 at 11:04 AM, Sam Simmons <[email protected]> wrote:
>> For app/project templates I found the docs a little misleading when they say
>> 'Any option passed to the startapp command' will be added to the context.
>
> You' ve understood the documentation correctly. This is a feature that is
> currently (and AFAICT was DOA) not fully implemented because there is code to
> process and add the custom command line switches to the context but the
> validation that the management commands framework performs on the command line
> options isn't allowing them to pass.
This sounds like it would be a misfeature.
It is a golden rule of command line apps that typos in options passed to
the command are not silently ignored.
If I type:
django-admin.py startproject --tempate=/home/me/foo
I should get an exception, not the default template rendered with
"tempate=/home/me/foo".
The feature given in the patch on ticket #18277, is however, much more
like it - you have to pass the context using --add-context
Regards,
Luke
--
OSBORN'S LAW
Variables won't, constants aren't.
Luke Plant || http://lukeplant.me.uk/
--
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers?hl=en.
