Re: [Django] #21333: Document queryset OR using a vertical bar

[Django]

#21333: Document queryset OR using a vertical bar
-+-
 Reporter:  Daniele Procida  |Owner:  Colm
 Type:   |  O'Connor
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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:"e410dce696d4b8aa8966e7c0931129015a6d84df" e410dce6]:
 {{{
 #!CommitTicketReference repository=""
 revision="e410dce696d4b8aa8966e7c0931129015a6d84df"
 [2.1.x] Fixed #21333 -- Doc'd the & and | queryset operators.

 Backport of c530428d360daf904c9e98515ea836643a73a54c 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.0d812ac9a87beb503f2670fae6e86521%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21333: Document queryset OR using a vertical bar

[Django]

#21333: Document queryset OR using a vertical bar
-+-
 Reporter:  Daniele Procida  |Owner:  Colm
 Type:   |  O'Connor
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"c530428d360daf904c9e98515ea836643a73a54c" c530428d]:
 {{{
 #!CommitTicketReference repository=""
 revision="c530428d360daf904c9e98515ea836643a73a54c"
 Fixed #21333 -- Doc'd the & and | queryset operators.
 }}}

-- 
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.d227c140876caccc38f98479f77a6c21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29261: Clarify the reason for LICENSE.python

[Django]

#29261: Clarify the reason for LICENSE.python
---+-
 Reporter:  James Bennett  |Owner:  James Bennett
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  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:"48b327aef1095a8978ba8d320d706949c1ec41da" 48b327ae]:
 {{{
 #!CommitTicketReference repository=""
 revision="48b327aef1095a8978ba8d320d706949c1ec41da"
 Fixed #29261 -- Doc'd the reason for LICENSE.python.
 }}}

-- 
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/069.990a339be7acdb027c14ba22d49f9d06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28077: Allow specifying custom operator classes for PostgreSQL indexes

[Django]

#28077: Allow specifying custom operator classes for PostgreSQL indexes
-+-
 Reporter:  IzyJeepee|Owner:  Ian Foote
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres, gin,   | Triage Stage:  Accepted
  operator, class|
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:"38cada7c94f5f73d2d47a0a730ea5d71d266fa2c" 38cada7]:
 {{{
 #!CommitTicketReference repository=""
 revision="38cada7c94f5f73d2d47a0a730ea5d71d266fa2c"
 Fixed #28077 -- Added support for PostgreSQL opclasses in Index.

 Thanks Vinay Karanam for the initial patch.
 }}}

-- 
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.30544dae94ba22e9ce3eac1a816f4743%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28144: Add allow_overwrite kwarg to FileSystemStorage._save

[Django]

#28144: Add allow_overwrite kwarg to FileSystemStorage._save
-+-
 Reporter:  Jon Prindiville  |Owner:  Jon
 |  Prindiville
 Type:  New feature  |   Status:  closed
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  file storage | Triage Stage:  Accepted
  overwrite  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b4cba4ed625ce7c88675616b3bbb237c28a926d1" b4cba4e]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4cba4ed625ce7c88675616b3bbb237c28a926d1"
 Fixed #28144 -- Added FileSystemStorage.OS_OPEN_FLAGS to allow
 customization.
 }}}

-- 
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.8956bde03b6aaa0bb01cf8c6f53a6d65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28643: Complete the ORM Function Library

[Django]

#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_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/064.479362f561e7e93f4eb7530316c90a0e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29537: Uploaded big files (>2621440 B) not readable by the server

[Django]

#29537: Uploaded big files (>2621440 B) not readable by the server
-+-
 Reporter:  fp4code  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:  duplicate
 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:   => duplicate
 * component:  Core (Other) => File uploads/storage


Comment:

 Looks like a duplicate of #28540.

-- 
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.102ebb813f998d353b00df65fd8df2df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  Ashaba
 |  John
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 Ashaba John):

 Replying to [comment:3 user0007]:
 > Replying to [comment:2 Ashaba John]:
 > Any chance to see fix for that in 2.1 release?
 Hey,

 Sorry for the delayed implementation. Will work on it and we should have
 it in the 2.1 release. 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/066.9d5b2e66975e122cd8c06254a2b08095%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29129: Child model updates parent model with empty fields making an extra query in multi-inheritance when parent model has custom PK

[Django]

