Update to Django 1.11

[jayfk]

I've told the bot to stay on 1.10.x for now (f62e05b) and merged the latest security release.

I believe @luzfcb was working on a release checklist. Let's put this here.

[luzfcb]

Checklist:

• Check if all dependencies officialy work with Django 1.11( if not, wait).

  Dependencies that are Django version-dependent ( Check off each of the below when it officially works on 1.11. ):

  If you want cookiecutter-django to be updated faster, please help the below projects in implementing compatibility with Django 1.11

  • django-environ
  • whitenoise
  • django-braces
  • django-crispy-forms
  • django-model-utils
  • django-allauth
  • django-autoslug
  • raven-python
  • django-redis
  • django-extensions
  • django-test-plus
  • factory_boy
  • django-debug-toolbar
  • pytest-django
  • django-storages-redux (deprecated) - Should be replaced by https://github.com/jschneier/django-storages - Done in Update django-storages and Boto3 fixes #998 & #1192 #1269
  • django-anymail
  • opbeat

• Check if dependencies require changes on django settings files.

• Add Python 3.6 to test suite tox.ini, .travis.yml

• Change the generated project to use Python 3.6

• Check that the tests pass on Django 1.11

• Check that the tests pass on Django 1.11 with zero deprecation warnings messages: https://docs.djangoproject.com/en/1.11/howto/upgrade-version/#resolving-deprecation-warnings

• Before update to Django 1.11, create a git tag to current version of cookiecuter-django

• Update to Django 1.11 and update other dependencies and:

  • Check if all possible generated project layout still works on deploy on Heroku.
  • Check if all possible generated project layout still works on deploy on Docker.
  • Check PyCharm 2017.1 compatibility, with and widout docker
  • Check PyCharm 2017.2 compatibility, with and widout docker
  • Update the README.rst
  • Update version on setup.py
  • Update changelog.
  • after update, create a git tag

[joke2k]

django-environ 0.4.2 confirm support for django 1.11 LTS
https://github.com/joke2k/django-environ#changelog

[dgorobets]

django-anymail support for django 1.11 https://github.com/anymail/django-anymail/releases/tag/v0.9

[dgorobets]

django-extensions support for django 1.11 https://github.com/django-extensions/django-extensions/blob/master/CHANGELOG.md#178

[dgorobets]

django-model-utils support for django 1.11 https://github.com/jazzband/django-model-utils/blob/master/CHANGES.rst#300-20170413

[pydanny]

django-debug-toolbar works for Django 1.11.

[ghost]

whitenoise works for Django 1.11 https://travis-ci.org/evansd/whitenoise

[ghost]

django-redis works for Django 1.11 https://travis-ci.org/niwinz/django-redis

[yunti]

django-crispy-froms. Looks like there tests are running against django 1.11 django-crispy-forms/django-crispy-forms@d3bf1f2

[yunti]

django all_auth Tests passing with support for Django 1.11
pennersr/django-allauth@fa07b32

[yunti]

django-storages tests passing for support with Django 1.11
jschneier/django-storages#295

[highpost]

pytest-django now supports 1.11
https://github.com/pytest-dev/pytest-django

[luzfcb]

migrate from django-storages-redux to django-storages done in #1269

[brylie]

opbeat likely supports Django 1.11. Is there a particular issue with opbeat, or reason to suspect that it doesn't support 1.11?

[brylie]

opbeat indicates it should work with Django 1.11:

We run our test suite with Django 1.11, and have lots of customers running the Opbeat module on Django 1.11

opbeat/opbeat_python#183 (comment)

[reggieriser]

The django-factory-boy package referenced above is different from the factory-boy used in cookiecutter-django -- factory-boy already supports Django 1.11: FactoryBoy/factory_boy#357

[luzfcb]

@reggieriser my mistake. I updated to the correct link.

[reggieriser]

If my PR is accepted, we can remove django-braces from the 1.11-compatibility list:
#1312

[brylie]

@kennethlove commented in the django-braces issue:

Yeah, django-braces should be 100% compatible with all future Django releases unless they restructure how CBVs are constructed.

[jayfk]

Thanks

[webyneter]

Maybe we could drop django-autoslug in favor of django-extensions' AutoSlugField?

[jayfk]

I think @pydanny wants to avoid running django-extensions on production. There's an issue about that, but I can't find it right now :/

[highpost]

