Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.10
 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 Ramin Farajpour Cami):

 Yes, Collin, waiting of response Tim ,

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

[Django] #27347: Contributing docs: Patch vs Pull-Request

[Django]

#27347: Contributing docs: Patch vs Pull-Request
+
 Reporter:  Thomas Güttler  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I don't understand why this approach gets used in the contributing docs:

git clone https://github.com/django/django.git
...
pip install -e /path/to/your/local/clone/django/
...
git diff > 24788.diff

 See https://docs.djangoproject.com/en/1.10/intro/contributing/

 I guess you prefer pull requests, since they are easier to handle.

 Why not take this approach?

   fork django to personal github account via github web gui
   ...
   pip install -e
 git+https://github.com/mygithubnickname/django.git#egg=django
   ...
   create pull request.

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

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

[Django] #27348: Typo in docs for modify_settings

[Django]

#27348: Typo in docs for modify_settings
+
 Reporter:  Thomas Güttler  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Uncategorized   |Version:  1.10
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 
https://docs.djangoproject.com/en/1.10/topics/testing/tools/#django.test.modify_settings

 wrong: `@modify_settings(MIDDLEWARE=...`

 correct `@modify_settings(MIDDLEWARE_CLASSES=...`

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

[Django] #27349: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW

[Django]

#27349: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW
---+
 Reporter:  David D Lowe   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.10
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 Have a look at the section "Customizing error views" in this documentation
 page:

 https://docs.djangoproject.com/en/1.10/topics/http/views/#customizing-
 error-views

 It does not mention the highly relevant CSRF_FAILURE_VIEW setting. I think
 it should.

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

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

Re: [Django] #27349: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW

[Django]

#27349: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW
---+--
 Reporter:  David D Lowe   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by David D Lowe):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I created a pull request, fixing this issue:

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

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

Re: [Django] #27349: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW

[Django]

#27349: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW
---+--
 Reporter:  David D Lowe   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.10
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by David D Lowe):

 * has_patch:  0 => 1


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

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

Re: [Django] #27347: Contributing docs: Patch vs Pull-Request

[Django]

#27347: Contributing docs: Patch vs Pull-Request
-+-
 Reporter:  Thomas Güttler   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 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
 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Duplicate of #26708.

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

Re: [Django] #27348: Typo in docs for modify_settings

[Django]

#27348: Typo in docs for modify_settings
+--
 Reporter:  Thomas Güttler  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Documentation   |  Version:  1.10
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Tim Graham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * component:  Uncategorized => Documentation
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug


Comment:

 `settings.MIDDLEWARE` is new in Django 1.10 and supersedes the deprecated
 `MIDDLEWARE_CLASSES` setting.

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

Re: [Django] #27347: Contributing docs: Patch vs Pull-Request

[Django]

#27347: Contributing docs: Patch vs Pull-Request
-+-
 Reporter:  Thomas Güttler   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 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
-+-

Comment (by Thomas Güttler):

 Thank you Graham. I guess only few people have the overview like you have.
 (and: sorry, I have not seen that this has been reported before).

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

Re: [Django] #19705: CommonMiddleware handles If-None-Match incorrectly

[Django]

#19705: CommonMiddleware handles If-None-Match incorrectly
-+-
 Reporter:  Aymeric Augustin |Owner:  Denis
 |  Cornehl
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  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
-+-

Comment (by Tim Graham ):

 In [changeset:"9eb49af821546af1cae8f3a91aefea4b99a6478f" 9eb49af8]:
 {{{
 #!CommitTicketReference repository=""
 revision="9eb49af821546af1cae8f3a91aefea4b99a6478f"
 Refs #19705 -- Documented decorator ordering with @condition().
 }}}

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

Re: [Django] #19705: CommonMiddleware handles If-None-Match incorrectly

[Django]

#19705: CommonMiddleware handles If-None-Match incorrectly
-+-
 Reporter:  Aymeric Augustin |Owner:  Denis
 |  Cornehl
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  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
-+-

