← Back to branch summary

~ubuntu-branches/ubuntu/natty/python-django/natty-security

« back to all changes in this revision

Viewing changes to docs/releases/1.0-porting-guide.txt

  • Committer: Bazaar Package Importer
  • Author(s): Jamie Strandboge
  • Date: 2011-02-17 13:34:07 UTC
  • mfrom: (1.1.13 upstream) (4.4.12 sid)
  • Revision ID: james.westby@ubuntu.com-20110217133407-rwr88elhhq6j7ba0
Tags: 1.2.5-1ubuntu1
https://launchpad.net/bugs/719031
* Merge from Debian for security fixes (LP: #719031). Remaining changes:
  - debian/control: don't Build-Depends on locales-all, which doesn't exist
    in natty
* Drop the following patches, now included upstream:
  - debian/patches/07_security_admin_infoleak.diff
  - debian/patches/08_security_pasword_reset_dos.diff

Show diffs side-by-side

added added

removed removed

Lines of Context:
docs/releases/1.0-porting-guide.txt
373
373
  ``sender=None``
374
374
 
375
375
* Make any custom signals you've declared into instances of
376
 
  :class:`django.dispatch.Signal`` instead of anonymous objects.
 
376
  :class:`django.dispatch.Signal` instead of anonymous objects.
377
377
 
378
378
Here's quick summary of the code changes you'll need to make:
379
379
 
626
626
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
627
627
 
628
628
``django.http.HttpResponse.headers`` has been renamed to ``_headers`` and
629
 
:class:`HttpResponse`` now supports containment checking directly. So use
630
 
``if header in response:`` instead of ``if header in response.headers:``.
 
629
:class:`~django.http.HttpResponse` now supports containment checking directly.
 
630
So use ``if header in response:`` instead of ``if header in response.headers:``.
631
631
 
632
632
Generic relations
633
633
-----------------
661
661
Running management commands from your code
662
662
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
663
663
 
664
 
:mod:`django.core.management`` has been greatly refactored.
 
664
:mod:`django.core.management` has been greatly refactored.
665
665
 
666
666
Calls to management services in your code now need to use
667
667
``call_command``. For example, if you have some test code that calls flush and