Re: [Django] #29336: No docs for circular template inheritance (was: No docs for circular inheritance)

2019-08-31 Thread Django 
#29336: No docs for circular template inheritance
-+-
 Reporter:  Adrian Turjak|Owner:  Adrian
 Type:   |  Turjak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.0
 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 frnhr):

 * cc: frnhr (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e2e924a5f8f3b6d84989476fe723b334%40djangoproject.com.

Re: [Django] #30405: IndexError in _get_lines_from_file when module does not match file contents (via loader)

2019-08-31 Thread Django 
#30405: IndexError in _get_lines_from_file when module does not match file 
contents
(via loader)
-+-
 Reporter:  Daniel Hahler|Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Error reporting  |  Version:  2.2
 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 Hasan Ramezani):

 * owner:  (none) => Hasan Ramezani
 * status:  new => assigned


Comment:

 @Florian, as far as I understand the solution would be something like
 this. am I right?


 {{{
 diff --git a/django/views/debug.py b/django/views/debug.py
 index 86da47ee20..8af1c2e1ca 100644
 --- a/django/views/debug.py
 +++ b/django/views/debug.py
 @@ -349,7 +349,7 @@ class ExceptionReporter:
  if hasattr(loader, 'get_source'):
  try:
  source = loader.get_source(module_name)
 -except ImportError:
 +except Exception:
  pass
  if source is not None:
  source = source.splitlines()

 }}}

 If you agree with me I can prepare a patch and include the 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.9ed72326e298b2d531b717740f199805%40djangoproject.com.

Re: [Django] #29406: Add Referrer-Policy header support

2019-08-31 Thread Django 
#29406: Add Referrer-Policy header support
---+-
 Reporter:  James Bennett  |Owner:  James Bennett
 Type:  New feature|   Status:  assigned
Component:  Utilities  |  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 Claude Paroz):

 * has_patch:  0 => 1
 * stage:  Someday/Maybe => Accepted


Comment:

 I reopened a [https://github.com/django/django/pull/11732 PR] based on
 James initial work.
 I hope that in conjunction with #30426, this would mean a more secure
 Django 3.0 by default.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.4921c020069aa5f4d22da2faf79278fc%40djangoproject.com.

Re: [Django] #30426: Make security headers default.

2019-08-31 Thread Django 
#30426: Make security headers default.
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  New feature  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam (Chainz) Johnson):

 It seems the consensus is to make it DENY by default with a warning - any
 objections?

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.fd0160ea3db14f2d2719b26c1a07be31%40djangoproject.com.

Re: [Django] #30741: sqlmigrate doesn't show a drop constraint SQL when previous create constrain operation wasn't perform. (was: Setting db_constraint=False to an existing column does not properly dr

2019-08-31 Thread Django 
#30741: sqlmigrate doesn't show a drop constraint SQL when previous create
constrain operation wasn't perform.
-+-
 Reporter:  Scott Stafford   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  db_constraint,   | Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * type:  Uncategorized => Bug
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 Thanks for this report, however IMO everything works properly.

 Removing constraints is based on introspection, hence SQL generated by the
 second migration is empty because you didn't run the first migration that
 creates constraint and in a consequence the second one wasn't able to
 introspect a non-existent constraint.

 0002 - SQL (before performing the first migration)
 {{{
 BEGIN;
 --
 -- Alter field parent on child
 --
 COMMIT;
 }}}

 0002 - SQL (after performing the first migration)
 {{{
 BEGIN;
 --
 -- Alter field parent on child
 --
 SET CONSTRAINTS
 "test_30741_child_parent_id_f98c7dab_fk_test_30741_parent_id" IMMEDIATE;
 ALTER TABLE "test_30741_child" DROP CONSTRAINT
 "test_30741_child_parent_id_f98c7dab_fk_test_30741_parent_id";
 COMMIT;
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3cddbf2d709bf4e8195b06167f3e6ccd%40djangoproject.com.

Re: [Django] #30744: Where did fulltext index support for MySQL go?

2019-08-31 Thread Django 
#30744: Where did fulltext index support for MySQL go?
-+-
 Reporter:  Mike Robinson|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 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 felixxm):

 * status:  new => closed
 * component:  Uncategorized => Database layer (models, ORM)
 * resolution:   => invalid
 * type:  Uncategorized => Cleanup/optimization


Comment:

 `__search` lookup was [https://docs.djangoproject.com/en/2.2/releases/1.10
 /#search-query-lookup deprecated in Django 1.10] and
 [https://docs.djangoproject.com/en/2.2/releases/2.0/#features-removed-
 in-2-0 removed in Django 2.0].

 Closing per TicketClosingReasons/UseSupportChannels.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.f25f6e1b824b3e70875886226f0747c6%40djangoproject.com.

Re: [Django] #30738: Misleading multiwidget template example.

2019-08-31 Thread Django 
#30738: Misleading multiwidget template example.
-+-
 Reporter:  Emmanuel Cazenave|Owner:  Daria
 Type:   |  Kolodzey
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.2
 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 Mariusz Felisiak ):

 In [changeset:"11cdfb340830abe57142e1fbc8bfae835b0f1183" 11cdfb34]:
 {{{
 #!CommitTicketReference repository=""
 revision="11cdfb340830abe57142e1fbc8bfae835b0f1183"
 [2.2.x] Fixed #30738 -- Fixed typo in docs/ref/forms/widgets.txt.

 Thanks Emmanuel Cazenave for the report.
 Backport of 3f8ee58ccc5c55e62625ad797ddde05778fe1bec 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.fb982f00d2ea69fdbddf9ba1e059d2ab%40djangoproject.com.

Re: [Django] #30738: Misleading multiwidget template example.

2019-08-31 Thread Django 
#30738: Misleading multiwidget template example.
-+-
 Reporter:  Emmanuel Cazenave|Owner:  Daria
 Type:   |  Kolodzey
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.2
 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
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"3f8ee58ccc5c55e62625ad797ddde05778fe1bec" 3f8ee58c]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f8ee58ccc5c55e62625ad797ddde05778fe1bec"
 Fixed #30738 -- Fixed typo in docs/ref/forms/widgets.txt.

 Thanks Emmanuel Cazenave for the report.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.9159344f53693fcc9ec36417e2715324%40djangoproject.com.