Hi,

Thanks for this PR. I think django-1.11 should still be supported since:

• django-2 drops python2 support as you mentioned (which is still the default python interpreter in nixpkgs)
• django-1.11 is a LTS release that will maintained longer than django-2.0

We could be just fine maintaining only 2 versions of django: latest and LTS.

If the django attribute points to the 2.0 branch, I’d like to have a django_lts that could be used like

pkgs.python3.override {
      packageOverrides = self: super: {
          django = self.django_lts;
      };
}

The other approach would be to have the django attrubute point to 1.11 branch and a new django_latest attribute.

I am fine with both approaches.

@lsix can there not be more than one lts at any time?

Yes, there can be multiplu LTS at any time (to give time to migrate from one LTS to the other):

however, I am not sure we want to support multiple LTS release at once in nixpkgs. Only one that will be maintained for the lifetime of a nixos release, and if many are available I would say only the most recent.

Anyway, both releases will have an attribute named after its version (django_1_11 and django_2_0), having a django_lts attribute is mainly used as an alias and to clearly state that a version is not an outdated one that should be dropped but a legitimate maintained release in nixpkgs.