I believe that factory_boy now supports Django 1.11
https://github.com/FactoryBoy/factory_boy

[pydanny]

The problem with django-extensions is that it includes security issues like providing a fancy shell that arguably shouldn't be in production. And who knows what other magic has been added to that crazy mix of packages.

That said, if django-autoslug is a blocker, let's not worry about it. If a malignant or foolish user can activate a fancy django-extensions shell in production, they've gotten in and there's nothing stopping them from unleashing destruction in their wake anyway.

[brylie]

Got a response on django-autoslug re: 1.11 support:

The fixes for 1.10 on master (see justinmayer/django-autoslug#6) are working just fine for me on 1.11, however the maintainer has not released a new version since the changes were merged last October. :(

@eykd

[reggieriser]

Django 2.0 alpha 1 has just been released (final coming in about two months). I noticed this from the pre-release notes:

Following the release of Django 2.0, we suggest that third-party app authors drop support for all versions of Django prior to 1.11.

Is anybody actively working on the 1.11 upgrade? I'll be glad to help or research.

[luzfcb]

@reggieriser feel free to do a pull-request to update to 1.11 (and make update to 2.0 more easy). Any help is welcome.

[yujinyuz]

When will django 1.11 cookiecutter get released? Thanks :)

[pydanny]

@yujinyuz you can run Cookiecutter Django and bump the Django version to 1.11 and it should work except in a few resolvable edge cases.

[jeffcjohnson]

I sent an email to the author of django-autoslug on October 14th offering to help with getting a new release out. So far no response.

[pydanny]

At this point I think we should remove that project as a dependency, either replacing with something else or discarding it entirely. Thoughts?

[webyneter]

A quick GitHub search reveals django-uuslug, for instance.

[webyneter]

It seems to be way more simpler when contrasted with django-autoslug, though.

[pydanny]

Considering that we've waited this long, I think simpler choice for slug going forward is the better option.

[webyneter]

Hopefully, I will have time to take a look at it tomorrow to see how it'd be best to migrate.

[Zerokami]

Two Scoops of Django seems to be recommending awesome-slugify

Wait : There is an article by Pydanny mentioned on Two Scoops and the maintainer seems to be pydanny . What?

http://pydanny.com/awesome-slugify-human-readable-url-slugs-from-any-string.html

Edit: So, it's a model field. Cool!

A lot of people from cookiecutter seem to have posted issues on the django-autoslug project including one 12 hours ago.

[Tafkas]

With the release of Django 2.0 is this still valid? Should the aim still be to support Django 1.11 for it's LTS or should this move towards Django 2.0?

[Zerokami]

@Tafkas Ideally you'd have support for a Django version until it's support in Django ends.

For Django 1.11 it's atleast Until April 2020

[pydanny]

I plan to look at this in the next day or so.

[odeckmyn]

How can I go with this cookiecutter and Django 2 please ?

[pydanny]

Yes, just run it and then do pip install -U Django. Works fine for me.

That we haven't finished this ticket is because were volunteers.

[browniebroke]

For what it's worth, I started a new project using this cookiecutter today, upgraded the resulting code to Django 1.11 and I deployed it to Heroku without any problems.

• Homepage works
• Static files are collected OK
• Created a super-user
• Logged into the admin

As far as I'm concerned, this issue (1.11) is resolved. Hopefully, some other folks could test other platforms and it would be a matter of sending a PR to change the requirements and a couple of places in the docs?

[brylie]

Woohoo! Now for 2.0 support (#1416) hehe :-)

[pydanny]

We just bumped it to 1.11 in 5395687.

[technolingo]

So django-autoslug was replaced with awesome-slugify? Could someone tell me how to update my existing project to Django 1.11? Thank you!

[pydanny]

Sorry, @Evilplanet, but upgrades to existing projects is outside the scope of Cookiecutter Django. You should consider opening a question on Stack Overflow.

[technolingo]

I see. Thank you!

[rossparks]

Doing the first app (http://cookiecutter-django.readthedocs.io/en/latest/my-favorite-cookie.html) with cookie cutter and getting errors.

I have the correct version of django installed -

conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: fe_sendauth: no password supplied

[pydanny]

@rossparks I'm sorry you are having difficulties, but your question is completely, 100% unrelated to migrating this project to Django 1.11. Furthermore, this issue is closed.

Don't hijack issues, especially closed ones.

If you have a problem, please open a new issue.