Re: [Django] #16614: Support server-side cursors for queryset iteration in database backends

[Django]

#16614: Support server-side cursors for queryset iteration in database backends
-+-
 Reporter:  Dan McGee|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  memory cursors   | Triage Stage:  Accepted
  database   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by François Freitag):

 * needs_docs:  1 => 0


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

Re: [Django] #24423: Combine i18n template tag tests

[Django]

#24423: Combine i18n template tag tests
--+
 Reporter:  Preston Timmons   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Internationalization  |  Version:  master
 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 Aleksandr Sobolev):

 * status:  assigned => new
 * owner:  Aleksandr Sobolev => (none)


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

Re: [Django] #27377: Clarify that prepopulated_fields doesn't work with OneToOneField

[Django]

#27377: Clarify that prepopulated_fields doesn't work with OneToOneField
-+-
 Reporter:  Malik A. Rumi|Owner:  Henry
 Type:   |  Dang
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  prepopulated_fields, admin.py  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Henry Dang):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #25492: warn about migrations mixing schema- and data- changing operations

[Django]

#25492: warn about migrations mixing schema- and data- changing operations
--+
 Reporter:  Joey Wilhelm  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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 Simon Charette):

 * has_patch:  0 => 1


Comment:

 Here's a [https://github.com/django/django/pull/7709 PR] solving the
 pending trigger events issue by checking deferred foreign key constraints
 before deleting them.

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

Re: [Django] #25492: warn about migrations mixing schema- and data- changing operations

[Django]

#25492: warn about migrations mixing schema- and data- changing operations
--+
 Reporter:  Joey Wilhelm  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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 Simon Charette):

 I just wanted to mention that wrapping your migration operations with `SET
 CONSTRAINTS ALL IMMEDIATE` solves the `pending trigger events` message.

 {{{#!python
 operations = [
 migrations.RunSQL('SET CONSTRAINTS ALL IMMEDIATE', 'SET CONSTRAINTS
 ALL DEFERRED'),
 migrations.AlterField(
 model_name='charity',
 name='name_legal',
 field=models.CharField(max_length=255, default='',
 verbose_name='legal name'),
 preserve_default=False,
 ),
 migrations.RunSQL('SET CONSTRAINTS ALL DEFERRED', 'SET CONSTRAINTS ALL
 IMMEDIATE'),
 ]
 }}}

 Maybe this is something that could be done automatically by Django in
 `AlterField` when it knows it has to perform both a data and structural
 update?

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

Re: [Django] #26478: Template Context should validate names

[Django]

#26478: Template Context should validate names
-+--
 Reporter:  Stephen Kelly|Owner:  Tim Martin
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.9
 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 Tim Martin):

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

Re: [Django] #24182: Document or improve limitations for doing queries in field defaults

[Django]

#24182: Document or improve limitations for doing queries in field defaults
-+
 Reporter:  arveitch |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  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 Simon Charette):

 Replying to [comment:7 arveitch]:
 > I've just tried this code in Django 1.8.2 and it now works as expected.
 >
 > Looks like this bug has been solved sometime between 1.7.3 and 1.8.2

 I confirm this is still an issue on 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.48ec447b265aa1581c338668bb786b9a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27392: Remove "Tests that", "Ensures that", etc. from test docstings

[Django]

#27392: Remove "Tests that", "Ensures that", etc. from test docstings
--+
 Reporter:  Tim Graham|Owner:  za
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 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 Tim Graham):

 For the "Tests adding" case, I'd just chop "Test". It's okay to make a
 work-in-progress 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/067.f8904dd62c7b66b1b28f7b6399087644%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27606: Error in formatting HttpResponseRedirect when __init__() raises DisallowedHost

[Django]

#27606: Error in formatting HttpResponseRedirect when __init__() raises
DisallowedHost
-+-
 Reporter:  Jerome Leclanche |Owner:  Jerome
 |  Leclanche
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * needs_tests:  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/062.70e8ac49b1f61c129e3bcaa18f1a9a36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27606: Error in formatting HttpResponseRedirect when __init__() raises DisallowedHost

[Django]

#27606: Error in formatting HttpResponseRedirect when __init__() raises
DisallowedHost
-+-
 Reporter:  Jerome Leclanche |Owner:  Jerome
 |  Leclanche
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.10
 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 Jerome Leclanche):

 https://github.com/django/django/pull/7708

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

Re: [Django] #27606: Error in formatting HttpResponseRedirect when __init__() raises DisallowedHost

[Django]

#27606: Error in formatting HttpResponseRedirect when __init__() raises
DisallowedHost
-+-
 Reporter:  Jerome Leclanche |Owner:  Jerome
 |  Leclanche
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.10
 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
-+-
Changes (by Jerome Leclanche):

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

Re: [Django] #25484: static template tag outputs invalid HTML if storage class's url() returns a URI with '&' characters.

[Django]

#25484: static template tag outputs invalid HTML if storage class's url() 
returns a
URI with '&' characters.
-+
 Reporter:  João Miguel Neves|Owner:  alix-
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 ):

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


Comment:

 In [changeset:"374e6230ca9f9bb84cc9dd760dfb6395fbb5ff0f" 374e623]:
 {{{
 #!CommitTicketReference repository=""
 revision="374e6230ca9f9bb84cc9dd760dfb6395fbb5ff0f"
 Fixed #25484 -- Made {% static %} render escaped URLs.
 }}}

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