#29129: Child model updates parent model with empty fields making an extra 
query in
multi-inheritance when parent model has custom PK
-+-
 Reporter:  user0007 |Owner:  Ashaba
 |  John
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 user0007):

 Replying to [comment:2 Ashaba John]:
 Any chance to see fix for that in 2.1 release?

-- 
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.957191f3104016dd19b4a18206c851d5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29224: Migration crashes deleting an index_together if there is a unique_together on the same fields

[Django]

#29224: Migration crashes deleting an index_together if there is a 
unique_together
on the same fields
+
 Reporter:  Matthieu Rigal  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  index   | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by Jeff):

 * cc: Jeff (added)


-- 
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.b706759ea960f3946a279add6d500adb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29224: Migration crashes deleting an index_together if there is a unique_together on the same fields

[Django]

#29224: Migration crashes deleting an index_together if there is a 
unique_together
on the same fields
+
 Reporter:  Matthieu Rigal  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.11
 Severity:  Normal  |   Resolution:
 Keywords:  index   | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Jeff):

 I haven't looked under the hood on this yet, but could it be related to
 the ordering of the operations generated for the mgiration? on first
 inspection it feels like this and
 [https://code.djangoproject.com/ticket/28862 #28862] could be caused by
 the same/similar underlying problem in how `FieldRelatedOptionOperation`
 subclasses ordering is handled in the migration `autodetector`'s migration
 optimizer.

-- 
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.64a8d129ee47b9a43ea6df2b76f65949%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29537: Uploaded big files (>2621440 B) not readable by the server

[Django]

#29537: Uploaded big files (>2621440 B) not readable by the server
+
   Reporter:  fp4code   |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Other)  |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 |
+
 There is a non-coherent uploading treatment between small and big files,
 this can be problematic if different users are involved for main and
 django servers
 (eg www-data for nginx and mysite for uwsgi processes).

 If the file is small, the MemoryFileUploadHandler is used, file is 0o644,
 readable by the server.

 If the file is big, the TemporaryFileUploadHandler is used, files are
 uploaded 0o600 in /tmp,
 and moved by file_move_safe which keeps attributes. Hence the file is not
 readable by the www-data server.

 A workaround is to define FILE_UPLOAD_PERMISSIONS=0o644,
 but it should be good to have a coherent behavior,
 taking into account that discovering this configuration anomaly is not
 immediate.

-- 
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.12a1e6e8efac03980e6d97341c040426%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17235: Multipartparser shouldn't leave request.POST/request.FILES mutable

[Django]

#17235: Multipartparser shouldn't leave request.POST/request.FILES mutable
-+-
 Reporter:  Florian Apolloner|Owner:  vinay
 |  karanam
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  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 vinay karanam):

 * owner:  (none) => vinay karanam
 * status:  new => assigned


