Re: [Django] #28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster

[Django]

#28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to
ImportError of GDALRaster
-+-
 Reporter:  Tom Kazimiers|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  GIS, GDAL, Contrib,  | Triage Stage:
  Bug|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> Under some circumstances `django.contrib.gis.gdal.HAS_GDAL` is `False`.
> This can be due to not having GDAL installed in the first place or by
> overriding one's OS name (and thereby causing the test in
> `django.contrib.gis.gdal.__init__.py` to result in an exception which in
> turns causes `HAS_GDAL = False`).¹
>

> Now with `HAS_GDAL = False`, I can't start Django anymore (neither the
> shell or any other command), because I get the following error:
> {{{
> django.core.exceptions.ImproperlyConfigured: 'postgresql' isn't an
> available database backend.
> Try using 'django.db.backends.XXX', where XXX is one of:
> 'mysql', 'oracle', 'postgresql', 'sqlite3'
> Error was: No module named postgresql.base
> }}}
>
> Digging a bit deeper into this reveals this is actually an ImportError:
> `Error was: cannot import name GDALRaster`. Using other
> `django.contrib.gis` functionality should also work without GDAL (and did
> so in the past).
>
> The problem seems to be that in commit
> `bbfad84dd980a97174c3b061a3d1b5f1373c380d`
> ([https://github.com/django/django/commit/bbfad84dd980a97174c3b061a3d1b5f1373c380d
> #diff-9501b5a77c1985430f52d03aedb3e434R7 here]) a new import has been
> added to `django/contrib/gis/db/backends/postgis/operations.py`, which
> tries to import `GDALRaster`: `from django.contrib.gis.gdal import
> GDALRaster`. This of course fails with `HAS_GDAL = False`, because
> `GDALRaster` has never been defined when `HAS_GDAL` was set false due to
> an (expected) exception in `django/django/contrib/gis/gdal/libgdal.py`,
> which is imported before `from django.contrib.gis.gdal.raster.source
> import GDALRaster` in `django/django/contrib/gis/gdal/__init__.py`.
>
> So maybe the import in
> `django/contrib/gis/db/backends/postgis/operations.py` and the use of
> `GDALRaster` should be conditional and only run if `HAS_GDAL = True`. I
> can provide a patch if wanted.
>
> This is a problem in both Django 1.10 and 1.11.
>
> ¹ In my project I need to do the latter to disable GDAL support
> completely, because loading the library conflicts with `pgmagick` on
> Ubuntu and there is no other way to disable GDAL, but this shouldn't
> matter here. It would be nice though to have a way to force `HAS_GDAL =
> False`, because unlike said in
> `django/django/contrib/gis/gdal/__init__.py`, setting
> `GDAL_LIBRARY_PATH='/null/path'` doesn't work (the automatic OS checks
> override this).

New description:

 Under some circumstances `django.contrib.gis.gdal.HAS_GDAL` is `False`.
 This can be due to not having GDAL installed in the first place or by
 overriding one's OS name (and thereby causing the test in
 `django.contrib.gis.gdal.__init__.py` to result in an exception which in
 turns causes `HAS_GDAL = False`).¹


 Now with `HAS_GDAL = False`, I can't start Django anymore (neither the
 shell or any other command), because I get the following error:
 {{{
 django.core.exceptions.ImproperlyConfigured: 'postgresql' isn't an
 available database backend.
 Try using 'django.db.backends.XXX', where XXX is one of:
 'mysql', 'oracle', 'postgresql', 'sqlite3'
 Error was: No module named postgresql.base
 }}}

 Digging a bit deeper into this reveals this is actually an ImportError:
 `Error was: cannot import name GDALRaster`. Using other
 `django.contrib.gis` functionality should also work without GDAL (and did
 so in the past).

 The problem seems to be that in commit
 `bbfad84dd980a97174c3b061a3d1b5f1373c380d`
 
