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 p
On 04/21/2018 11:10 PM, Scott Kitterman wrote:
> I believe we could benefit from more documentation and perhaps tools to make
> it easier to integrate tests for Django modules.
>
> Scott K
I agree, and it would be nice to have it within within the
python-django-common package, so one could use i
On April 21, 2018 8:56:52 PM UTC, Thomas Goirand wrote:
>On 04/21/2018 08:23 AM, Helmut Grohne wrote:
...
>> After the dust has settled, I can follow up on d-devel with a summary
>> that suggests filtering this particular django exception.
>
>Again, instead you could setup a working Django envir
On 04/21/2018 08:23 AM, Helmut Grohne wrote:
> Control: severity 896234 normal
> Control: severity 896242 normal
> Control: severity 896272 normal
> Control: severity 896306 normal
> Control: severity 896307 normal
> Control: severity 896328 normal
> Control: severity 896378 normal
> Control: sever
Control: severity 896234 normal
Control: severity 896242 normal
Control: severity 896272 normal
Control: severity 896306 normal
Control: severity 896307 normal
Control: severity 896328 normal
Control: severity 896378 normal
Control: severity 896396 normal
Control: severity 896429 normal
On Sat, Ap
Helmut Grohne writes:
> django.core.exceptions.ImproperlyConfigured: Requested setting
> DEFAULT_INDEX_TABLESPACE, but settings are not configured. You must
> either define the environment variable DJANGO_SETTINGS_MODULE or call
> settings.configure() before accessing settings.
I believe this bu
6 matches
Mail list logo