Comment:

 [https://github.com/django/django/pull/10110 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.b940b0ddcfff71c61507a5336aa809ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js boxes don't resize to have equal height

[Django]

#29536: SelectFilter2.js boxes don't resize to have equal height
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Claude Paroz ):

 In [changeset:"58a0a84c3817de94f1b108697b23b57f78d67425" 58a0a84c]:
 {{{
 #!CommitTicketReference repository=""
 revision="58a0a84c3817de94f1b108697b23b57f78d67425"
 [2.1.x] Fixed #29536 -- Fixed SelectFilter2.js resizing to make boxes have
 equal height.

 Thanks Tim Graham for the review.
 Backport of a5f139236f930df06ae0642507530ca98081e2a9 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.150dd48d6e867b7a7bc7ab27ad9c34fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js boxes don't resize to have equal height

[Django]

#29536: SelectFilter2.js boxes don't resize to have equal height
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  regression   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"a5f139236f930df06ae0642507530ca98081e2a9" a5f13923]:
 {{{
 #!CommitTicketReference repository=""
 revision="a5f139236f930df06ae0642507530ca98081e2a9"
 Fixed #29536 -- Fixed SelectFilter2.js resizing to make boxes have equal
 height.

 Thanks Tim Graham for the 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.782596d79d4bade4796cc6a2df7f9043%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29533: Flushing stdout in django-admin command

[Django]

#29533: Flushing stdout in django-admin command
-+-
 Reporter:  David Ruggles|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  2.0
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 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:   => wontfix


Comment:

 I think we'll instead pursue making management commands use logging
 (#21429).

-- 
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.a645caa36127afc960f6f95618a12f0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js boxes don't resize to have equal height (was: SelectFilter2.js box resizing code has no effect)

[Django]

#29536: SelectFilter2.js boxes don't resize to have equal height
-+-
 Reporter:  Claude Paroz |Owner:  Claude
 |  Paroz
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  regression   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Tim Graham):

 * stage:  Accepted => Ready for checkin


-- 
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.e6521c7f9fdaff638ad022d4da50dcfd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29237: ModelAdmin.inlines cause a model to lose its primary key from a model field default

[Django]

#29237: ModelAdmin.inlines cause a model to lose its primary key from a model 
field
default
---+
 Reporter:  Gunnar Thielebein  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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:  0  |UI/UX:  0
---+
Changes (by Jeff):

 * cc: Jeff (added)


-- 
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.26efd492029c7fb1222ae59f7a1c369d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20147: Provide an alternative to request.META for accessing HTTP headers

[Django]

#20147: Provide an alternative to request.META for accessing HTTP headers
---+---
 Reporter:  Luke Plant |Owner:  santiagobasulto
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by Tim Graham):

 * needs_better_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/067.2b60474d5dfbb9897b36711698629e49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29504: JSONField dictionary/object lookup using an "integer" key

[Django]

#29504: JSONField dictionary/object lookup using an "integer" key
--+
 Reporter:  Shaheed Haque |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  wontfix
 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
 * type:  Uncategorized => Cleanup/optimization
 * resolution:   => wontfix


Comment:

 Closing per discussion on 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/070.f12ff6d06bd9c938e5a392d23d4f421f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29480: mysql constraints are sometimes retrieved out of the order that they are defined in

[Django]

#29480: mysql constraints are sometimes retrieved out of the order that they are
defined in
-+-
 Reporter:  Thomas Grainger  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   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:"4fba321a457e52df77d0b512d043019e9f6b0bc9" 4fba321a]:
 {{{
 #!CommitTicketReference repository=""
 revision="4fba321a457e52df77d0b512d043019e9f6b0bc9"
 Fixed #29480 -- Made MySQL backend retrieve constraint columns in their
 defined order.
 }}}

-- 
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.ef8bfad11d512fcaf63ad862a2e687bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29525: Handle strings as allowed_hosts arguments to is_safe_url()

[Django]

#29525: Handle strings as allowed_hosts arguments to is_safe_url()
--+
 Reporter:  Przemysław Suliga |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  master
 Severity:  Normal|   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:"d22b90b4eabc1fe9b7b35aada441e0edf5ebd6d8" d22b90b4]:
 {{{
 #!CommitTicketReference repository=""
 revision="d22b90b4eabc1fe9b7b35aada441e0edf5ebd6d8"
 Fixed #29525 -- Allowed is_safe_url()'s allowed_hosts arg to be a string.
 }}}

-- 
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.ac85a2a0d23889c88b153a60e5ce5226%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js box resizing code has no effect

[Django]

#29536: SelectFilter2.js box resizing code has no effect
---+
 Reporter:  Claude Paroz   |Owner:  Claude Paroz
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Claude Paroz):

 * has_patch:  0 => 1
 * ui_ux:  0 => 1


Comment:

 [https://github.com/django/django/pull/10109 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/065.3fab0036ab6fe2b4d06a104756b36678%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js box resizing code has no effect

[Django]

#29536: SelectFilter2.js box resizing code has no effect
---+
 Reporter:  Claude Paroz   |Owner:  Claude Paroz
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz):

 * owner:  nobody => Claude Paroz
 * status:  new => assigned


Comment:

 I think I can handle 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/065.a7ddb9cf6b3b50563696aef2fccca050%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js box resizing code has no effect

[Django]

#29536: SelectFilter2.js box resizing code has no effect
---+
 Reporter:  Claude Paroz   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz):

 * Attachment "Capture d'écran de 2018-06-29 16-03-42.png" added.

 Current look with size mismatch

-- 
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.42073221493179503b01373725184bbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29536: SelectFilter2.js box resizing code has no effect

[Django]

#29536: SelectFilter2.js box resizing code has no effect
---+
 Reporter:  Claude Paroz   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords:  regression | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Claude Paroz):

 * Attachment "Capture d'écran de 2018-06-29 16-03-50.png" added.

 What it used to look like

-- 
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.8b4f0b4819ae628ac6e3ee1ecc422a46%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29536: SelectFilter2.js box resizing code has no effect

