Hello, Several people have started porting their apps for Python 3, but they're running into trouble when they try to support both Django 1.4 and master. They end up with regrettable patterns such as:
try:
from django.utils.six import PY3
except ImportError:
PY3 = False
Authors of pluggable apps generally chose to support the current and the
previous version of Django. Thus their users can alternatively upgrade
Django and their apps, which makes upgrades less scary.
Now we have two alternatives:
1) tell them to roll their own compat or wait until they can target 1.5 +
1.6 — quite a downer,
2) add some forwards compatibility tools to 1.4.
We generally don't add features to minor releases, but there's a precedent
(csrf_noop), and the patch is as harmless as they come (see attachment).
What do you think?
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
python3-forwards-compat-for-django-14.diff
Description: Binary data
