yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: horizon
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1266676

Title:
  replace deprecated code for django-1.7

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  1.7

  See the Django 1.5 release notes for more details on these changes.

      The module django.utils.simplejson will be removed. The standard library provides json which should be used instead.
      The function django.utils.itercompat.product will be removed. The Python builtin version should be used instead.
      Auto-correction of INSTALLED_APPS and TEMPLATE_DIRS settings when they are specified as a plain string instead of a tuple will be removed and raise an exception.
      The mimetype argument to the __init__ methods of HttpResponse, SimpleTemplateResponse, and TemplateResponse, will be removed. content_type should be used instead. This also applies to the render_to_response() shortcut and the sitemap views, index() and sitemap().
      When HttpResponse is instantiated with an iterator, or when content is set to an iterator, that iterator will be immediately consumed.
      The AUTH_PROFILE_MODULE setting, and the get_profile() method on the User model, will be removed.
      The cleanup management command will be removed. It’s replaced by clearsessions.
      The daily_cleanup.py script will be removed.
      The depth keyword argument will be removed from select_related().
      The undocumented get_warnings_state()/restore_warnings_state() functions from django.test.utils and the save_warnings_state()/ restore_warnings_state() django.test.*TestCase methods are deprecated. Use the warnings.catch_warnings context manager available starting with Python 2.6 instead.
      The undocumented check_for_test_cookie method in AuthenticationForm will be removed following an accelerated deprecation. Users subclassing this form should remove calls to this method, and instead ensure that their auth related views are CSRF protected, which ensures that cookies are enabled.
      The version of django.contrib.auth.views.password_reset_confirm() that supports base36 encoded user IDs (django.contrib.auth.views.password_reset_confirm_uidb36) will be removed. If your site has been running Django 1.6 for more than PASSWORD_RESET_TIMEOUT_DAYS, this change will have no effect. If not, then any password reset links generated before you upgrade to Django 1.7 won’t work after the upgrade.

  
  This is connected with blueprint django-1point6

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1266676/+subscriptions