[Django]

#29536: SelectFilter2.js box resizing code has no effect
-+
   Reporter:  Claude Paroz   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  2.0
   Severity:  Normal |   Keywords:  regression
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 SelectFilter2.js has some code to resize select boxes to the same height
 in horizontal mode.
 
https://github.com/claudep/django/blob/78912ccd0e1fcdfe98ca85081c9eb8acb7aa1f6d/django/contrib/admin/static/admin/js/SelectFilter2.js#L166

 Obviously this doesn't work any more. JS coder needed!

-- 
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.7ef7032b81b05ac601d9509532cc5870%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29501: Add support for ./manage.py dbshell -c SQL

[Django]

#29501: Add support for ./manage.py dbshell -c SQL
-+-
 Reporter:  Artem Skoretskiy |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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 Artem Skoretskiy):

 No progress AKAIK.

 Maybe it would be easier to call database-specific CLI tool with right
 parameters than run cursor.

 Pros:
 * No need to care about printing results (user could execute SELECT)
 * Could run commands that are unique for the CLI (e.g. \dt to show tables
 in psql)

 Cons:
 * Each backend would need its own command to run (but we already have
 dbshell, so we know name of binary; just need a parameter to execute a
 query).
 * Each backend would show results in its own format, so you cannot e. g.
 save result as cab file)

 Another completely different approach would be to pass all command line
 arguments provided to dbshell, e.g. after “—“ divider to database CLI app.
 For example:
 {{{
 ./manage.py dbshell — -c “select * from auth_user”
 }}}

-- 
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.dd339b1cd2431d4783ce529542780085%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29535: Updated email.MIME* references for Python 3

[Django]