Re: [Django] #16859: CSRF Improvements

[Django]

#16859: CSRF Improvements
-+-
 Reporter:  Paul McMillan|Owner:  Paul
 Type:   |  McMillan
  Cleanup/optimization   |   Status:  new
Component:  CSRF |  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:"33e86b3488dbf29f5aeb38cf0ee6597190d33c59" 33e86b34]:
 {{{
 #!CommitTicketReference repository=""
 revision="33e86b3488dbf29f5aeb38cf0ee6597190d33c59"
 Refs #16859 -- Disabled CSRF_COOKIE_* checks when using CSRF_USE_SESSIONS.
 }}}

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

Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

[Django]

#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by Tim Graham ):

 In [changeset:"e1f93e2b1e0da8cdacbb63167bab8732ffbab872" e1f93e2b]:
 {{{
 #!CommitTicketReference repository=""
 revision="e1f93e2b1e0da8cdacbb63167bab8732ffbab872"
 [1.10.x] Refs #25550 -- Removed a deprecated reverse assignment example in
 docs.

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

Re: [Django] #25550: Deprecate direct assignment to the reverse side of a related set

[Django]

#25550: Deprecate direct assignment to the reverse side of a related set
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (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
-+-

Comment (by Tim Graham ):

 In [changeset:"8dac9890a5941e7b59ea0ebebed400965941fe09" 8dac9890]:
 {{{
 #!CommitTicketReference repository=""
 revision="8dac9890a5941e7b59ea0ebebed400965941fe09"
 Refs #25550 -- Removed a deprecated reverse assignment example in docs.
 }}}

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

Re: [Django] #27613: BaseInlineFormSet is validating form for extra forms

[Django]

#27613: BaseInlineFormSet is validating form for extra forms
+--
 Reporter:  Sonu kumar  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.10
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  FormSet | 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:

 The foreign key widget would need to send "-1" on a form submission so
 that the field
 
[https://github.com/django/django/blob/af5983e4f5e8e9737bc6c7c38221b3e7c9914d1a/django/forms/fields.py#L186-L205
 doesn't appear to change]. Since the field appears to change, Django
 validates the form.

 You'll likely need to use a custom widget or a different method to
 accomplish your use case. I don't think it's a bug in Django, but if you
 want to propose some change that fixes the issue for you, feel free to
 reopen with a 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/065.fe40befbba3c9479d1e9ce2fbafd3439%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27613: BaseInlineFormSet is validating form for extra forms

[Django]

#27613: BaseInlineFormSet is validating form for extra forms
+--
 Reporter:  Sonu kumar  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  FormSet | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Sonu kumar):

 Hmm, It's not happening if you remove default=-1, but do you know any
 reason for 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.7a34050979f236aa662db822f5bb39cb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27613: BaseInlineFormSet is validating form for extra forms

[Django]

#27613: BaseInlineFormSet is validating form for extra forms
+--
 Reporter:  Sonu kumar  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  FormSet | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Tim Graham):

 Does it happen if you remove `default=-1`? That looks unusual. Can you
 explain the use case?

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

Re: [Django] #27606: Error in formatting HttpResponseRedirect when __init__() raises DisallowedHost

[Django]

#27606: Error in formatting HttpResponseRedirect when __init__() raises
DisallowedHost
--+
 Reporter:  Jerome Leclanche  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  HTTP handling |  Version:  1.10
 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 Tim Graham):

 Yes.

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

Re: [Django] #27606: Error in formatting HttpResponseRedirect when __init__() raises DisallowedHost

[Django]

#27606: Error in formatting HttpResponseRedirect when __init__() raises
DisallowedHost
--+
 Reporter:  Jerome Leclanche  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  HTTP handling |  Version:  1.10
 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 tundebabzy):

 Replying to [comment:6 Tim Graham]:
 > I think it would be fine.
 Do you mean it would be fine to call super before raising the exception?

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

Re: [Django] #27613: BaseInlineFormSet is validating form for extra forms

[Django]

#27613: BaseInlineFormSet is validating form for extra forms
+--
 Reporter:  Sonu kumar  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  FormSet | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Sonu kumar):

 Hi Tim,
 I have found root caused this is happen only when you add following code
 snippet to Explanation model.
 {{{
 past_explanation = models.ForeignKey('self', on_delete=models.CASCADE,
  db_constraint=False, blank=True,
  default=-1, null=True)
 }}}

 I think this is a bug since, from the model  and admin configuration we
 can see that user should be able to add Question without any explanation,
 but it's not allowing to do so.

 You can find code at GitHub repo https://github.com/sonus21/Django_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.67b8070ddcbb9841a8b32a8c364276cd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27613: BaseInlineFormSet is validating form for extra forms

[Django]

#27613: BaseInlineFormSet is validating form for extra forms
+--
 Reporter:  Sonu kumar  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.10
 Severity:  Normal  |   Resolution:
 Keywords:  FormSet | 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):

 * severity:  Release blocker => Normal
 * easy:  1 => 0


Comment:

 Could you try to simplify your example code so that it only contains the
 minimum code needed to reproduce the issue as well as an explanation of
 why Django appears to be at fault?

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