Removed some compatibility bits for Python 3.2.

[timgraham]

No description provided.

[charettes]

This got me wondering if we're planing to set up something in order to make sure we don't introduce u string literals now that we drop Python3.2 support. They can be easy to miss while reviewing a patch and a failure on Python3.2 was a great way of spotting them.

[timgraham]

That seems like something that could be implemented as part of flake8. I haven't looked to see if it might exist.

[berkerpeksag]

Here's a couple of candidates for the PR:

• https://github.com/django/django/blob/master/django/core/mail/message.py#L107
• https://github.com/django/django/blob/master/docs/faq/install.txt#L19
• https://github.com/django/django/blob/master/docs/intro/install.txt#L13
• https://github.com/django/django/blob/master/docs/topics/install.txt#L11 (there's a typo in that line: 3.3 should be 3.3+)

[claudep]

We might question the support of Python < 2.7.3. I've read that Mac OS X Lion ships 2.7.1. Would this be a blocker?

[timgraham]

I don't feel strongly either way in this case. If there were a maintenance overhead here I'd definitely be in favor of enforcing our "we only support the latest minor release" more aggressively.

[claudep]

Let's keep that, you're right that this doesn't cost us much.