#29535: Updated email.MIME* references for Python 3
-+-
 Reporter:  José L. Patiño   |Owner:  nobody
  Andrés |
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  2.0
 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:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"a881499a77c814f65c0dd40dc5f3964fb870b0dd" a881499a]:
 {{{
 #!CommitTicketReference repository=""
 revision="a881499a77c814f65c0dd40dc5f3964fb870b0dd"
 [2.0.x] Fixed #29535 -- Updated email.MIME* references for Python 3.

 Backport of b5dd6ef3d52544ec7533509915c61545d5c3d85a 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/066.e045071cedfa65b67084cdc380de402c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29535: Updated email.MIME* references for Python 3

[Django]

#29535: Updated email.MIME* references for Python 3
-+-
 Reporter:  José L. Patiño   |Owner:  nobody
  Andrés |
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  2.0
 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:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b5dd6ef3d52544ec7533509915c61545d5c3d85a" b5dd6ef]:
 {{{
 #!CommitTicketReference repository=""
 revision="b5dd6ef3d52544ec7533509915c61545d5c3d85a"
 Fixed #29535 -- Updated email.MIME* references for Python 3.
 }}}

-- 
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.ecbbbc908de850f196867cb969d1c1ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29535: Updated email.MIME* references for Python 3

[Django]

#29535: Updated email.MIME* references for Python 3
-+-
 Reporter:  José L. Patiño   |Owner:  nobody
  Andrés |
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  2.0
 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:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"dfbfa3abedeecabc34f4a3fcbb8d8b9f4fb35e62" dfbfa3a]:
 {{{
 #!CommitTicketReference repository=""
 revision="dfbfa3abedeecabc34f4a3fcbb8d8b9f4fb35e62"
 [2.1.x] Fixed #29535 -- Updated email.MIME* references for Python 3.

 Backport of b5dd6ef3d52544ec7533509915c61545d5c3d85a 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/066.38133a8ca45f4ef1d0d0c75ee5a4476c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29535: Updated email.MIME* references for Python 3 (was: Errors in "Sending email" documentation)

[Django]

#29535: Updated email.MIME* references for Python 3
-+-
 Reporter:  José L. Patiño   |Owner:  nobody
  Andrés |
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Ready for checkin


-- 
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.3425db19199f024da9f277d4e4469b8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29459: Make Form data/files initialize with an empty MultiValueDict rather than dict

[Django]

#29459: Make Form data/files initialize with an empty MultiValueDict rather than
dict
--+
 Reporter:  Sven R. Kunze |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Forms |  Version:  2.0
 Severity:  Normal|   Resolution:
 Keywords:  Form QueryDict| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+

Comment (by Herbert Fortes):

 IMHO, an empty dict should not make too much noise on the code. For now at
 least.

-- 
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.7d6b0a2cb7e69211209534de7ed3b3ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29501: Add support for ./manage.py dbshell -c SQL

[Django]

#29501: Add support for ./manage.py dbshell -c SQL
-+-
 Reporter:  Artem Skoretskiy |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 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 Volodymyr Dmytriiev):

 any progress on this one? Is the previously suggested approach good
 enough? If so, I'd love to give a try?

-- 
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.aa4448d62b114d160a972a859cdbc949%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29535: Errors in "Sending email" documentation

[Django]

#29535: Errors in "Sending email" documentation
-+-
 Reporter:  José L. Patiño   |Owner:  nobody
  Andrés |
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  2.0
 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
-+-

Comment (by José L. Patiño Andrés):

 I have submitted a [https://github.com/django/django/pull/10107 pull
 request for this one].

-- 
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.7087a45f696b290edc2403ebdc691779%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29535: Errors in "Sending email" documentation

[Django]

#29535: Errors in "Sending email" documentation
-+-
 Reporter:  José L. Patiño   |Owner:  nobody
  Andrés |
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  2.0
 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
-+-
Description changed by José L. Patiño Andrés:

Old description:

> There are a couple of errors in the
> [https://docs.djangoproject.com/en/2.0/topics/email/ "Sending email"]
> documentation page.
>
> The "attachments" instructions always says the attachments can be "either
> `email.MIMEBase.MIMEBase` instances, or (filename, content, mimetype)
> triples.". Turns out the `email.MIMEBase.MIMEBase` module does not exist,
> and the correct one is
> [https://docs.python.org/3/library/email.mime.html#email.mime.base.MIMEBase
> `email.mime.base.MIMEBase`].
>
> Error can be found in
> [https://github.com/django/django/blob/master/docs/topics/email.txt#L275
> this] and
> [https://github.com/django/django/blob/master/docs/topics/email.txt#L330
> this] lines of the documentation.

New description:

 There are a couple of errors in the
 [https://docs.djangoproject.com/en/2.0/topics/email/ "Sending email"]
 documentation page.

 The "attachments" instructions always says the attachments can be "either
 `email.MIMEBase.MIMEBase` instances, or (filename, content, mimetype)
 triples.". Turns out the `email.MIMEBase.MIMEBase` module does not exist,
 and the correct one is `email.mime.base.MIMEBase` as can be seen in
 [https://docs.python.org/3/library/email.mime.html#email.mime.base.MIMEBase
 Python docs].

 Error can be found in
 [https://github.com/django/django/blob/master/docs/topics/email.txt#L275
 this] and
 [https://github.com/django/django/blob/master/docs/topics/email.txt#L330
 this] lines of the documentation.

--

-- 
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.a98f7ee1794c84f1f7c7a5e4c239ff77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29535: Errors in "Sending email" documentation

[Django]

#29535: Errors in "Sending email" documentation
-+
   Reporter:  José L. Patiño Andrés  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  2.0
   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  |
-+
 There are a couple of errors in the
 [https://docs.djangoproject.com/en/2.0/topics/email/ "Sending email"]
 documentation page.

 The "attachments" instructions always says the attachments can be "either
 `email.MIMEBase.MIMEBase` instances, or (filename, content, mimetype)
 triples.". Turns out the `email.MIMEBase.MIMEBase` module does not exist,
 and the correct one is
 [https://docs.python.org/3/library/email.mime.html#email.mime.base.MIMEBase
 `email.mime.base.MIMEBase`].

 Error can be found in
 [https://github.com/django/django/blob/master/docs/topics/email.txt#L275
 this] and
 [https://github.com/django/django/blob/master/docs/topics/email.txt#L330
 this] lines of the documentation.

-- 
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/051.a5dac9639c813165564b46670ecb4ccd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29532: Make model/app urls configurable for admin

[Django]

#29532: Make model/app urls configurable for admin
-+-
 Reporter:  Ramez Issac  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  2.1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  admin , url, | Triage Stage:
  routing|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ramez Issac):

 If you don't like putting as admin specific option in the Meta, (and i
 tend to agree)  then, for this specific use, where you think it should it
 go ?!

 It's not that big of an api change, and maybe there are more and more uses
 cases that can benefit from this.
 A discussion maybe ?

-- 
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/068.1cdf7af4383209aa1669c7a114e6f312%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.