That macro is confusing, I admit. It actually enables the deprecated functions!
On Wed, Jun 26, 2013 at 9:54 AM, Jeremy Lainé <jeremy.la...@m4x.org> wrote: > Hi Pete, > > I'll upload the new version, but I'm not sure I understand why the > Qt5-specific patch is required. > > How does disabling deprecated functions help the build? > > Jeremy > > Le Jun 26, 2013 à 10:39 AM, Pete Woods a écrit : > > > Package: qdjango > > Severity: wishlist > > Tags: patch > > > > Dear Maintainer, > > > > I have packaged the new release of QDjango with the following bugfixes: > > * Fix and test "unique" field option. > > * Add a "unique_together" model option. > > * Don't crash if QDjango::database() is called before > QDjango::setDatabase(). > > * Make index names coincide with those used by django. > > * Register models without instantiating them. > > * Improve foreign keys: > > - Do not take object ownership in QDjangoMetaModel::setForeignKey(). > > - Fix QDjangoQuerySet::selectRelated() with NULL foreign keys. > > > > Patch included to build against latest Qt version. > > > > Original source tarball came without modification from: > > https://qdjango.googlecode.com/files/qdjango-0.3.0.tar.gz > > > > > > > > -- System Information: > > Debian Release: wheezy/sid > > APT prefers saucy-updates > > APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, > 'saucy'), (100, 'saucy-backports') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 3.9.0-6-generic (SMP w/4 CPU cores) > > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > <qdjango_0.3.0-1.debian.tar.gz><qdjango_0.3.0-1.dsc> > >
