zsoldosp / django-currentuser

Conveniently store reference to request user on thread/db level.

django-currentuser

Conveniently store reference to request user on thread/db level.

• Quickstart
• Differences to django-cuser
• Supported Versions
• Release Notes
• Contributing
  • Reporting issues/improvements
  • Pull Requests
  • Setting up all Python versions
  • Code of Conduct
  • Contributors

Quickstart

Install django-currentuser:

pip install django-currentuser

Add it to the middleware classes in your settings.py:

MIDDLEWARE = (
    ...,
    'django_currentuser.middleware.ThreadLocalUserMiddleware',
)

Then use it in a project:

from django_currentuser.middleware import (
    get_current_user, get_current_authenticated_user)

# As model field:
from django_currentuser.db.models import CurrentUserField
class Foo(models.Model):
    created_by = CurrentUserField()
    updated_by = CurrentUserField(on_update=True)

Differences to django-cuser

Both libraries serve the same purpose, but be aware of these differences (as of django-cuser v.2017.3.16):

• django-currentuser's CurrentUserField stores the reference to the request user at initialization of the model instance and still allows you to overwrite the value before saving. django-cuser sets the value in the pre_save handler of the field just before writing it to the database. Intermediate changes will be ignored.
• django-cuser deletes the user reference from the thread after finishing a response and it will therefore no longer be available for testing purposes.

Supported Versions

