From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id B3C741381F3 for ; Mon, 20 May 2013 09:05:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 57CD6E08F1; Mon, 20 May 2013 09:05:33 +0000 (UTC) Received: from icp-osb-irony-out3.external.iinet.net.au (icp-osb-irony-out3.external.iinet.net.au [203.59.1.219]) by pigeon.gentoo.org (Postfix) with ESMTP id 4A56BE08F1 for ; Mon, 20 May 2013 09:05:31 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As0FAC/mmVE6B2i0/2dsb2JhbABagwgwglK/aRZ0gmBnFDQQP4geulSSfAOJHYUFiRWGQop/gxwv X-IronPort-AV: E=Sophos;i="4.87,706,1363104000"; d="scan'208";a="126373498" Received: from unknown (HELO archtester.homenetwork) ([58.7.104.180]) by icp-osb-irony-out3.iinet.net.au with ESMTP; 20 May 2013 17:05:30 +0800 Date: Mon, 20 May 2013 17:05:33 +0800 From: IAN DELANEY To: idella4@gentoo.org, gentoo-python@lists.gentoo.org Subject: [gentoo-python] recent trend of django-foo tests Message-ID: <20130520170533.462ab085@archtester.homenetwork> Organization: homenetwork X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 9e435de8-9cab-4e16-b551-6c6a3da180ac X-Archives-Hash: 3a3b863af334385d6ecef6335ce9877d Am generally reluctant to enter things here, however this issues appears apt. Recent versions of django-xxx packages' test suites have made a habit of falling over, which is no surprise in itself, but they have a new cause. They all expect to find a setting to SECRET_KEY which is set in djang.conf.global_settings. For while I thought "${PYTHON}" -c "from django.conf import \ global_settings;global_settings.SECRET_KEY='green'" ${test} did the trick but it seems that the ${test} after the import with -c " " is discarded somehow and never actually run with the attempt to set SECRET_KEY='green'. The output looks as if it was an effective run but it's not the case. How this came about, who knows. The backtrace tells it's expecting a hard coded entry in the installed global_settings.py. django has some other django specific mechanisms for running test suites and setting settings. Anyone know at least one? How about patching django itself to include the setting? (That one I expect goes down like a lead balloon.) kind regards Ian Delaney