Changes between Version 31 and Version 32 of IrcFAQ
- Timestamp:
- Mar 28, 2007, 4:04:19 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
IrcFAQ
v31 v32 32 32 = Django questions = 33 33 34 == Which version should I use, the 0.9 5.1release or the Subversion checkout? == #WhichVersion34 == Which version should I use, the 0.96 release or the Subversion checkout? == #WhichVersion 35 35 36 The 0.9 5.1 release is the most well-tested. That said, many people run sites based on a Subversion checkout happily. If you '''do''' use a Subversion checkout, note that you don't need to run {{{setup.py}}} -- just make sure that the checkout is on your Python path.36 The 0.96 release is well-tested and stable, and is best for production deployments. Tracking the development version of Django through a Subversion checkout can be nice if there's a new feature you really want, but does require you to pay more attention to what's going on in Django development -- if a backwards-incompatible change is introduced, you'll need to be watching the development timeline to notice it and change your code to suit, where sticking to official releases means that you get a list of any changes you need to make in the release notes. 37 37 38 Django 0.96 will be released in the near future, and it will be recommended that production deployments stick to that release once it's out; there will be some backwards-incompatible changes in Django after 0.96, and the easiest migration plan is probably to run on 0.96 until that's done, then migrate your code all in one step.38 There will be several backwards-incompatible changes before the next release of Django (for example, the workings of the admin app will be changing), so it's officially recommended that production deployments stick to the 0.96 release until the next release is ready. 39 39 40 40 == Should I read the documentation on the djangoproject.com website, or djangobook.com? == #WhichDocs 41 41 42 Start with the [http://www.djangoproject.com/documentation/ documentation] here . This is especially true if you're using 0.95.1, since the version the examples on djangobook.com are based on the development version of Django, which contains several features which were not present in the 0.95.1 release (but which will be present in the upcoming 0.96 release).42 Start with the [http://www.djangoproject.com/documentation/ documentation] here, and then have a look at the book if you're interested; the documentation on djangoproject.com includes the official tutorial, and a number of comprehensive references which aren't currently available in the book. 43 43 44 44 == What does `'function' object has no attribute 'rindex'` mean? == #WeirdError1 45 45 46 This error is a telltale sign that you're trying to follow djangobook.com with a version of Django that's too old. See previous question.46 This error is a telltale sign that you're trying to use examples in the Django book with an older version of Django -- the book includes examples which rely on features introduced in Django 0.96. 47 47 48 48 == How do I extend a model? I want to subclass django.contrib.auth.models.User. == #ModelSubclassing … … 98 98 == I have created several users, but only the superuser is able to log into the admin == #OrdinaryUserCantLoginAdmin 99 99 100 In .95 and prior releases, you cannot put a plain password when creating a new user in admin. You have to generate the password and put the hash. Or you have to do create_user in the shell. Or maybe you have not set the user as staff - a user without staff priveledges cannot login to admin. 100 In .95 and prior releases, you cannot put a plain password when creating a new user in admin -- the form expects a hashed password in the format which will be stored in the database. In Django 0.96 and later, this is not a problem. 101 102 Also, keep in mind that admin access requires the "is_active" and "is_staff" boxes to be checked for the user. 101 103 102 104 == When will the next release be out? -or- When will X branch be done? == #AreWeThereYet