Changeset 7619
- Timestamp:
- 06/11/08 22:36:48 (4 months ago)
- Files:
-
- django/trunk/docs/authentication.txt (modified) (2 diffs)
- django/trunk/docs/django-admin.txt (modified) (1 diff)
- django/trunk/docs/faq.txt (modified) (8 diffs)
- django/trunk/docs/sessions.txt (modified) (2 diffs)
- django/trunk/docs/settings.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/authentication.txt
r7590 r7619 271 271 manage.py createsuperuser --username=joe --email=joe@example.com 272 272 273 You will be prompted for a password. Once entered, the user is created. If you274 leave off the ``--username`` or the ``--email`` option, It will prompt you for 275 those values as well.273 You will be prompted for a password. After you enter one, the user will be 274 created immediately. If you leave off the ``--username`` or the ``--email`` 275 options, it will prompt you for those values. 276 276 277 277 If you're using an older release of Django, the old way of creating a superuser … … 280 280 python /path/to/django/contrib/auth/create_superuser.py 281 281 282 Where ``/path/to`` is the path to the Django codebase on your filesystem. The283 ``manage.py`` command is prefer ed since it'll figureout the correct path and282 ...where ``/path/to`` is the path to the Django codebase on your filesystem. The 283 ``manage.py`` command is preferred because it figures out the correct path and 284 284 environment for you. 285 285 django/trunk/docs/django-admin.txt
r7615 r7619 105 105 106 106 When run interactively, this command will prompt for a password for 107 the new superuser account ; when run non-interactively, no password108 will be set and the superuser account will not be able to log in until107 the new superuser account. When run non-interactively, no password 108 will be set, and the superuser account will not be able to log in until 109 109 a password has been manually set for it. 110 110 111 111 The username and e-mail address for the new account can be supplied by 112 112 using the ``--username`` and ``--email`` arguments on the command 113 line ; if not supplied, ``createsuperuser`` will prompt for them when114 running interactively.113 line. If either of those is not supplied, ``createsuperuser`` will prompt for 114 it when running interactively. 115 115 116 116 This command is only available if Django's `authentication system`_ django/trunk/docs/faq.txt
r7602 r7619 227 227 Short answer: When we're comfortable with Django's APIs, have added all 228 228 features that we feel are necessary to earn a "1.0" status, and are ready to 229 begin maintaining backwards compatibility. 229 begin maintaining backwards compatibility. 230 230 231 231 The merging of Django's `Queryset Refactor branch`_ went a long way toward Django … … 261 261 would be happy to help you. 262 262 263 You might also be interested in posting a job to http://djangogigs.com/ . 264 If you want to find Django-capable people in your local area, try 263 You might also be interested in posting a job to http://djangogigs.com/ . 264 If you want to find Django-capable people in your local area, try 265 265 http://djangopeople.net/ . 266 266 … … 647 647 .. _creating users: ../authentication/#creating-users 648 648 649 Getting Help649 Getting help 650 650 ============ 651 651 … … 654 654 655 655 If this FAQ doesn't contain an answer to your question, you might want to 656 try the `django-users mailing list`_. Feel free to ask any question related 657 to installing, using, or debugging Django. 658 659 If you prefer IRC, the `#django IRC channel`_ on freenode is an active660 community of helpful individuals who may be able to solve your problem. 656 try the `django-users mailing list`_. Feel free to ask any question related 657 to installing, using, or debugging Django. 658 659 If you prefer IRC, the `#django IRC channel`_ on the Freenode IRC network is an 660 active community of helpful individuals who may be able to solve your problem. 661 661 662 662 .. _`django-users mailing list`: http://groups.google.com/group/django-users … … 667 667 668 668 django-users_ has a lot of subscribers. This is good for the community, as 669 there are lot of people that cancontribute answers to questions.669 it means many people are available to contribute answers to questions. 670 670 Unfortunately, it also means that django-users_ is an attractive target for 671 spammers. 671 spammers. 672 672 673 673 In order to combat the spam problem, when you join the django-users_ mailing 674 list, we manually moderate the first message you send to the list. This means 675 that spammers get caught, but it also means that your first question to the 674 list, we manually moderate the first message you send to the list. This means 675 that spammers get caught, but it also means that your first question to the 676 676 list might take a little longer to get answered. We apologize for any 677 677 inconvenience that this policy may cause. … … 679 679 .. _django-users: http://groups.google.com/group/django-users 680 680 681 Nobody on django-users answered my question ?What should I do?681 Nobody on django-users answered my question! What should I do? 682 682 -------------------------------------------------------------- 683 683 684 Wait. Ask again later. Try making your question more specific, or provide 685 a better example of your problem. 686 687 Remember, the readers of django-users_ are all volunteers. If nobody has 688 answered your question, it may be because nobody knows the answer, it may 689 be because nobody can understand the question, or it may be that everybody 690 that can help is extremely busy. 691 692 Resist any temptation to mail the `django-developers mailing list`_ in an 693 attempt to get an answer to your question. django-developers_ is for discussing 694 the development of Django itself. Attempts to use django-developers_ as 695 a second-tier support mechanism will not be met an enthusiastic response. 696 697 .. _`django-developers mailing list`: http://groups.google.com/group/django-developers 684 Try making your question more specific, or provide a better example of your 685 problem. 686 687 As with most open-source mailing lists, the folks on django-users_ are 688 volunteers. If nobody has answered your question, it may be because nobody 689 knows the answer, it may be because nobody can understand the question, or it 690 may be that everybody that can help is busy. One thing you might try is to ask 691 the question on IRC -- visit the `#django IRC channel`_ on the Freenode IRC 692 network. 693 694 You might notice we have a second mailing list, called django-developers_ -- 695 but please don't e-mail support questions to this mailing list. This list is 696 for discussion of the development of Django itself. Asking a tech support 697 question there is considered quite impolite. 698 698 699 .. _django-developers: http://groups.google.com/group/django-developers 699 700 … … 709 710 -------------------------------------------------------- 710 711 711 If you think you have found a security problem with Django, please send 712 a message to security@djangoproject.com. This is a private list only 713 open to long-time, highly trusted Django developers, and its archives 714 are not publicly readable. 712 If you think you've found a security problem with Django, please send a message 713 to security@djangoproject.com. This is a private list only open to long-time, 714 highly trusted Django developers, and its archives are not publicly readable. 715 715 716 716 Due to the sensitive nature of security issues, we ask that if you think you 717 have found a security problem, *please* don't send a message to one of the 717 have found a security problem, *please* don't send a message to one of the 718 718 public mailing lists. Django has a `policy for handling security issues`_; 719 while a defect is outstanding, we would like to minimize any damage that 719 while a defect is outstanding, we would like to minimize any damage that 720 720 could be inflicted through public knowledge of that defect. 721 721 … … 743 743 functionality, and Django's developers have to review and prioritize. 744 744 745 On top of that - the team working on Django are all volunteers. As a result,746 the amount of time that we have to work on Django is limited, and will vary747 from week to week depending on how much spare time we have. If we are busy, we 748 may notbe able to spend as much time on Django as we might want.745 On top of that: the people who work on Django are all volunteers. As a result, 746 the amount of time that we have to work on the framework is limited and will 747 vary from week to week depending on our spare time. If we're busy, we may not 748 be able to spend as much time on Django as we might want. 749 749 750 750 Besides, if your feature request stands no chance of inclusion in Django, we django/trunk/docs/sessions.txt
r7586 r7619 140 140 141 141 * If ``value`` is a ``datetime`` or ``timedelta`` object, the 142 session will expire at that specific time.143 144 * If ``value`` is ``0`` thenthe user's session cookie will expire145 when the irbrowser is closed.142 session will expire at that specific date/time. 143 144 * If ``value`` is ``0``, the user's session cookie will expire 145 when the user's Web browser is closed. 146 146 147 147 * If ``value`` is ``None``, the session reverts to using the global … … 169 169 170 170 Returns either ``True`` or ``False``, depending on whether the user's 171 session cookie will expire when the irbrowser is closed.171 session cookie will expire when the user's Web browser is closed. 172 172 173 173 You can edit ``request.session`` at any point in your view. You can edit it django/trunk/docs/settings.txt
r7538 r7619 394 394 DEBUG_PROPAGATE_EXCEPTIONS 395 395 -------------------------- 396 397 **New in Django development version** 396 398 397 399 Default: ``False``
