Log message:
Judging from the documentation, this prefers py-sqlite3 nowadays,
which has the advantage of being available for python-3.x.
(default-off option, so no PKGREVISION++)

Log message:
Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE=  33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE=  33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.

Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.

Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.

Whitespace cleanups and other nits corrected, where necessary.

Log message:
Use versioned_dependencies.mk for flup.

Log message:
Changes 1.6.1:
Bug fixes
Fixed BCryptSHA256PasswordHasher with py-bcrypt and Python 3.
Fixed a regression that prevented a ForeignKey with a hidden reverse manager \ 
(related_name ending with ‘+’) from being used as a lookup for \ 
prefetch_related.
Fixed Queryset.datetimes raising AttributeError in some situations.
Fixed ModelBackend raising UnboundLocalError if get_user_model() raised an error.
Fixed a regression that prevented editable GenericRelation subclasses from \ 
working in ModelForms.
Added missing to_python method for ModelMultipleChoiceField which is required in \ 
Django 1.6 to properly detect changes from initial values.
Fixed django.contrib.humanize translations where the unicode sequence for the \ 
non-breaking space was returned verbatim.
Fixed loaddata error when fixture file name contained any dots not related to \ 
file extensions or when fixture path was relative but located in a subdirectory.
Fixed display of inline instances in formsets when parent has 0 for primary key.
Fixed a regression where custom querysets for foreign keys were overwritten if \ 
ModelAdmin had ordering set.
Removed mention of a feature in the --locale/-l option of the makemessages and \ 
compilemessages commands that never worked as promised: Support of multiple \ 
locale names separated by commas. It’s still possible to specify multiple \ 
locales in one run by using the option multiple times.
Fixed a regression that unnecessarily triggered settings configuration when \ 
importing get_wsgi_application.
Fixed test client logout() method when using the cookie-based session backend.
Fixed a crash when a GeometryField uses a non-geometric widget.
Fixed password hash upgrade when changing the iteration count.
Fixed a bug in the debug view when the URLconf only contains one element.
Re-added missing search result count and reset link in changelist admin view.
The current language is no longer saved to the session by LocaleMiddleware on \ 
every response, but rather only after a logout.
Fixed a crash when executing runserver on non-English systems and when the \ 
formatted date in its output contained non-ASCII characters.
Fixed a crash in the debug view after an exception occurred on Python ≥ 3.3.
Fixed a crash in ImageField on some platforms (Homebrew and RHEL6 reported).
Fixed a regression when using generic relations in ModelAdmin.list_filter.

Log message:
Changes 1.6:
Simplified default project and app templates
Improved transaction management
Persistent database connections
Discovery of tests in any test module
Time zone aware aggregation
Support for savepoints in SQLite
BinaryField model field
GeoDjango form widgets
check management command added for verifying compatibility
Model.save() algorithm changed
Minor features

Log message:
Changes 1.5.5:
Django 1.5.5 fixes a couple security-related bugs and several other bugs in the \ 
1.5 series.

Readdressed denial-of-service via password hashers
Django 1.5.4 imposes a 4096-byte limit on passwords in order to mitigate a \ 
denial-of-service attack through submission of bogus but extremely large \ 
passwords. In Django 1.5.5, we’ve reverted this change and instead improved \ 
the speed of our PBKDF2 algorithm by not rehashing the key on every iteration.

Properly rotate CSRF token on login
This behaviour introduced as a security hardening measure in Django 1.5.2 did \ 
not work properly and is now fixed.

Bugfixes
Fixed a data corruption bug with datetime_safe.datetime.combine.
Fixed a Python 3 incompatability in django.utils.text.unescape_entities().
Fixed a couple data corruption issues with QuerySet edge cases under Oracle and \ 
MySQL.
Fixed crashes when using combinations of annotate(), select_related(), and only()

Log message:
Changes 1.5.4:
These releases address a denial-of-service attack against Django's \ 
authentication framework. All users of Django are encouraged to upgrade \ 
immediately.

Log message:
Changes 1.5.3:
These releases address a directory-traversal vulnerability in one of Django's \ 
built-in template tags. While this issue requires some fairly specific factors \ 
to be exploitable, we encourage all users of Django to upgrade promptly.

Log message:
Changes 1.5.2:
These releases address two cross-site scripting (XSS) vulnerabilities: one in a \ 
widget used by Django's admin interface, and one in a utility function used to \ 
validate redirects often used after login or logout.

While these issues are of limited impact and may not effect all Django users, we \ 
encourage all users to upgrade as soon as possible.

Log message:
Changes 1.5.1:
The biggest fix is for a memory leak introduced in Django 1.5. Under certain \ 
circumstances, repeated iteration over querysets could leak memory - sometimes \ 
quite a bit of it. If you'd like more information, the details are in our ticket \ 
tracker (and in a related issue in Python itself).

If you've noticed memory problems under Django 1.5, upgrading to 1.5.1 should \ 
fix those issues.

Django 1.5.1 also includes a couple smaller fixes:
* Module-level warnings emitted during tests are no longer silently hidden.
* Prevented filtering on password hashes in the user admin.