Cleanups for when we drop Python 2 compatibility

[Tim Graham]

This is a tracking ticket of things that we can remove when we drop Python 2 compatibility in Django 2.0. Please edit the description of the ticket as you come across new items.

• django.core.mail.message.make_msgid() #23905
• django.dispatch.weakref_backports
• django.http.cookie workarounds
• django.utils.2to3_fixes
• django.utils.decorators.ContextDecorator
• django.utils.encoding
  • @python_2_unicode_compatible
  • force/smart _unicode
  • either force/smart _text or force/smart _str
• django.utils.html_parser.use_workaround
• django.utils.http functions like urlquote_plus -- I think the versions of these functions on Python 3 don't have the unicode characters bug we are working around.
• django.utils.lru_cache
• django.utils.six
• from __future__ import unicode_literals
• str() stuff for environment variables, e.g. 0bfb53866199f366ed140d49938fd185e5898156
• Inheriting from object in django.core.servers.basehttp (and perhaps other places) ala 4ee06ec3fc8e94d164afbd2f9c880c60c658a9ac
• git grep 'long int' (mostly docs)
• django.utils._os [npath,upath]
• In tests: contextlib.closing(self.urlopen (contextlib.closing no longer needed)
• Support for pysqlite (doesn't support Python 3)

[Wojtek Ruszczewski]

Various nonlocal workarounds (​example).

[Anssi Kääriäinen]

I believe we can get rid of the Field.creation_counter hack. In Python 3 it is possible to store the attrs in a sorted dictionary. See ​http://stackoverflow.com/questions/4459531/how-to-read-class-attributes-in-the-same-order-as-declared.

[Curtis Maloney]

In far too many tests we rely on the fact six aliases builtins [like input] instead of using mock.

I submitted a patch recently to clean up a couple of these I found, but I am finding more.