Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Django 1.9 #282

Closed

Commits on May 2, 2016

  1. Upgrade to Django 1.9

    This is a fairly extensive commit, since most of the requirements had
    to be upgraded as well. Dependencies have been locked down to specific
    versions for consistency and troubleshooting. Notable changes:
    
      - Moved wsgi.py to a more standard location, updated apache config.
        Now referenced in roundware.settings.WSGI_APPLICATION
    
      - For roundware.api2, implemented the new Application Configuration
        structure. See http://stackoverflow.com/q/32795227/1943591
    
      - django-guardian now creates its own AnonymousUser in the database.
        Removed AnonymousUser references from fixtures to avoid conflicts.
        http://django-guardian.readthedocs.io/en/stable/configuration.html
    
      - ManyToManyField no longer accepts null=True
    
      - django.contrib.auth.models.User should not be accessed directly.
        Use django.conf.settings.AUTH_USER_MODEL instead
    
      - Django changed the way it loads models, which broke streaming.
        Moving django.setup() in roundwared.rwstreamd fixed the issue.
    
      - django_chartit is no longer maintained. Moved to django_chartit2
        This may require us to install jQuery and Highcharts manually
    
      - django.forms.models.save_instance has been removed.
        We are now calling save() instead, but it might need more testing.
        django/django@8656cf
        django/django@b11564
    IllyaMoskvin committed May 2, 2016
    Configuration menu
    Copy the full SHA
    42873a4 View commit details
    Browse the repository at this point in the history