Changes between Version 123 and Version 124 of BackwardsIncompatibleChanges


Ignore:
Timestamp:
09/09/2007 05:24:32 PM (8 years ago)
Author:
adrian
Comment:

Added "django-admin.py and manage.py now require subcommands to precede options"

Legend:

Unmodified
Added
Removed
Modified
  • BackwardsIncompatibleChanges

    v123 v124  
    363363
    364364Update your code by performing an explicit {{{order_by()}}} on the {{{QuerySet}}} you pass to {{{archive_year}}} or add an {{{ordering}}} option to your model's {{{class Meta}}}.
     365
     366== django-admin.py and manage.py now require subcommands to precede options ==
     367
     368In [6075], {{{django-admin.py}}} and {{{manage.py}}} were changed so that any options (e.g., {{{--settings}}}) must be specified *after* the subcommand (e.g., {{{runserver}}}).
     369
     370This used to be accepted:
     371{{{django-admin.py --settings=foo.bar runserver}}}
     372
     373Now, options must come after the subcommand:
     374{{{django-admin.py runserver --settings=foo.bar}}}
Back to Top