Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Django 1.11 Incompatibilities

See original GitHub issue

The overall functionality to store actions via signals seems to work nicely in Django 1.11, but trying to use the activity_stream and display_action templatetags I came across some small things that are broken due to changes in 1.11.

  • actstream/templatetags/, line 96:

    return render_to_string(templates, context)

    Context is a django.template.context.Context instance here, but in 1.11 it must be a simple dict,

    return render_to_string(templates, context.flatten())

    would possibly fix that, haven’t fully tested it yet.

  • actstream/, top of the file:

        from django.conf.urls import url, patterns
    except ImportError:
        from django.conf.urls.defaults import url, patterns

    The patterns() function is not available anymore, either the url patterns need some rework or you’d have to provide your own vendorized version. In 1.9 it says:

    django.conf.urls.patterns() is deprecated and will be removed in Django 1.10. Update your urlpatterns to be a list of django.conf.urls.url() instances instead.

  • actstream/ All usage of render_to_response() is a problem, see

    The dictionary and context_instance parameters for the following functions are removed: django.shortcuts.render() django.shortcuts.render_to_response()

The changelog tells me that the latest, officially supported Django version is 1.9. Are there any plans yet to extend support to Django 1.10+?

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:3
  • Comments:31 (3 by maintainers)

github_iconTop GitHub Comments

cb109commented, Jul 12, 2017

Thanks for your work @cmwaura 🙇

rrmerugucommented, May 28, 2017

whats the status of this PR? Eagerly waiting for 1.11 support

Read more comments on GitHub >

github_iconTop Results From Across the Web

Django 1.11 release notes
Python compatibility¶. Django 1.11 requires Python 2.7, 3.4, 3.5, 3.6, or 3.7 (as of 1.11.17). We highly recommend and only officially ...
Read more >
Incompatibility with Django 1.11 #277 - syrusakbary/pyjade
templatize method has moved to a different module So now raises AttributeError: 'module' object has no attribute 'templatize'
Read more >
Djangorestframework > 3.11 Incompatible with Django 1.11 ...
Create a new (version) django project and installl libraries as a requirements.txt , by this way you just need to replace main files...
Read more >
Django 1.11 and PostgreSQL 10 compatibility - Google Groups
Django supports PostgreSQL 9.3 and higher. psycopg2 2.5.4 or higher is required, though the latest release is recommended. I ...
Read more >
Fix Django 1.11 Compatibility · 601e1ad44c ... - OpenDev
django_openstack_auth - RETIRED, A Django authentication backend for use with the OpenStack Keystone Identity backend. ... Fix Django 1.11 Compatibility.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found