([https://github.com/django/django/commit/bbfad84dd980a97174c3b061a3d1b5f1373c380d
 #diff-9501b5a77c1985430f52d03aedb3e434R7 here]) a new import has been
 added to `django/contrib/gis/db/backends/postgis/operations.py`, which
 tries to import `GDALRaster`: `from django.contrib.gis.gdal import
 GDALRaster`. This of course fails with `HAS_GDAL = False`, because
 `GDALRaster` has never been defined when `HAS_GDAL` was set false due to
 an (expected) exception in `django/django/contrib/gis/gdal/libgdal.py`,
 which is imported before `from django.contrib.gis.gdal.raster.source
 import GDALRaster` in `django/django/contrib/gis/gdal/__init__.py`.

 So maybe the import 

[Django] #28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to ImportError of GDALRaster

[Django]

#28160: Can't start with django.contrib.gis.gdal.HAS_GDAL = False due to
ImportError of GDALRaster
-+-
   Reporter:  Tom|  Owner:  nobody
  Kazimiers  |
   Type:  Bug| Status:  new
  Component:  GIS|Version:  1.10
   Severity:  Normal |   Keywords:  GIS, GDAL, Contrib,
   Triage Stage: |  Bug
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Under some circumstances `django.contrib.gis.gdal.HAS_GDAL` is `False`.
 This can be due to not having GDAL installed in the first place or by
 overriding one's OS name (and thereby causing the test in
 `django.contrib.gis.gdal.__init__.py` to result in an exception which in
 turns causes `HAS_GDAL = False`).¹


 Now with `HAS_GDAL = False`, I can't start Django anymore (neither the
 shell or any other command), because I get the following error:
 {{{
 django.core.exceptions.ImproperlyConfigured: 'postgresql' isn't an
 available database backend.
 Try using 'django.db.backends.XXX', where XXX is one of:
 'mysql', 'oracle', 'postgresql', 'sqlite3'
 Error was: No module named postgresql.base
 }}}

 Digging a bit deeper into this reveals this is actually an ImportError:
 `Error was: cannot import name GDALRaster`. Using other
 `django.contrib.gis` functionality should also work without GDAL (and did
 so in the past).

 The problem seems to be that in commit
 `bbfad84dd980a97174c3b061a3d1b5f1373c380d`
 
