Ensure we always coerce values to unicode in our __unicode__ method, and
remove some now unneeded verbosity and comments since the upstream bug
has been fixed.
Signed-off-by: Dan McGee <dan@archlinux.org>
Django 1.7 has built-in migrations support, so we no longer want these
around. All existing installs should be fully migrated at this point to
the latest schema.
Signed-off-by: Dan McGee <dan@archlinux.org>
This makes entering new releases a bit less cumbersome as we don't
really need to enter either the file size or the torrent infohash.
Signed-off-by: Dan McGee <dan@archlinux.org>
Most of these were suggested by PyCharm, and include everything from
little syntax issues and other bad smells to dead or bad code.
Signed-off-by: Dan McGee <dan@archlinux.org>
This was added in Django 1.5 and allows saving only a subset of a
model's fields. It makes sense in a few cases to utilize it.
Signed-off-by: Dan McGee <dan@archlinux.org>
This allows them to be overridden and changed in a central location,
like we do with the SVN URL, PXE boot URL, etc.
Signed-off-by: Dan McGee <dan@archlinux.org>
It should be unique anyway, but it is especially important now that we
are using it in URL patterns for lookup.
Signed-off-by: Dan McGee <dan@archlinux.org>
This allows uploading of the actual torrent file itself into the webapp
and then pulling the relevant pieces of information out of it.
Signed-off-by: Dan McGee <dan@archlinux.org>
Add a file_size field which we will use in the RSS feed, and also add a
field for future storage of the torrent data itself.
Signed-off-by: Dan McGee <dan@archlinux.org>
This should prevent the need for monthly template updates from Pierre
and Thomas; best to just let them enter the data themselves and have it
show up on the website.
Signed-off-by: Dan McGee <dan@archlinux.org>
We were already using this on package flag requests, and we can support
IPv6 addresses here as well with minimal hassle.
Signed-off-by: Dan McGee <dan@archlinux.org>
Now that Django actually provides a concise way to use a RequestContext
object without instantiating it, we can use that rather than the old
function-based generic view that worked well to do the same.
Additionally, these function-based generic views will be gone in Django
1.5, so might as well make the move now.
Signed-off-by: Dan McGee <dan@archlinux.org>
This was around from the time when we handled timezones sanely and
Django did not; now that we are on 1.4 we no longer need our own code to
handle this.
Signed-off-by: Dan McGee <dan@archlinux.org>
This table is getting very long as we have upwards of 210 ISOs in the
production database. However, it doesn't make much sense to list ISOs
that no longer exist and were never tested, so omit these from the
results page if we know this to be the case.
Signed-off-by: Dan McGee <dan@archlinux.org>
This is most of the transition to Django 1.4 `USE_TZ = True`. We need to
ensure we don't mix aware and non-aware datetime objects when dealing
with datetimes in the code. Add a utc_now() helper method that we can
use most places, and ensure there is always a timezone attached when
necessary.
Signed-off-by: Dan McGee <dan@archlinux.org>
Until Django 1.3, the functions include(), patterns() and url() plus
handler404, handler500 were located in a django.conf.urls.defaults
module.
In Django 1.4, they live in django.conf.urls.
Signed-off-by: Dan McGee <dan@archlinux.org>
Use some annotation stuff and trickeration to reduce the number of
queries we need on the results overview page by quite a bit.
Signed-off-by: Dan McGee <dan@archlinux.org>
ISO Overview shows a simple list of all the ISOs that are available
and how many times they've been tested successfully or have failed.
Signed-off-by: Tom Willemsen <ryuslash@gmail.com>
Signed-off-by: Dan McGee <dan@archlinux.org>
