From 5adceb6586afcac163b1abf9fb6f2d0f1b151b9a Mon Sep 17 00:00:00 2001 From: Dan McGee Date: Mon, 24 May 2010 10:57:17 -0500 Subject: Fix null field issues exposed by Django 1.1.2 Apparently Django 1.1.1 let null fields pass right through but this now causes reporead to blow up in 1.1.2. Fix the issue and get things working again by allowing nulls where it probably makes sense and including a migration to fix the issue, which for the real database will be a no-op. Signed-off-by: Dan McGee --- devel/management/commands/reporead.py | 5 ----- 1 file changed, 5 deletions(-) (limited to 'devel') diff --git a/devel/management/commands/reporead.py b/devel/management/commands/reporead.py index 777bc5dd..ee606846 100644 --- a/devel/management/commands/reporead.py +++ b/devel/management/commands/reporead.py @@ -95,11 +95,6 @@ class Pkg(object): selfdict['name'] = val['name'][0] selfdict['base'] = None del val['name'] - if 'desc' not in val: - logger.warning("Package %s has no description" % selfdict['name']) - val['desc'] = None - if 'url' not in val: - val['url'] = None if 'license' not in val: val['license'] = [] for x in val.keys(): -- cgit v1.2.3