On 22/02/2012, at 11:01 AM, Daryl wrote:

> Hi All,
> 
> When running tests I often end up crashing things and when restarting
> the tests i get the line;
> 
> Creating test database for alias 'default'...
> Got an error creating the test database: (1007, "Can't create database
> 'test_xxxxx'; database exists")
> Type 'yes' if you would like to try deleting the test database
> 'test_xxxxx', or 'no' to cancel:
> 
> So i type 'yes' and finish the tests, then i spend an hour searching
> django.org to find the flag needed to suppress this message.
> 
> Would other developers support the suggestion that the lines below in
> test/util.py be changed to add a helpful little line as suggested
> below???

I have to say I'm not especially enthused by this idea. Documentation for the 
--noinput command is available from the --help option on every command where it 
is applicable:

./manage.py test --help

And on the list of common options for all management commands (which is a 
top-level link in Django's documentation).

https://docs.djangoproject.com/en/1.3/ref/django-admin/#common-options

It also turns up as the first result if you search the documentation for 
"suppress".

The only room for improvement I can see is that the ``test`` command doesn't 
currently contain a specific mention that --noinput is a valid option. Other 
commands have such a statement -- see the docs for ``syncdb`` or ``flush`` for 
an example.

I'm not sure why it took you an hour to find this information. I'm certainly 
open to any suggestions as to how we could organize our documentation better to 
make it easier to find this information. However, I don't accept that making 
warning messages even more verbose is a helpful solution to this problem. 

Yours,
Russ Magee %-)

-- 
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.

Reply via email to