• for django-currentuser`, fixes are always made against the latest version
• for Python, support is guided by https://devguide.python.org/versions/#supported-versions
• for Django, support is guided by https://docs.djangoproject.com/en/dev/faq/install/#what-python-version-can-i-use-with-django and https://www.djangoproject.com/download/#supported-versions (assuming the Python version listed there is supported)

Release Notes

• 0.7.0 * add support for Django 5.0 * add support for Python 3.12 * drop support for Django 4.0 and 4.1
• 0.6.1
  • remove project transfer warning from README in order not to scare people away from the project
• 0.6.0
  • add support for Django 4.0, 4.1, and 4.2
  • add support for Python 3.11
  • drop support for Python 3.6 and 3.7
• 0.5.3 - add support for Django 3.2 and Python 3.9
• 0.5.2 - Fixed Django deprecation warning about using ugettext_lazy()
• 0.5.1 - add support for Django 3.1 and Python 3.8
• 0.5.0 - add support for update on save (thank you @felubra) - no longer build on Python 3.5, deprecated
• 0.4.3 - add support for Django 3.0
• 0.4.2 - Minor fix for supported Django and Python versions
• 0.4.0 - update supported versions
  • drop support for Python 3.4
  • drop support for Django 2.0
  • add support for Python 3.7
  • add support for Django 2.2
  • update tox3travis.py to not loose deployment feature
• 0.3.4 - Use public Travis for packaging to remove dependency on outdated build system
• 0.3.3 - drop Python 3.7 support due to build process problems
• 0.3.1 - attempt to add Python 3.7 support
• 0.3.0 - update supported versions according to https://www.djangoproject.com/download/#supported-versions and https://devguide.python.org/#status-of-python-branches
  • drop support for Python 3.2
• 0.2.3 - support custom user model, drop Django 1.10 support
• 0.2.2 - support Django 2.0
• 0.2.1 - version fixes #9
  • support Django 1.11.x and not just 1.11.0
• 0.2.0 - New middleclass format
  • Adapt to new object based middle class format of Django 1.10+
  • Drop support for deprecated Django versions 1.8 and 1.9
• 0.1.1 - minor release
  • suppress warning for passed kwargs as long as they match the defaults (avoids them being printed during running tests when fields are cloned)
• 0.1.0 - initial release
  • provides middleware + methods to set + retrieve reference of currently logged in user from thread
  • provides CurrentUserField that by default stores the currently logged in user
  • supports Django 1.10, 1.11 on python 2.7, 3.4, 3.5, and 3.6 - as per the official django docs

Contributing

As an open source project, we welcome contributions.

The code lives on github.

Reporting issues/improvements

Please open an issue on github or provide a pull request whether for code or for the documentation.

For non-trivial changes, we kindly ask you to open an issue, as it might be rejected. However, if the diff of a pull request better illustrates the point, feel free to make it a pull request anyway.

Pull Requests

• for code changes
  • it must have tests covering the change. You might be asked to cover missing scenarios
  • the latest flake8 will be run and shouldn't produce any warning
  • if the change is significant enough, documentation has to be provided

To trigger the packaging, run make release on the master branch with a changed version number.

Setting up all Python versions

sudo apt-get -y install software-properties-common
sudo add-apt-repository ppa:fkrull/deadsnakes
sudo apt-get update
for version in 3.8 3.9 3.10 3.11; do
  py=python$version
  sudo apt-get -y install ${py} ${py}-dev
done

Code of Conduct

As it is a Django extension, it follows Django's own Code of Conduct. As there is no mailing list yet, please use github issues

Contributors

Current maintainer: @zsoldosp Initial development & maintenance: @PaesslerAG

For contributors, see github contributors.

django-currentuser's Issues

Error when making migrations and migrating

The following error appears when making migrations and migrating:
UserWarning: You passed an argument to CurrentUserField that will be ignored. Avoid args and following kwargs: default, null, to.

How can this be avoided?

I use Python 3.9 and Django 3.1.6

support for django 4

cannot update the django version 3.0 to 4.1

Release version 0.4.2 on Pypi

Just an update on when will the next release roll-out on Pypi? I still have to import directly from git, the latest commit fixes my problem now.

Thank you!

Add other user object data

Hi,

would it be possible to add additional user object data?
I'm looking for users is_staff or is_superuser
Need to work with this data in a place where I'm not able to get to the User object model.
And this plugin was already able to provide me with the username.

Thanks,
Christian

Problem with custom users models

In my django project am not using the basic user table, I created custom user model,, when I used current user it gives me an error

townoftech_warehouse.Item.created_by: (fields.E301) Field defines a relation with the model 'auth.User', which has been swapped out.
	HINT: Update the relation to point at 'settings.AUTH_USER_MODEL'.

that is how I am using it in models.py

class Item(models.Model):
    item_category = models.ForeignKey(Category, on_delete="PROTECT")
    item_name = models.CharField(max_length=100, null=False)
    item_quantity = models.IntegerField(default=1)
    created_at = models.DateTimeField(auto_now_add=True, editable=False)
    created_by = CurrentUserField(settings.AUTH_USER_MODEL)

add possibility to save username as string instead of pk

For our project we would like to save the username as string instead of having a foreign key.
Would it be possible to add this as a feature?

Getting and setting the current user while testing

New to using this project, thanks for creating and maintaining it!

While creating tests for myself, I find myself wanting to set the current user. I've finally had success using the internal _set_current_user() method. It would be great if there were an external facing testing toolset to make this easier/more accessible. Happy to make a go at it, if there's interest.

Wondering why null=True?

For my purposes I'd rather have null=False and it errors out if the value is None. Wondering the thought process on enforcing null=True?

Wrong pinning of versions

It seems there's an issue with the pinning of version.

It's currently impossible to use django-currentuser 0.4.1 with Django 2.2.1.

ERROR: django-currentuser 0.4.1 has requirement Django<2.0,>=1.11.17, but you'll have django 2.1.8 which is incompatible.
ERROR: django-currentuser 0.4.1 has requirement Django<2.3,>=2.2.1; python_version > "3.4", but you'll have django 2.1.8 which is incompatible.

Step to reproduce:

pip install django
pip install django-currentuser

Django 3.2 compatibility

Hi! I use this with django 3.2 and it works for me, although setup.py says it requires Django<3.2
Are there known problems with 3.2 or can you loose this restriction in a new release?

Thanks!

Error and Warning on Django V3.2 on Custom User Model Migrations

According to github's REAEME.md

On Custom User Model

created_by = CurrentUserField()
updated_by = CurrentUserField(on_update=True)

it gives me this error

$ py manage.py makemigrations
SystemCheckError: System check identified some issues:

ERRORS:
authentication.User.created_by: (fields.E304) Reverse accessor for 'authentication.User.created_by' clashes with reverse accessor for 'authentication.User.updated_by'.
        HINT: Add or change a related_name argument to the definition for 'authentication.User.created_by' or 'authentication.User.updated_by'.
authentication.User.updated_by: (fields.E304) Reverse accessor for 'authentication.User.updated_by' clashes with reverse accessor for 'authentication.User.created_by'.
        HINT: Add or change a related_name argument to the definition for 'authentication.User.updated_by' or 'authentication.User.created_by'.

Then I Try to Solve like the following

created_by = CurrentUserField(related_name="+")
updated_by = CurrentUserField(on_update=True, related_name="+")

Then it gives me following warning

$ py manage.py makemigrations
E:\django\venv\lib\site-packages\django_currentuser\db\models\fields.py:57: UserWarning: You passed 
an argument to CurrentUserField that will be ignored. Avoid args and following kwargs: default, null, to.       
  warnings.warn(self.warning)
Migrations for 'authentication':
  authentication\migrations\0001_initial.py
    - Create model User
    - Create model Permission
    - Create model Role
    - Add field role to user
    - Add field updated_by to user

Please help me to fix this warning and errors

Support for django 4.x

Add support for django 4.x - For now, the project is tagged to support django 3.2.x

make initial release after the repo's transfer

Maintainer wanted

On July 28, a new message was added to the readme file:

WARNING:
This project is currently frozen and will not longer be maintained. If there is someone interested in continuing to maintain this project please contact: [email protected] .

Does anyone feel called to do this?

IntegrityError when running django tests

In my tests, I create an object that has an CurrentUserField. Up until recently everything worked, but now it fails with an SQLdb.IntegrityError after upgrading to python 3.9, django 3.2 and django-currentuser 0.5.3.

I was able to resolve this by explicitly overriding the user in the setUp() method of my test class as follows: _set_current_user(my_user). Is that the recommended approach? If so, we should document it somewhere.

Stacktrace:

ERROR: test_donation_bill (app.fairgeben.tests.test_donation.DonationInternalsTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/mysql/base.py", line 73, in execute
    return self.cursor.execute(query, args)
  File "/opt/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 206, in execute
    res = self._query(query)
  File "/opt/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 312, in _query
    db.query(q)
  File "/opt/venv/lib/python3.9/site-packages/MySQLdb/connections.py", line 224, in query
    _mysql.connection.query(self, query)
MySQLdb._exceptions.IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (`test_edonapi`.`fairgeben_donationcomment`, CONSTRAINT `fairgeben_donationco_created_by_id_5e9223c0_fk_users_use` FOREIGN KEY (`created_by_id`) REFERENCES `users_user` (`id`))')

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/app/fairgeben/tests/test_donation.py", line 290, in test_donation_bill
    self.assertRaises(
  File "/usr/local/lib/python3.9/unittest/case.py", line 733, in assertRaises
    return context.handle('assertRaises', args, kwargs)
  File "/usr/local/lib/python3.9/unittest/case.py", line 201, in handle
    callable_obj(*args, **kwargs)
  File "/usr/src/app/fairgeben/models.py", line 631, in add_to_accounting
    self._log_invalid_status_change(
  File "/usr/src/app/fairgeben/models.py", line 553, in _log_invalid_status_change
    DonationComment.objects.create(
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/query.py", line 453, in create
    obj.save(force_insert=True, using=self.db)
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/base.py", line 726, in save
    self.save_base(using=using, force_insert=force_insert,
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/base.py", line 763, in save_base
    updated = self._save_table(
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/base.py", line 868, in _save_table
    results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/base.py", line 906, in _do_insert
    return manager._insert(
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/query.py", line 1270, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
  File "/opt/venv/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql
    cursor.execute(sql, params)
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/opt/venv/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/opt/venv/lib/python3.9/site-packages/django/db/backends/mysql/base.py", line 73, in execute
    return self.cursor.execute(query, args)
  File "/opt/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 206, in execute
    res = self._query(query)
  File "/opt/venv/lib/python3.9/site-packages/MySQLdb/cursors.py", line 312, in _query
    db.query(q)
  File "/opt/venv/lib/python3.9/site-packages/MySQLdb/connections.py", line 224, in query
    _mysql.connection.query(self, query)
django.db.utils.IntegrityError: (1452, 'Cannot add or update a child row: a foreign key constraint fails (`test_edonapi`.`fairgeben_donationcomment`, CONSTRAINT `fairgeben_donationco_created_by_id_5e9223c0_fk_users_use` FOREIGN KEY (`created_by_id`) REFERENCES `users_user` (`id`))')

Key (modified_by_id)=(1) is not present in table "account_customuser" when running unit test

Error getting user in settings.py

I am trying to get the current user in settings.py but i am getting None.

Adding Instance through admin panel dosent fill user field of model that inherits from abstract model

I have an abstract model

class BaseModel(models.Model):
    date_added = models.DateTimeField(auto_now_add=True)
    date_modified = models.DateTimeField(auto_now=True)
    added_by = CurrentUserField(blank=True, null=True, on_delete=models.SET_NULL, related_name='added_by')
    modified_by = CurrentUserField(blank=True, null=True, on_delete=models.SET_NULL, related_name='modified_by')

    class Meta:
        abstract = True

and

class Company(BaseModel):
    name = models.CharField(max_length=400)
    nip = models.CharField(max_length=13, unique=True)
    description = models.TextField()
    year_established = models.CharField(max_length=4, blank=True, null=True)
    www = models.URLField(blank=True, null=True)
    logo = models.FileField(blank=True, null=True)
    sectors = models.ManyToManyField(Sector, blank=True, null=True)

    def __str__(self):
        return f"{self.name}"

After adding Company through admin panel the added_by and modified_by field are blank.

Django 5.0 support

tearDown problems in unit tests?

I have the following model:

class Business(models.Model):
    ... 
    created_on = models.DateTimeField(auto_now_add=True, editable=False)
    created_by = CurrentUserField(null=True, blank=True, editable=False,       # Attention 4
                                  on_delete=models.SET_NULL)

And I am testing this in the following test case:

class Base(TestCase):
    def setUp(self):
        self.padmin = User.objects.create_user('padmin')
        for u in (self.padmin,):
            u.set_password('password')
            u.save()

        self.business = Business.objects.create(name='name', address='address',
                                                phone_number='123-456-7890')
        self.business2 = Business.objects.create(name='name2', address='address',
                                                 phone_number='123-456-7891')

    def STEP_create_instance(self):
        self.client.login(username='padmin', password='password')
        url = '/'
        self.client.post(url, {})    # Attention: 1


class SafesiteProductionFlowIntegrationTest(Base):

    def test_one(self):
        self.STEP_create_instance()    # Attention: 2

    def test_two(self):
        self.STEP_create_instance()    # Attention: 3 

When I run this test, I am getting the following error:

System check identified no issues (0 silenced).
..E
======================================================================
ERROR: test_before_split2 (instances.tests.test_viewflow.SafesiteProductionFlowIntegrationTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/backends/utils.py", line 83, in _execute
    return self.cursor.execute(sql)
psycopg2.IntegrityError: insert or update on table "businesses_business" violates foreign key constraint "businesses_business_created_by_id_25175862_fk_auth_user_id"
DETAIL:  Key (created_by_id)=(1) is not present in table "auth_user".


The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/test/testcases.py", line 209, in __call__
    self._post_teardown()
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/test/testcases.py", line 893, in _post_teardown
    self._fixture_teardown()
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/test/testcases.py", line 1041, in _fixture_teardown
    connections[db_name].check_constraints()
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/backends/postgresql/base.py", line 235, in check_constraints
    self.cursor().execute('SET CONSTRAINTS ALL IMMEDIATE')
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/backends/utils.py", line 68, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/Users/vng/.virtualenvs/prometheus/lib/python3.6/site-packages/django/db/backends/utils.py", line 83, in _execute
    return self.cursor.execute(sql)
django.db.utils.IntegrityError: insert or update on table "businesses_business" violates foreign key constraint "businesses_business_created_by_id_25175862_fk_auth_user_id"
DETAIL:  Key (created_by_id)=(1) is not present in table "auth_user".


----------------------------------------------------------------------
Ran 2 tests in 0.438s

FAILED (errors=1)

Commenting out the following removes the error:

• Removing the CurrentUserField in Attention: 4
• Removing the client post in Attention: 1
• Removing either of the test (Attention 2 and Attention 3) methods making this test test a single method

It seems like CurrentUserField is causing some issues during tearDown.

Any ideas?

Kwarg 'to' can be Model class instance (is not always a string)

https://github.com/PaesslerAG/django-currentuser/blob/f63850d711ba88c9a9ee2128642dbaee8165a081/django_currentuser/db/models/fields.py#L25

Support for Django 2.0

Django 2.0 has been released but this package currently requires 'Django>=1.8,<1.12' as dependency.

Support for Django 2.2

Talking about the support for Django 2.2, is there anything related on the roadmapping?

Can we have an `updated_by = CurrentUserField(on_update=True)` too?

Can we have an updated_by = CurrentUserField(on_update=True) similar to auto_now=True?

Django 2.1

Django 2.1.4 has been released but this package currently requires 'Django<2.1,>=1.11' as dependency. Seems compatible though, just mentioning, tx.

Warning running `makemigrations` after updating to Django 3.1 and django-currentuser 0.5.1

Environment:

• Windows 10 (WSL 2 Debian)
• Python 3.8
• pipenv
• Django 3.1
• django-currentuser 0.5.1

Problem:

When I run python manage.py makemigrations I get the following warning. This warning is new after updating to the latest version of Django and django-currentuser. If I revert Django to 3.0.X the warning will go away.

/home/admin/.local/share/virtualenvs/Project-HFzz1tdt/lib/python3.8/site-packages/django_currentuser/db/models/fields.py:57: UserWarning: You passed an argument to CurrentUserField that will be ignored. Avoid args and following kwargs: default, null, to.
  warnings.warn(self.warning)

I have one reference to CurrentUserField in my project:

from django.db import models
from django_currentuser.db.models import CurrentUserField


class UserTrackingModel(models.Model):
    created_by = CurrentUserField()

    class Meta:
        abstract = True

I use UserTrackingModel as a base class for some of my models, like so:

from camp.db_models import UserTrackingModel

class Foo(TimeStampedModel, UserTrackingModel):
    name = models.CharField(default="", max_length=200, unique=True)
    thing = models.ForeignKey(Thing, on_delete=models.PROTECT, null=False)

Desired Outcome

I would like to be able to generate migrations without getting a warning that could potentially turn into a bigger problem down the road.

don't enforce supported versions in setup.py?

inspired by #27, #30, #31

It could be better NOT to specify the python and Django versions, just as a super low bar - i.e.: python 2.7 and Django 1.11, and simply list in the README (tox) which versions are supported

• Each Django ensures it can only be installed with the right python version AFAIK, so the django version-python version match is taken care of
• we could end up with users installing the app on unsupported Django versions (e.g.: 2.0), but then if they come to report a bug, we can just remind them it is not supported
• we don't have to test against unsupported versions in tox/travis

Would simplify life quite a bit as setuptools is never trivial :)

Django v. 3.0 compatibility

I tested it with version 0.4.2 and it seems to work fine with django3.0 after editing parameters in setup.py.

on_delete should be a required parameter

IMO the CurrentUserField should not have on_delete=CASCADE as a default parameter. Instead it should align with Django (3.2) ForeignKey field implementation, where the parameter for on_delete is required.

The current behaviour might lead to unwanted deletion if the user is deleted.

Thank you for considering my request.

v0.3 in pypi

When will v0.3 be published to pypi?

Avoid closure around request scope

Currently the order in which this middleware is inserted in respect to AuthenticationMiddleware
and SessionMiddleware does not matter as we use a closure that returns the request-scope only on-demand.

This closure can fail in certain setups (see #1 (comment)) and seems avoidable. Right now nothing speaks against requiring a fixed order where ThreadLocalUserMiddleware is only allowed after the other two.

See: https://github.com/PaesslerAG/django-currentuser/blob/mb-prepare-package/django_currentuser/middleware.py#L29

Error on migrations - CurrentUserField argument ignored

Getting this error on migration:

UserWarning: You passed an argument to CurrentUserField that will be ignored. Avoid args and following kwargs: default, null, to.
warnings.warn(self.warning)

Should we be using asgiref.local.Local if available for import?

With django now supporting async, should we be trying to import asgiref.local.Local if available, which is a drop-in async replacement for threading.local?

Perhaps replacing:

from threading import local

With:

try:
    from asgiref.local import Local as local
except ImportError:
    from threading import local

Would be happy to make a PR for this, but not sure how to approach the situation where asgiref package is available vs when it is not.

Conflicting dependencies with Django 4.0

ERROR: Cannot install -r requirements.txt, Django==4.0 and django-currentuser==0.5.3 because these package versions have conflicting dependencies.

The conflict is caused by:
    django-currentuser 0.5.3 depends on Django<3.3 and >=1.11.17; python_version >= "2.7"

Is this just a matter of adjusting the dependency requirement or are there any changes needed in the package?

Not able to get current logged in user id in my custome middleware

I am trying to get the current loggedin user in middleware[Database router middleware] but unable to get.

it is always gives me like below -
<function get_current_authenticated_user at 0x7fcb67062280>

please help me to get the loggedin user in my database router so i can manage all the databases from single middleware.

Django >1.11 support

Will Django 1.11.1 and 2.0.1 be supported by the pip package any time soon?