Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #10427 > unrolled thread
| Started by | Brian May <bam@debian.org> |
|---|---|
| First post | 2018-04-21 02:10 +0200 |
| Last post | 2018-04-25 03:20 +0200 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.maint.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#896429: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import Brian May <bam@debian.org> - 2018-04-21 02:10 +0200
Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import Thomas Goirand <zigo@debian.org> - 2018-04-21 23:00 +0200
Testing Django Packages, was: Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import Scott Kitterman <debian@kitterman.com> - 2018-04-21 23:20 +0200
Re: Testing Django Packages, was: Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import Thomas Goirand <zigo@debian.org> - 2018-04-22 12:20 +0200
Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import Brian May <bam@debian.org> - 2018-04-25 03:20 +0200
| From | Brian May <bam@debian.org> |
|---|---|
| Date | 2018-04-21 02:10 +0200 |
| Subject | Bug#896429: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import |
| Message-ID | <vGNWV-6hw-1@gated-at.bofh.it> |
Helmut Grohne <helmut@subdivi.de> 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 bug report, and several others you filled recently that contain this same text are false. Like it or not, it is just not possible to import Django libraries without providing a valid django settings file. This is not a sign that something is broken. -- Brian May <bam@debian.org>
[toc] | [next] | [standalone]
| From | Thomas Goirand <zigo@debian.org> |
|---|---|
| Date | 2018-04-21 23:00 +0200 |
| Subject | Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import |
| Message-ID | <vH7LY-2to-21@gated-at.bofh.it> |
| In reply to | #10427 |
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: severity 896396 normal > Control: severity 896429 normal > > I have lowered the severity of the relevant bugs (matching > "ImproperlyConfigured") to prevent issues with testing migration. Instead, please *CLOSE* those bugs unless you've done proper testing. > I wonder whether we can draw anything useful from these bugs before > closing them. Unless you try to setup a working Django env before doing the import, I'm afraid you can't draw anything. > So yeah, for django this may make sense, but this behaviour is still > unfortunate from a qa pov. Feel free to raise this on a Django upstream message. I very much agree this isn't best. > 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 environment and restart the tests. I'm not sure how hard that would be though. Cheers, Thomas Goirand (zigo)
[toc] | [prev] | [next] | [standalone]
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2018-04-21 23:20 +0200 |
| Subject | Testing Django Packages, was: Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import |
| Message-ID | <vH85j-2Ss-3@gated-at.bofh.it> |
| In reply to | #10431 |
On April 21, 2018 8:56:52 PM UTC, Thomas Goirand <zigo@debian.org> 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 environment and restart >the tests. I'm not sure how hard that would be though. I maintain several Django packages that have upstream tests. When I looked into running the test suite either during package build or as an autopackagetest, I concluded it was more trouble than I had patience for. I believe we could benefit from more documentation and perhaps tools to make it easier to integrate tests for Django modules. Scott K
[toc] | [prev] | [next] | [standalone]
| From | Thomas Goirand <zigo@debian.org> |
|---|---|
| Date | 2018-04-22 12:20 +0200 |
| Subject | Re: Testing Django Packages, was: Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import |
| Message-ID | <vHkg9-2Js-1@gated-at.bofh.it> |
| In reply to | #10432 |
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 it for tests. Cheers, Thomas Goirand (zigo)
[toc] | [prev] | [next] | [standalone]
| From | Brian May <bam@debian.org> |
|---|---|
| Date | 2018-04-25 03:20 +0200 |
| Subject | Re: [Python-modules-team] Bug#896429: python3-django-tables2: django_tables2 fails to import |
| Message-ID | <vIhgd-7lM-9@gated-at.bofh.it> |
| In reply to | #10431 |
Thomas Goirand <zigo@debian.org> 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 <bam@debian.org>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web