Re: [Django] #30040: Documentation on permissions on templates is wrong

2018-12-15 Thread Django 
#30040: Documentation on permissions on templates is wrong
-+-
 Reporter:  Adrian Samatan   |Owner:  2w3
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  template | Triage Stage:  Accepted
  permissions documentation  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by 2w3):

 * owner:  (none) => 2w3
 * 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.d402f72369d4be1b52dfa7aeb07853b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30040: Documentation on permissions on templates is wrong

2018-12-15 Thread Django 
#30040: Documentation on permissions on templates is wrong
-+-
 Reporter:  Adrian Samatan   |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  template | Triage Stage:  Accepted
  permissions documentation  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lqez):

 * owner:  lqez => (none)
 * status:  assigned => new


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

Re: [Django] #30040: Documentation on permissions on templates is wrong

2018-12-15 Thread Django 
#30040: Documentation on permissions on templates is wrong
-+-
 Reporter:  Adrian Samatan   |Owner:  lqez
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  template | Triage Stage:  Accepted
  permissions documentation  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by lqez):

 * owner:  nobody => lqez
 * 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.017130b795422fb16b5b355e3c2ad508%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29186: "django.request" logging breaks "logging.handlers.SocketHandler"

2018-12-15 Thread Django 
#29186: "django.request" logging breaks "logging.handlers.SocketHandler"
--+-
 Reporter:  direx |Owner:  candypoplatte
 Type:  Bug   |   Status:  assigned
Component:  Core (Other)  |  Version:  2.0
 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 candypoplatte):

 * owner:  nobody => candypoplatte
 * 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/063.7b0d89a4160327be09de4b91f91b044f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30043: AdminURLFieldWidget incorrectly unquotes URLs e.g. containing %2F

2018-12-15 Thread Django 
#30043: AdminURLFieldWidget incorrectly unquotes URLs e.g. containing %2F
-+-
   Reporter:  Brenton|  Owner:  nobody
  Partridge  |
   Type:  Bug| Status:  new
  Component: |Version:  master
  contrib.admin  |   Keywords:  admin, urlfield,
   Severity:  Normal |  smart_urlquote, url, quote
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Intended behavior: If a URLField is used in the Django admin, and the
 currently saved URL in the database contains the escape %2F, the href of
 the rendered link should contain that escape verbatim (e.g. %2F, not a /
 in that location).

 Current behavior (master branch, Python 3.7.0): The href of the rendered
 link contains a / in that location, creating an extra portion of the path
 and, when clicked, sending the admin user to a completely different and
 unintended URL.

 Root cause:
 
https://github.com/django/django/blob/315357ad25a6590e7f4564ec2e56a22132b09001/django/contrib/admin/widgets.py#L340
 uses `smart_urlquote` to set the href (subsequently read by
 
https://github.com/django/django/blob/master/django/contrib/admin/templates/admin/widgets/url.html
 ).

 smart_urlquote (as implemented here:
 
https://github.com/django/django/blob/315357ad25a6590e7f4564ec2e56a22132b09001/django/utils/html.py#L203
 ) has caused problems before e.g.
 https://code.djangoproject.com/ticket/28123 . That issue, though, refers
 to a backport, whereas this behavior is broken on the master branch in
 Python 3.

 One fix would be to not use smart_urlquote, and just ensure that the href
 is set to the exact same value as initially shown in the input field and
 rendered as the text of the  tag. Is there a reason why smart_urlquote
 was used in the first place, though?

 I'm happy to submit a patch and test case if this is a desired fix.

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

Re: [Django] #30023: SQLite schema editor can cause table corruption if used within a transaction since Django 2.0

2018-12-15 Thread Django 
#30023: SQLite schema editor can cause table corruption if used within a
transaction since Django 2.0
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Release blocker  |   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 Simon Charette ):

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


Comment:

 In [changeset:"315357ad25a6590e7f4564ec2e56a22132b09001" 315357ad]:
 {{{
 #!CommitTicketReference repository=""
 revision="315357ad25a6590e7f4564ec2e56a22132b09001"
 Fixed #30023 -- Prevented SQLite schema alterations while foreign key
 checks are enabled.

 Prior to this change foreign key constraint references could be left
 pointing
 at tables dropped during operations simulating unsupported table
 alterations
 because of an unexpected failure to disable foreign key constraint checks.

 SQLite3 does not allow disabling such checks while in a transaction so
 they
 must be disabled beforehand.

 Thanks ezaquarii for the report and Carlton and Tim 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/067.e0853d5debc5daa3dd34bbd2bcadf498%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29851: Window Frame Doesn't Work In SubQuery

2018-12-15 Thread Django 
#29851: Window Frame Doesn't Work In SubQuery
-+-
 Reporter:  Daniel Fuchs |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (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
-+-
Changes (by felixxm):

 * Attachment "29851.diff" added.

 Test.

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

Re: [Django] #12952: Models history doesn't use verbose names

2018-12-15 Thread Django 
#12952: Models history doesn't use verbose names
-+-
 Reporter:  Antonio Cangiano |Owner:  Sanyam
 Type:   |  Khurana
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  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:  1
-+-
Changes (by Sanyam Khurana):

 * needs_better_patch:  1 => 0


Comment:

 Hey Carlton, I've addressed the last nit-picks in the patch. Thank you for
 your patience!

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