Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.etla.org!aioe.org!bofh.it!news.nic.it!robomod From: Brian May Newsgroups: linux.debian.maint.python Subject: Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import Date: Wed, 25 Apr 2018 03:20:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Apr 25 01:17:22 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .debian. - helo: .mirror.linuxpenguins. - helo-domain: .linuxpenguins.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 Organization: Debian MIME-Version: 1.0 Content-Type: text/plain X-Mailing-List: archive/latest/15866 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/87tvs09jay.fsf@silverfish.pri Approved: robomod@news.nic.it Lines: 29 Sender: robomod@news.nic.it X-Original-Date: Wed, 25 Apr 2018 11:16:53 +1000 X-Original-Message-ID: <87tvs09jay.fsf@silverfish.pri> X-Original-References: <20180420200123.GX10848@alf.mars> <8736zpbftc.fsf@silverfish.pri> <20180421062318.GB30142@alf.mars> <44a224af-4d75-c22c-165f-6a5d7aed831f@debian.org> Xref: csiph.com linux.debian.maint.python:10465 Thomas Goirand writes: > Feel free to raise this on a Django upstream message. I very much agree > this isn't best. I believe there is (or at least was, and probably still is) general agreement that the Django settings mechanism is horrible for numerous reasons. IIRC this has been discussed at past PyCON AU conferences. Unfortunately, this has been labelled as a "hard problem". As in coming up with a replacement that the Django core developers can agree to is non-trivial (which also means dealing with existing applications in a sensible manner). e.g. do a google search for "django settings class" and you will see that there are a number of projects to get class based settings for Django. A feature I really wish Django supported out of the box. Unfortunately most of these projects (I might have missed something) appear to have been abandoned. Maybe this is an isssue that needs to be pushed at PyCon or PyConAU. If there isn't an existing upstream bug report already, somebody should definitely file one. Or add details as to how the problem affects testing, if not already given. I don't believe the bug report by itself will solve this problem, but I think it is a necessarily prerequisite for a solution. -- Brian May