Comment (by Tim Graham ):

 In [changeset:"404587078112295d961939ae76b49ab22da3c79c" 40458707]:
 {{{
 #!CommitTicketReference repository=""
 revision="404587078112295d961939ae76b49ab22da3c79c"
 [1.10.x] Refs #19705 -- Documented decorator ordering with @condition().

 Backport of 9eb49af821546af1cae8f3a91aefea4b99a6478f 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.2f06d437b5360feaa69be34e656bbb17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19705: CommonMiddleware handles If-None-Match incorrectly

[Django]

#19705: CommonMiddleware handles If-None-Match incorrectly
-+-
 Reporter:  Aymeric Augustin |Owner:  Denis
 |  Cornehl
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  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
-+-

Comment (by Tim Graham ):

 In [changeset:"9108696a7553123f57c5d42f9c4a90cad44532f4" 9108696]:
 {{{
 #!CommitTicketReference repository=""
 revision="9108696a7553123f57c5d42f9c4a90cad44532f4"
 Refs #19705 -- Changed gzip modification times to 0.

 This makes gzip output deterministic, which allows
 ConditionalGetMiddleware to reliably compare ETags on gzipped
 content (views using the gzip_page() decorator in particular).
 }}}

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

Re: [Django] #27345: Stop setting the Date header in ConditionalGetMiddleware

[Django]

#27345: Stop setting the Date header in ConditionalGetMiddleware
-+-
 Reporter:  Kevin Christopher|Owner:  nobody
  Henry  |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Seems okay to me. [https://github.com/django/django/pull/7392 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.d4cd9cbf7648f43ec19ae64a7f524637%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27349: Docs: "Customizing error views" does not mention CSRF_FAILURE_VIEW (was: Docs: "Costomizing error views" does not mention CSRF_FAILURE_VIEW)

[Django]

#27349: Docs: "Customizing error views" does not mention CSRF_FAILURE_VIEW
--+
 Reporter:  David D Lowe  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

Re: [Django] #27344: ConditionalGetMiddleware should not operate on unsafe requests

[Django]

#27344: ConditionalGetMiddleware should not operate on unsafe requests
-+-
 Reporter:  Kevin Christopher|Owner:  Kevin
  Henry  |  Christopher Henry
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  1.10
 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):

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

Re: [Django] #27346: Stop setting the Content-Length header in ConditionalGetMiddleware

[Django]

#27346: Stop setting the Content-Length header in ConditionalGetMiddleware
-+-
 Reporter:  Kevin Christopher|Owner:  nobody
  Henry  |
 Type:   |   Status:  new
  Cleanup/optimization   |
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 Tim Graham):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 It was [https://github.com/django/django/pull/6798#issuecomment-227557147
 discussed briefly] when adding `Content-Length` to `CommonMiddleware`. We
 didn't see much advantage to removing it at the time as
 `ConditionalGetMiddleware` might be used without `CommonMiddleware`. I
 don't have a strong feeling about it though.

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

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ramin Farajpour Cami):

 * Attachment "session.diff" 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/065.250bab19d5a93dcfd7997c77d71d65a2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ramin Farajpour Cami):

 * has_patch:  0 => 1


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

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

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  HTTP handling => contrib.sessions
 * needs_tests:  0 => 1