([https://github.com/django/django/commit/bbfad84dd980a97174c3b061a3d1b5f1373c380d
 #diff-9501b5a77c1985430f52d03aedb3e434R7 here]) a new import has been
 added to `django/contrib/gis/db/backends/postgis/operations.py`, which
 tries to import `GDALRaster`: `from django.contrib.gis.gdal import
 GDALRaster`. This of course fails with `HAS_GDAL = False`, because
 `GDALRaster` has never been defined when `HAS_GDAL` was set false due to
 an (expected) exception in `django/django/contrib/gis/gdal/libgdal.py`,
 which is imported before `from django.contrib.gis.gdal.raster.source
 import GDALRaster` in `django/django/contrib/gis/gdal/__init__.py`.

 So maybe the import in
 `django/contrib/gis/db/backends/postgis/operations.py` and the use of
 `GDALRaster` should be conditional and only run if `HAS_GDAL = True`. I
 can provide a patch if wanted.

 This is a problem in both Django 1.10 and 1.11.

 ¹ In my project I need to do the latter to disable GDAL support
 completely, because loading the library conflicts with `pgmagick` on
 Ubuntu and there is no other way to disable GDAL, but this shouldn't
 matter here. It would be nice though to have a way to force `HAS_GDAL =
 False`, because unlike said in
 `django/django/contrib/gis/gdal/__init__.py`, setting
 `GDAL_LIBRARY_PATH='/null/path'` doesn't work (the automatic OS checks
 override this).

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.8c553e48891ed29b0fc020ce214521ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28052: Django inadvertently removes all indexes when switching to db_index=False

[Django]

#28052: Django inadvertently removes all indexes when switching to 
db_index=False
---+
 Reporter:  Markus Holtermann  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.11
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"4c12b10263e3ff92872d33928f6d1dd820de8c0a" 4c12b102]:
 {{{
 #!CommitTicketReference repository=""
 revision="4c12b10263e3ff92872d33928f6d1dd820de8c0a"
 [1.11.x] Refs #28052 -- Cleaned up some indexes in schema tests.

 Backport of d0e43f225f59145903c72c650eeef1f80e12f9ed from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.dd57d6d10685a2fe90eb959bbdd81b6f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28052: Django inadvertently removes all indexes when switching to db_index=False

[Django]

#28052: Django inadvertently removes all indexes when switching to 
db_index=False
---+
 Reporter:  Markus Holtermann  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.11
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"d0e43f225f59145903c72c650eeef1f80e12f9ed" d0e43f2]:
 {{{
 #!CommitTicketReference repository=""
 revision="d0e43f225f59145903c72c650eeef1f80e12f9ed"
 Refs #28052 -- Cleaned up some indexes in schema tests.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a666d5952876ab2ec3de42a74babf65d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28095: Document Widget.build_attrs() signature change in Django 1.11

[Django]

#28095: Document Widget.build_attrs() signature change in Django 1.11
-+-
 Reporter:  Melvyn Sopacua   |Owner:  brian
 Type:   |  houston morrow
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.b316a9e4a95c5b0ce9b05bc317f2beeb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28100: Remove link in UserChangeForm.password's translatable help_text

[Django]

#28100: Remove link in UserChangeForm.password's translatable help_text
-+-
 Reporter:  Hélio Correia|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6e89abdc49e6c002290adb8f9e43db3cb9c889ab" 6e89abdc]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e89abdc49e6c002290adb8f9e43db3cb9c889ab"
 [1.11.x] Refs #28100 -- Added 1.11.1 release note for
 e6bfd3d751278d7cfd09af1120c4bbce509c05da.

 Backport of 941280229e8cd108c2d8ead12b0dcf3ff021bf23 from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.ae5e700e04330161a49c6980da16ed44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28100: Remove link in UserChangeForm.password's translatable help_text

[Django]

#28100: Remove link in UserChangeForm.password's translatable help_text
-+-
 Reporter:  Hélio Correia|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"941280229e8cd108c2d8ead12b0dcf3ff021bf23" 9412802]:
 {{{
 #!CommitTicketReference repository=""
 revision="941280229e8cd108c2d8ead12b0dcf3ff021bf23"
 Refs #28100 -- Added 1.11.1 release note for
 e6bfd3d751278d7cfd09af1120c4bbce509c05da.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.38c57af0e5b709a3f85623cf2c6e3344%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28159: Using InlineFormset.save_as_new crashes in Django 1.11 (was: Fix issues with InlineFormset.save_as_new in Django 1.11)

[Django]

#28159: Using InlineFormset.save_as_new crashes in Django 1.11
-+-
 Reporter:  Alexander Kavanaugh  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.11
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  inlineformset,save_as_new  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted
 * severity:  Normal => Release blocker
 * needs_tests:  0 => 1


Old description:

> Django 1.11 now marks multipart POST data as immutable [(Release notes
> section)](https://docs.djangoproject.com/en/1.11/releases/1.11/#miscellaneous).
> This causes an issue with the private ``save_as_new`` feature in
> InlineFormsets: the set code in the conditional block
> [here](https://github.com/django/django/blob/master/django/forms/models.py#L886)
> now throws an AttributeError because the data it's attempting to change
> is marked as immutable.
>
> To restore previous behavior, this pull request turns off the
> immutability flag on the form data while the save_as_new functionality
> runs and turns immutability back on when the mutation code is complete.
>
> Note that the mutable flag isn't set if there is no data, hence the
> ``hasattr`` code.
>
> PR: https://github.com/django/django/pull/8448

New description:

 Django 1.11 marks multipart POST data as immutable:
 4a246a02bdcbc13b15480c014f51cb0682af7c1e (#17235) . This causes an issue
 with the private `save_as_new` feature in InlineFormsets: the set code in
 the conditional block in
 
[https://github.com/django/django/blob/05098fa4494e66e1d3750d7f4821f7b3114693b9/django/forms/models.py#L886
 BaseInlineFormSet._construct_form()] now raises `AttributeError` because
 the data it's attempting to change is marked as immutable.

 To restore previous behavior, [https://github.com/django/django/pull/8448
 this pull request] turns off the immutability flag on the form data while
 the save_as_new functionality runs and turns immutability back on when the
 mutation code is complete.

 Note that the mutable flag isn't set if there is no data, hence the
 `hasattr` code.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.486e1e874eff23fdafcd14a7502c8224%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28158: Error in tutorials

[Django]

#28158: Error in tutorials
-+--
 Reporter:  Abraham Mercado  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Uncategorized => Documentation


Comment:

 It's correct as is. Maybe you missed the `from .models import Question`
 import.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.57c9ad4d991cca6753d536b18ab5344a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28159: Fix issues with InlineFormset.save_as_new in Django 1.11

[Django]

#28159: Fix issues with InlineFormset.save_as_new in Django 1.11
-+-
   Reporter:  Alexander  |  Owner:  nobody
  Kavanaugh  |
   Type:  Bug| Status:  new
  Component:  Forms  |Version:  1.11
   Severity:  Normal |   Keywords:
   Triage Stage: |  inlineformset,save_as_new
  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Django 1.11 now marks multipart POST data as immutable [(Release notes
 section)](https://docs.djangoproject.com/en/1.11/releases/1.11/#miscellaneous).
 This causes an issue with the private ``save_as_new`` feature in
 InlineFormsets: the set code in the conditional block
 
[here](https://github.com/django/django/blob/master/django/forms/models.py#L886)
 now throws an AttributeError because the data it's attempting to change is
 marked as immutable.

 To restore previous behavior, this pull request turns off the immutability
 flag on the form data while the save_as_new functionality runs and turns
 immutability back on when the mutation code is complete.

 Note that the mutable flag isn't set if there is no data, hence the
 ``hasattr`` code.

 PR: https://github.com/django/django/pull/8448

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.27828fd0d7fd5794f0a7a5614f88c960%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28139: Add one more level in the topics main index

[Django]

#28139: Add one more level in the topics main index
---+--
 Reporter:  Shai Berger|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by Shai Berger):

 Thanks!

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.8d76b33f14562986d8ccc4eeff4e0816%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28158: Error in tutorials

[Django]

#28158: Error in tutorials
-+--
 Reporter:  Abraham Mercado  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Abraham Mercado):

 * Attachment "Screen Shot 2017-05-01 at 6.01.49 PM.png" added.

 Example

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b2864850e2a1edaea70d9e50b1604aca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28158: Error in tutorials

[Django]

#28158: Error in tutorials
---+
   Reporter:  Abraham Mercado  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Uncategorized|Version:  1.11
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Hello, on the 3rd part of the tutorial, i think there is an error,  This
 is the URL: https://docs.djangoproject.com/en/1.11/intro/tutorial03/
 The section that has the error is the "Raising a 404" section. it says:

  except Question.DoesNotExist:

 when i think it should be "question" instead of "Question"

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.2ae38f07254f44e8d04515c126d8e0af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28095: Document Widget.build_attrs() signature change in Django 1.11

[Django]

#28095: Document Widget.build_attrs() signature change in Django 1.11
-+-
 Reporter:  Melvyn Sopacua   |Owner:  brian
 Type:   |  houston morrow
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by brian houston morrow):

 Okay, that makes sense.
 I've removed that part of the commit and left the remaining changes to the
 1.11 release note in this  [https://github.com/django/django/pull/8447
 pull request].

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.6537f8141398c5204b04f36a50b9de59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28157: Options order is lost in choicefields when mixing grouped and non-grouped options.

[Django]

#28157: Options order is lost in choicefields when mixing grouped and 
non-grouped
options.
--+
   Reporter:  atopus  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  1.11
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  1   |
--+
 With this tuple (fetched from django documentation),

 {{{
 MEDIA_CHOICES = (
 ('Audio', (
 ('vinyl', 'Vinyl'),
 ('cd', 'CD'),
 )
 ),
 ('Video', (
 ('vhs', 'VHS Tape'),
 ('dvd', 'DVD'),
 )
 ),
 ('unknown', 'Unknown'),
 )
 }}}

 the "unknown" option is displayed at the beginning of the dropbox.

 More generally, every non-grouped options are displayed first, followed by
 grouped options.

 If an embedded mix of them is needed -- which is my case -- the order is
 entirely lost.

 I guess this is not the expected behavior.

 Thanks for your assistance,

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.310a231c8bcedec2bb0d2cc42ae0714c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28052: Django inadvertently removes all indexes when switching to db_index=False

[Django]

#28052: Django inadvertently removes all indexes when switching to 
db_index=False
---+
 Reporter:  Markus Holtermann  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.11
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Tim Graham ):

 In [changeset:"6afede82192067efecedb039c29eb301816d5fb5" 6afede8]:
 {{{
 #!CommitTicketReference repository=""
 revision="6afede82192067efecedb039c29eb301816d5fb5"
 [1.11.x] Fixed #28052 -- Prevented dropping Meta.indexes when changing
 db_index to False.

 Thanks Marc Tamlyn for the report and Ian Foote/Tim Graham for review.

 Backport of 663e48947ff8ef3e6a6275bda2d1ee1b0de13be3 from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a48590ea81788afa0e77e8507cbc8c46%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28052: Django inadvertently removes all indexes when switching to db_index=False

[Django]

#28052: Django inadvertently removes all indexes when switching to 
db_index=False
---+
 Reporter:  Markus Holtermann  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  1.11
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"663e48947ff8ef3e6a6275bda2d1ee1b0de13be3" 663e4894]:
 {{{
 #!CommitTicketReference repository=""
 revision="663e48947ff8ef3e6a6275bda2d1ee1b0de13be3"
 Fixed #28052 -- Prevented dropping Meta.indexes when changing db_index to
 False.

 Thanks Marc Tamlyn for the report and Ian Foote/Tim Graham for review.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ff41ad8fa4ac69029a457003f4432a94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28043: Cloning a ModelState fails to deepcopy all options

[Django]

#28043: Cloning a ModelState fails to deepcopy all options
-+-
 Reporter:  Ian Foote|Owner:  Ian Foote
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  ModelState clone | Triage Stage:  Accepted
  indexes|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"211d2bf3f21fee22c868cd39452a133ad1e16c4d" 211d2bf3]:
 {{{
 #!CommitTicketReference repository=""
 revision="211d2bf3f21fee22c868cd39452a133ad1e16c4d"
 [1.11.x] Fixed #28043 -- Prevented AddIndex and RemoveIndex from mutating
 model state.

 Backport of 63afe3a2bfaf97fecff6641137a85296029d5b73 from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cdb6573e77b5d59b085aa465b546a383%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28043: Cloning a ModelState fails to deepcopy all options

[Django]

#28043: Cloning a ModelState fails to deepcopy all options
-+-
 Reporter:  Ian Foote|Owner:  Ian Foote
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  ModelState clone | Triage Stage:  Accepted
  indexes|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"63afe3a2bfaf97fecff6641137a85296029d5b73" 63afe3a2]:
 {{{
 #!CommitTicketReference repository=""
 revision="63afe3a2bfaf97fecff6641137a85296029d5b73"
 Fixed #28043 -- Prevented AddIndex and RemoveIndex from mutating model
 state.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1906f601814259f8206d72e1b2b432ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28095: Document Widget.build_attrs() signature change in Django 1.11

[Django]

#28095: Document Widget.build_attrs() signature change in Django 1.11
-+-
 Reporter:  Melvyn Sopacua   |Owner:  brian
 Type:   |  houston morrow
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Melvyn Sopacua):

 I don't think it should be documented.

 The apparent reason for making this backwards-incompatible change was that
 it was deemed internal (''because'' it was not documented).
 However - it is widely used in the field, as `Widget.render()` used to be
 abstract and widget implementors copied code from `InputWidget` and
 friends, which used build_attrs.

 But because it is widely used and incompatible, it should be noted in the
 release notes.

 Personally, I expect this method to be removed, as it's nothing more then
 a wrapper for `dict.update()`, with no added value (the fact that you
 could pass keyword arguments that would be added as attributes was it's
 added value, as that is much easier to type and read).

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.cbefcdcdbeaadccf092e09ac9f8d97fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28081: django.test.client:conditional_content_removal() is not compliant with RFC7230

[Django]

#28081: django.test.client:conditional_content_removal() is not compliant with
RFC7230
---+--
 Reporter:  Ed Morley  |Owner:  João Silva
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8445 PR]

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d770d5ac93eb683ee9f1d981cac8f544%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28146: PostGIS: Django 1.11 adds two extra queries: SELECT postgis_lib_version() and SELECT version()

[Django]

#28146: PostGIS: Django 1.11 adds two extra queries: SELECT 
postgis_lib_version()
and SELECT version()
-+-
 Reporter:  George Tantiras  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  GIS  |  Version:  1.11
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I'll close the ticket since the two queries are expected. Please open a
 new ticket if you identify a bug causing the increased load time.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.c526d914080b7f892148cb4dd381c19a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28139: Add one more level in the topics main index

[Django]

#28139: Add one more level in the topics main index
---+--
 Reporter:  Shai Berger|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by Tim Graham ):

 In [changeset:"ccb3b0ee679efd7c2e2f50b2e1bcd57634eecdca" ccb3b0ee]:
 {{{
 #!CommitTicketReference repository=""
 revision="ccb3b0ee679efd7c2e2f50b2e1bcd57634eecdca"
 [1.11.x] Fixed #28139 -- Added another level of headings in the topics
 index.

 Backport of 4b0211dad55fc9d154dd5fc5b0006a647115d75d from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.94609dd5c44751bad04f23e684503401%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28139: Add one more level in the topics main index

[Django]

#28139: Add one more level in the topics main index
---+--
 Reporter:  Shai Berger|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4b0211dad55fc9d154dd5fc5b0006a647115d75d" 4b0211da]:
 {{{
 #!CommitTicketReference repository=""
 revision="4b0211dad55fc9d154dd5fc5b0006a647115d75d"
 Fixed #28139 -- Added another level of headings in the topics index.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.dab355fb09ede02856e140239fa39456%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27795: Audit force_text invocations

[Django]

#27795: Audit force_text invocations
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b39aabc6c6b84cbe4005f3fdf3b9c0c4307afc76" b39aabc]:
 {{{
 #!CommitTicketReference repository=""
 revision="b39aabc6c6b84cbe4005f3fdf3b9c0c4307afc76"
 Refs #27795 -- Reworked get_or_create test erroneously mixing bytes and
 str.

 As CharField.to_python() now always calls str(), assigning bytes to a
 CharField is no longer correct usage. Doing so results in a warning:

   django/db/models/fields/__init__.py:1061: BytesWarning: str() on a bytes
 instance

 Use a unique constraint violation to trigger the database error instead.

 Warning introduced in 301de774c21d055e9e5a7073e5bffdb52bc71079.
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.dfee0083022fb3ffdf40136c5f764dd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28123: django.utils.html.smart_urlquote() is incorrectly parsing the query string

[Django]

#28123: django.utils.html.smart_urlquote() is incorrectly parsing the query 
string
+--
 Reporter:  Denis Pechenev  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Utilities   |  Version:  1.10
 Severity:  Normal  |   Resolution:  wontfix
 Keywords:  smart_urlquote  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Tim Graham):

 * status:  new => closed
 * component:  Uncategorized => Utilities
 * resolution:   => wontfix


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.75dd05b6fe9a378a5a9e7c32610fa933%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28145: Django documention - MySQL database connector - PyMySQL for python 3 support

[Django]

#28145: Django documention - MySQL database connector -  PyMySQL for python 3
support
---+--
 Reporter:  kinganu|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.11
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  mysql  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => needsinfo


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a53e765861a7cfc5788f72a147dcf876%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28156: User.has_perm always returns False for a custom permission inherited from group

[Django]

#28156: User.has_perm always returns False for a custom permission inherited 
from
group
--+--
 Reporter:  Vasili Korol  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:  invalid
 Keywords:  permissions   | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Tim Graham):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 You put the permission's name first in the tuple rather than the codename.
 It should be: `permissions = ( ("run_task_locally", "Can run tasks on the
 local server"), )`

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.35c28f9eeac3fee2539aff8fe5365ca8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28105: BaseGeometryWidget.get_context() crashes if attrs contains the name of an existing key

[Django]

#28105: BaseGeometryWidget.get_context() crashes if attrs contains the name of 
an
existing key
-+-
 Reporter:  Dylan Verheul|Owner:  Dylan
 |  Verheul
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  gis, forms, widgets  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b1aea89dee4598857aaa3847f996e7cd03316a10" b1aea89]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1aea89dee4598857aaa3847f996e7cd03316a10"
 [1.11.x] Fixed #28105 -- Fixed crash in BaseGeometryWidget.get_context()
 when overriding existing attrs.

 Backport of 75aeebebfe3df3ea46b8e12dd5e7719f98664d3a from master
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.2a8fea5ba91ac4f8c3cad2b14994f253%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28156: User.has_perm always returns False for a custom permission inherited from group

[Django]

#28156: User.has_perm always returns False for a custom permission inherited 
from
group
--+--
 Reporter:  V.Korol   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  permissions   | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by V.Korol):

 * type:  Uncategorized => Bug


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.805995c458f25860677c1c6e8272c6e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28156: User.has_perm always returns False for a custom permission inherited from group

[Django]

#28156: User.has_perm always returns False for a custom permission inherited 
from
group
-+-
   Reporter:  V.Korol|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  contrib.auth   |Version:  1.8
   Severity:  Normal |   Keywords:  permissions
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I define a custom permission in one of my models (in application called
 'tasks'):

 {{{
 class Task ( models.Model ) :
 ...
 class Meta :
  permissions = ( ( "Can run tasks on the local server",
 "run_task_locally" ), )
 }}}

 In the admin interface, I grant this permission to one of the auth groups.
 Now, for all users, belonging to this group,  {{{user.has_perm(
 "tasks.run_task_locally" )}}} is {{{False}}}. If the permission is granted
 for each user individually (not through the group), or if it's a
 supersuser, then {{{user.has_perm}}} returns {{{True}}}.

 I do not observe this problem with standard model permissions like
 ''appname.add_modelname'' or ''appname.change_modelname''.

 Running Django 1.8.18 on Python 3.4.3 using default authentication
 backend.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.21176d064c51a23f88e073c37f68609a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28081: django.test.client:conditional_content_removal() is not compliant with RFC7230

[Django]

#28081: django.test.client:conditional_content_removal() is not compliant with
RFC7230
---+--
 Reporter:  Ed Morley  |Owner:  João Silva
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by João Silva):

 * owner:  nobody => João Silva
 * status:  new => assigned


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ba2a2465501f1d54363704523f63e6e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27554: Queryset evaluation fails with mix of nested and flattened prefetches (AttributeError on RelatedManager)

[Django]

#27554: Queryset evaluation fails with mix of nested and flattened prefetches
(AttributeError on RelatedManager)
-+-
 Reporter:  Anthony Leontiev |Owner:  François
 |  Freitag
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch | Triage Stage:  Accepted
  AttributeError prefetch_related|
  nested RelatedManager  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Pascal Briet):

 Any update on this issue ?
 It prevents us from migrating to 1.10

 Thanks !

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f8c0f97d13f05c86fba85b34eedf6518%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28105: BaseGeometryWidget.get_context() crashes if attrs contains the name of an existing key

[Django]

#28105: BaseGeometryWidget.get_context() crashes if attrs contains the name of 
an
existing key
-+-
 Reporter:  Dylan Verheul|Owner:  Dylan
 |  Verheul
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  1.11
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  gis, forms, widgets  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Was the backport to 1.11 omitted?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.8057bb86da680e2ca583c9700dcc8f2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.