On Wed, Apr 22, 2009 at 12:46:32PM -0700, Phil Mocek wrote: > [What you've repeatedly asked is] explained in the Django > settings documentation that I referenced earlier, that you > apparently did not read before asking your question or after I > helpfully suggested that you read it. It's also explained by > the in-built usage help that manage.py provides. You never > indicated where you'd already searched for the information you > seek, and it seems that you haven't searched at all.
Sheesh, it's also explained just five paragraphs into the second Google search result I cited. If you don't understand some part of the information that has been presented to you (information that you could very easily have found for yourself in the manner I demonstrated for you), by all means tell us what you're struggling with and someone will likely be willing to clarify for you. But please don't waste people's time by asking for things that you could easily have found before posting to the list -- *and* that you were very considerately directed to after you posted to the list. Quoting ESR: <http://www.catb.org/~esr/faqs/smart-questions.html#before> >> Before asking a technical question by e-mail, or in a >> newsgroup, or on a website chat board, do the following: >> >> 1. Try to find an answer by searching the archives of the forum >> you plan to post to. >> 2. Try to find an answer by searching the Web. >> 3. Try to find an answer by reading the manual. >> 4. Try to find an answer by reading a FAQ. >> 5. Try to find an answer by inspection or experimentation. >> 6. Try to find an answer by asking a skilled friend. >> 7. If you're a programmer, try to find an answer by reading the >> source code. >> >> When you ask your question, display the fact that you have done >> these things first; this will help establish that you're not >> being a lazy sponge and wasting people's time. Better yet, >> display what you have learned from doing these things. We like >> answering questions for people who have demonstrated they can >> learn from the answers. >> >> Use tactics like doing a Google search on the text of whatever >> error message you get (searching Google groups as well as Web >> pages). This might well take you straight to fix documentation >> or a mailing list thread answering your question. Even if it >> doesn't, saying "I googled on the following phrase but didn't >> get anything that looked promising" is a good thing to do in >> e-mail or news postings requesting help, if only because it >> records what searches won't help. It will also help to direct >> other people with similar problems to your thread by linking >> the search terms to what will hopefully be your problem and >> resolution thread. >> >> Take your time. Do not expect to be able to solve a complicated >> problem with a few seconds of Googling. Read and understand the >> FAQs, sit back, relax and give the problem some thought before >> approaching experts. Trust us, they will be able to tell from >> your questions how much reading and thinking you did, and will >> be more willing to help if you come prepared. Don't instantly >> fire your whole arsenal of questions just because your first >> search turned up no answers (or too many). >> >> Prepare your question. Think it through. Hasty-sounding >> questions get hasty answers, or none at all. The more you do to >> demonstrate that having put thought and effort into solving >> your problem before seeking help, the more likely you are to >> actually get help. >> >> Beware of asking the wrong question. If you ask one that is >> based on faulty assumptions, J. Random Hacker is quite likely >> to reply with a uselessly literal answer while thinking "Stupid >> question...", and hoping the experience of getting what you >> asked for rather than what you needed will teach you a lesson. -- Phil Mocek --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