Comment:

 I wish I understood the use case better. Anyway, a test is also needed and
 there's a syntax error (double "if") in the patch. Pull requests are
 preferred if you can provide that.

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

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Collin Anderson):

 This change is growing on me. It does seem a hair more beginner friendly.
 I also wish I understood the use case better. Ramin: how is the current
 behavior problematic? Why is this an issue? What's so bad about the `Set-
 Cookie` header in this 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.23275a241cfe1d7c772998da1b86fadc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ramin Farajpour Cami):

 Replying to [comment:20 Collin Anderson]:
 > This change is growing on me. It does seem a hair more beginner
 friendly. I also wish I understood the use case better. Ramin: how is the
 current behavior problematic? Why is this an issue? What's so bad about
 the `Set-Cookie` header in this case?

 I said above, there isn't problem but sessionid is empty any checked, you
 think current behavior is good, close this ticket,

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

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ramin Farajpour Cami):

 PR -> https://github.com/django/django/pull/7394

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

Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

[Django]

#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:  Bug  |   Status:  new
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_tests:  1 => 0


Comment:

 What's still missing for me is a description of your use case at a high
 level. What task are you trying to accomplish in your project? Give a
 sample view or something that demonstrates why this change is useful.

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

Re: [Django] #6363: Login page is redisplayed without any message if AdminSite.has_permission() returns False (was: Bug with has_permission method of AdminSite class.)

[Django]

#6363: Login page is redisplayed without any message if 
AdminSite.has_permission()
returns False
-+-
 Reporter:  Michel Sabchuk   |Owner:  Iacopo
 |  Spalletti
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * keywords:  nfa-someday =>
 * version:  newforms-admin => master


Comment:

 This may be addressed by #25163 which added this message to the login page
 if `AdminSite.has_permission()` returns `False`:
  You are authenticated as , but are not authorized to access
 this page. Would you like to login to a different account?

 I haven't checked if the previously proposed patches might be a further
 improvement.

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

Re: [Django] #27346: Stop setting the Content-Length header in ConditionalGetMiddleware

[Django]

#27346: Stop setting the Content-Length header in ConditionalGetMiddleware
-+-
 Reporter:  Kevin Christopher|Owner:  Aleksandr
  Henry  |  Sobolev
 Type:   |   Status:  assigned
  Cleanup/optimization   |
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 Aleksandr Sobolev):

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

[Django] #27350: Attaching signals to abstract models don't work as it used to be

[Django]

#27350: Attaching signals to abstract models don't work as it used to be
--+
 Reporter:  thoas |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi,

 I'm currently porting an application from Django 1.9.x to 1.10.x, we are
 relying on managers to attach signals to allow developers overriding them
 in our generic applications, this does not work anymore.

 A complete example:


 {{{
 from django.db import models
 from django.db.models import signals


 class Poll(models.Model):
 question = models.CharField(max_length=255)
 answers_count = models.PositiveIntegerField(default=0)


 class AnswerManager(models.Manager):
 def contribute_to_class(self, cls, name):
 signals.post_save.connect(self.post_save, sender=cls)

 return super(AnswerManager, self).contribute_to_class(cls, name)

 def post_save(self, instance, **kwargs):
 poll = instance.poll
 poll.answers_count = poll.answers.count()
 poll.save(update_fields=('answers_count', ))


 class AbstractAnswer(models.Model):
 text = models.CharField(max_length=255)
 poll = models.ForeignKey(Poll, related_name='answers')

 objects = AnswerManager()

 class Meta:
 abstract = True


 class Answer(AbstractAnswer):
 class Meta:
 abstract = False


 class ModelsTests(TestCase):
 def test_simple_compute(self):
 poll = Poll.objects.create(question='Weird?')

 Answer.objects.create(poll=poll, text='Yes')

 # refresh
 poll = Poll.objects.get(pk=poll.pk)

 # still 0 on Django 1.10 and 1 on Django 1.9
 assert poll.answers_count == 1
 }}}


 The complete application is available [[https://github.com/thoas/django-
 signals-wtf|here]] and travis is available [[https://travis-ci.org/thoas
 /django-signals-wtf/builds/167669153|here]] to test again both 1.10 and
 1.9.

 Is this some kind of undocumented new behavior or a 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/048.8df3e5cb195ff8c952055b6a15facdad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27341: Altering max_length on sqlite: makemigrations creates correct migration, but migrate does not alter length of varchar in the database itself (was: Altering max_length on sqlite: m

[Django]

#27341: Altering max_length on sqlite: makemigrations creates correct migration,
but migrate does not alter length of varchar in the database itself
+--
 Reporter:  Gerben Morsink  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  worksforme
 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:   => worksforme


Comment:

 Regardless of my last comment, I see a change from  `varchar(200)` to
 `varchar(201)` in the "SQLite Database Browser" program after changing the
 length of `CharField` and running the migration. Please reopen if you can
 provide steps on how to reproduce.

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

Re: [Django] #27350: Attaching signals to abstract models don't work as it used to be

[Django]

#27350: Attaching signals to abstract models don't work as it used to be
-+-
 Reporter:  Florent Messa|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Hi, you should
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#bisecting-a-regression bisect] to find the commit where the
 behavior changed. If I had to guess it might be
 ed0ff913c648b16c4471fc9a9441d1ee48cb5420 or
 3a47d42fa33012b2156bf04058d933df6b3082d2.

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

Re: [Django] #27350: Attaching signals to abstract models don't work as it used to be

[Django]

#27350: Attaching signals to abstract models don't work as it used to be
-+-
 Reporter:  Florent Messa|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 Florent Messa):

 Replying to [comment:1 Tim Graham]:
 > Hi, you should
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#bisecting-a-regression bisect] to find the commit where the
 behavior changed. If I had to guess it might be
 ed0ff913c648b16c4471fc9a9441d1ee48cb5420 or
 3a47d42fa33012b2156bf04058d933df6b3082d2.

 It was introduced by 3a47d42fa33012b2156bf04058d933df6b3082d2

 Build is available on [[https://travis-ci.org/thoas/django-signals-
 wtf/builds/167683086|travis]], **110a** is the parent commit of
 3a47d42fa33012b2156bf04058d933df6b3082d2 and **110b** is located at
 3a47d42fa33012b2156bf04058d933df6b3082d2

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

Re: [Django] #27350: Attaching signals to abstract models don't work as it used to be

[Django]

#27350: Attaching signals to abstract models don't work as it used to be
-+-
 Reporter:  Florent Messa|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * cc: Loic Bistuer (added)


Comment:

 Looking at your code, I don't think we broke any public APIs, so I'd say
 it's up to you to investigate and say why it's a bug and to propose a fix.
 Maybe Loic can advise without too much effort.

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

Re: [Django] #27350: Attaching signals to abstract models don't work as it used to be

[Django]

#27350: Attaching signals to abstract models don't work as it used to be
-+-
 Reporter:  Florent Messa|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 Florent Messa):

 Replying to [comment:3 Tim Graham]:
 > Looking at your code, I don't think we broke any public APIs, so I'd say
 it's up to you to investigate and say why it's a bug and to propose a fix.
 Maybe Loic can advise without too much effort.

 The **contribute_to_class** is called twice in 1.9.x on the abstract level
 and child.

 That's not the case on 1.10.x your child model needs to declare explicitly
 the manager even if it's inherited.

 I can update my code on my side on every child to redeclare the manager,
 as you have said it's not a public API as it's not documented. I can
 investigate more on my side and provide a fix for that but will you
 consider it?

 Btw, thank you for you reactivity ;)

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

Re: [Django] #26352: models.E003 check incorrectly prevents duplicate ManyToMany through-self that differ by through_fields

[Django]

#26352: models.E003 check incorrectly prevents duplicate ManyToMany through-self
that differ by through_fields
--+
 Reporter:  Simon Willison|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (System checks)  |  Version:  1.9
 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
 * component:  Database layer (models, ORM) => Core (System checks)
 * stage:  Unreviewed => Accepted


Comment:

 Does the original pull request solve it? If so, feel free to update and
 resend it.

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

Re: [Django] #27350: Attaching signals to abstract models don't work as it used to be

[Django]

#27350: Attaching signals to abstract models don't work as it used to be
-+-
 Reporter:  Florent Messa|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 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 Tim Graham):

 I didn't follow the manager changes closely enough to say what the
 expected behavior is.

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

Re: [Django] #16682: KeyboardInterrupt not handled properly in transaction aborting

[Django]

#16682: KeyboardInterrupt not handled properly in transaction aborting
-+-
 Reporter:  Malcolm Tredinnick   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  1.11 | 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):

 * keywords:   => 1.11
 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * stage:  Ready for checkin => Accepted


Comment:

 Reopening as the test hangs on the last line when I run it on Oracle
 (using the Oracle DB Developer VM). I haven't seen any problems with it on
 Jenkins. Can anyone else reproduce that and/or have an idea about the
 cause?

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

Re: [Django] #27345: Stop setting the Date header in ConditionalGetMiddleware

[Django]

#27345: Stop setting the Date header in ConditionalGetMiddleware
-+-
 Reporter:  Kevin Christopher|Owner:  nobody
  Henry  |
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"61f9243e5138b79f2671936b4f55941cd02da89e" 61f9243]:
 {{{
 #!CommitTicketReference repository=""
 revision="61f9243e5138b79f2671936b4f55941cd02da89e"
 Fixed #27345 -- Stopped setting the Date header in
 ConditionalGetMiddleware.
 }}}

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

Re: [Django] #27349: Docs: "Customizing error views" does not mention CSRF_FAILURE_VIEW

[Django]

#27349: Docs: "Customizing error views" does not mention CSRF_FAILURE_VIEW
--+
 Reporter:  David D Lowe  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"223393a9e3d5131e1701b05df4b995d2774902b3" 223393a]:
 {{{
 #!CommitTicketReference repository=""
 revision="223393a9e3d5131e1701b05df4b995d2774902b3"
 [1.10.x] Fixed #27349 -- Doc'd the CSRF_FAILURE_VIEW setting in view topic
 guide.

 Backport of 424187ec4be73a36d5430901382a27c8523f446a from master
 }}}

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

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

Re: [Django] #27349: Docs: "Customizing error views" does not mention CSRF_FAILURE_VIEW

[Django]

#27349: Docs: "Customizing error views" does not mention CSRF_FAILURE_VIEW
--+
 Reporter:  David D Lowe  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"424187ec4be73a36d5430901382a27c8523f446a" 424187ec]:
 {{{
 #!CommitTicketReference repository=""
 revision="424187ec4be73a36d5430901382a27c8523f446a"
 Fixed #27349 -- Doc'd the CSRF_FAILURE_VIEW setting in view topic guide.
 }}}

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

Re: [Django] #27324: Simplify get_constraints on Oracle

[Django]

#27324: Simplify get_constraints on Oracle
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  oracle   | 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"5a772a0b7bf71128287396d310ddd3db13625a1f" 5a772a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a772a0b7bf71128287396d310ddd3db13625a1f"
 Fixed #27324 -- Simplified DatabaseIntrospection.get_constraints() on
 Oracle.
 }}}

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

Re: [Django] #25751: Translation of strings in a javascript file: Docs seem to be incorrect

[Django]

#25751: Translation of strings in a javascript file: Docs seem to be incorrect
-+-
 Reporter:  George Tantiras  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  javascript   | Triage Stage:  Accepted
  translation|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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

Re: [Django] #20888: Allow defining order of column for indexes

[Django]

#20888: Allow defining order of column for indexes
-+-
 Reporter:  anonymous|Owner:  Akshesh
 |  Doshi
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index, order, db-| Triage Stage:  Accepted
  indexes 1.11   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by François Freitag):

 * has_patch:  0 => 1


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

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