date:20160602

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-02 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dbshell  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by phildini):

 Should a test be added to account for the case where 'NAME' == 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/069.8019c8e075a625963dd0a40fa774c2a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

2016-06-02 Thread Django

#2: assertRedirects gives unhelpful error message expected URL is external
-+-
 Reporter:  inglesp  |Owner:
 Type:   |  tobiasmcnulty
  Cleanup/optimization   |   Status:  new
Component:  Testing framework|  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 Markus Holtermann ):

 In [changeset:"78a0ca67f6dfb6c74dcabe36aa460c4eb5cfe7ae" 78a0ca6]:
 {{{
 #!CommitTicketReference repository=""
 revision="78a0ca67f6dfb6c74dcabe36aa460c4eb5cfe7ae"
 Refs #2 -- Fixed test failures caused by assertRedirects changes
 (#6701)
 }}}

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

Re: [Django] #10107: Allow mark_safe() to be used as a decorator

2016-06-02 Thread Django

#10107: Allow mark_safe() to be used as a decorator
-+
 Reporter:  matehat  |Owner:  svvitale
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  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
-+
Changes (by svvitale):

 * owner:  susan => svvitale


Comment:

 Talked to susan at Pycon 2016 and created a new PR to incorporate the
 comments from her original work.  New PR here:
 https://github.com/django/django/pull/6706

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

Re: [Django] #22288: F() expression not compatible with __range field look up

2016-06-02 Thread Django

#22288: F() expression not compatible with __range field look up
-+-
 Reporter:  liushaohua86@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by MatthewWilkes):

 I have updated the PR at https://github.com/django/django/pull/6216 - I
 believe this is in a good state but will need re-reviewing by ORM experts.

 Is this something that should be against 1.10 or 1.11 at this stage?

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

Re: [Django] #15250: Cannot fill parent model instance in cache

2016-06-02 Thread Django

#15250: Cannot fill parent model instance in cache
-+-
 Reporter:  vzima|Owner:  czpython
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/6704 PR] with some comments for
 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/063.efb4ec21556ab4b39e35c81a70885529%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17209: Dogfood class-based views in contrib.auth

2016-06-02 Thread Django

#17209: Dogfood class-based views in contrib.auth
-+-
 Reporter:  melinath |Owner:  auvipy
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  class-based views| Triage Stage:  Accepted
  admin auth |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by phildini):

 * needs_better_patch:  0 => 1


Comment:

 I think the code looks good, and includes appropriate test changes.
 However, the patch needs to be rebased, and the references to 1.10 should
 be set to the next version.

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

Re: [Django] #15250: Cannot fill parent model instance in cache

2016-06-02 Thread Django

#15250: Cannot fill parent model instance in cache
-+-
 Reporter:  vzima|Owner:  czpython
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 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 czpython):

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

Re: [Django] #16043: Specialization cache should be filled/shared with parent object cache (multitable inheritance)

2016-06-02 Thread Django

#16043: Specialization cache should be filled/shared with parent object cache
(multitable inheritance)
-+-
 Reporter:  zimnyx   |Owner:  czpython
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by czpython):

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

Re: [Django] #26586: makemigrations does not detect custom field subclassing change

2016-06-02 Thread Django

#26586: makemigrations does not detect custom field subclassing change
-+-
 Reporter:  tuffnatty|Owner:  baylee
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  migrations, custom   | Triage Stage:  Accepted
  fields |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 For future reference, it would probably be fine to reclassify this ticket
 as a documentation issue, but since you've already created another issue,
 I'll close 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/067.4eba98d29ba6560bdebf7825c2ca1988%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26628: Log CSRF failures to django.security by default.

2016-06-02 Thread Django

#26628: Log CSRF failures to django.security by default.
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"697ed75de5197a2175247464e1eee14fcf38562f" 697ed75]:
 {{{
 #!CommitTicketReference repository=""
 revision="697ed75de5197a2175247464e1eee14fcf38562f"
 [1.10.x] Refs #26628 -- Documented CSRF failure logging.

 Backport of ff9198ee0f1de24a5b2861d28849344e7a5714c4 from master
 }}}

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

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

Re: [Django] #26628: Log CSRF failures to django.security by default.

2016-06-02 Thread Django

#26628: Log CSRF failures to django.security by default.
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"cbc8ef6127a92cc59dfb28461e865242e5e39329" cbc8ef61]:
 {{{
 #!CommitTicketReference repository=""
 revision="cbc8ef6127a92cc59dfb28461e865242e5e39329"
 [1.9.x] Refs #26628 -- Documented CSRF failure logging.

 Backport of ff9198ee0f1de24a5b2861d28849344e7a5714c4 from master
 }}}

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

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

Re: [Django] #26628: Log CSRF failures to django.security by default.

2016-06-02 Thread Django

#26628: Log CSRF failures to django.security by default.
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"ff9198ee0f1de24a5b2861d28849344e7a5714c4" ff9198e]:
 {{{
 #!CommitTicketReference repository=""
 revision="ff9198ee0f1de24a5b2861d28849344e7a5714c4"
 Refs #26628 -- Documented CSRF failure logging.
 }}}

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

Re: [Django] #26700: 1.10 release notes missing information on TEMPLATES setting

2016-06-02 Thread Django

#26700: 1.10 release notes missing information on TEMPLATES setting
--+
 Reporter:  jrabbit   |Owner:  jrabbit
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:  templates, settings   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"83ea51a2441ac497e4d94269bf2746409bf4cfd0" 83ea51a2]:
 {{{
 #!CommitTicketReference repository=""
 revision="83ea51a2441ac497e4d94269bf2746409bf4cfd0"
 [1.10.x] Fixes #26700 -- Added how to upgrade to TEMPLATES link in 1.10
 release notes.

 Backport of d65e2899b2b25c62a4ead7aba121421c19e55bce from master
 }}}

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

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

Re: [Django] #26700: 1.10 release notes missing information on TEMPLATES setting

2016-06-02 Thread Django

#26700: 1.10 release notes missing information on TEMPLATES setting
--+
 Reporter:  jrabbit   |Owner:  jrabbit
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:  fixed
 Keywords:  templates, settings   | 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:"d65e2899b2b25c62a4ead7aba121421c19e55bce" d65e289]:
 {{{
 #!CommitTicketReference repository=""
 revision="d65e2899b2b25c62a4ead7aba121421c19e55bce"
 Fixes #26700 -- Added how to upgrade to TEMPLATES link in 1.10 release
 notes.
 }}}

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

Re: [Django] #26702: Document custom field subclass change requires new custom field class

2016-06-02 Thread Django

#26702: Document custom field subclass change requires new custom field class
--+
 Reporter:  baylee|Owner:  baylee
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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 timgraham):

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

Re: [Django] #21523: Models DateField to_python method no longer supports mock dates.

2016-06-02 Thread Django

#21523: Models DateField to_python method no longer supports mock dates.
-+-
 Reporter:  hugo@…   |Owner:  akki
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 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 phildini):

 * stage:  Accepted => Ready for checkin


Comment:

 The patch looks good, is documented, and has tests.

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
-+-
 Reporter:  aaugustin|Owner:  bjcubsfan
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 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 carljm):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-06-02 Thread Django

#26526: Document QuerySet.latest() behavior for null values
--+
 Reporter:  int-ua|Owner:  g3rd
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e6c5e68acd4bff90e371fd148ed6976e147692ad" e6c5e68a]:
 {{{
 #!CommitTicketReference repository=""
 revision="e6c5e68acd4bff90e371fd148ed6976e147692ad"
 Fixed #26526 -- Documented QuerySet.latest()'s dependency on database
 ordering.
 }}}

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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-06-02 Thread Django

#26526: Document QuerySet.latest() behavior for null values
--+
 Reporter:  int-ua|Owner:  g3rd
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"cd4246aab1740d77fa6ebd66c7d2053634501598" cd4246aa]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd4246aab1740d77fa6ebd66c7d2053634501598"
 [1.10.x] Fixed #26526 -- Documented QuerySet.latest()'s dependency on
 database ordering.

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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-06-02 Thread Django

#26526: Document QuerySet.latest() behavior for null values
--+
 Reporter:  int-ua|Owner:  g3rd
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  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:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"9d52cdfbbc02a21fafc74146c571ac6e50812a00" 9d52cdfb]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d52cdfbbc02a21fafc74146c571ac6e50812a00"
 [1.9.x] Fixed #26526 -- Documented QuerySet.latest()'s dependency on
 database ordering.

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+-
 Reporter:  aaugustin  |Owner:  bjcubsfan
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 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 bjcubsfan):

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

Re: [Django] #26701: Improve link to issue tracker in the contributor guide

2016-06-02 Thread Django

#26701: Improve link to issue tracker in the contributor guide
--+
 Reporter:  shaunagm  |Owner:  shaunagm
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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 shaunagm):

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

Re: [Django] #26700: 1.10 release notes missing information on TEMPLATES setting

2016-06-02 Thread Django

#26700: 1.10 release notes missing information on TEMPLATES setting
--+
 Reporter:  jrabbit   |Owner:  jrabbit
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:  templates, settings   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

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

Re: [Django] #26702: Document custom field subclass change requires new custom field class

2016-06-02 Thread Django

#26702: Document custom field subclass change requires new custom field class
-+-
 Reporter:  baylee   |Owner:  baylee
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 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 baylee):

 * status:  new => assigned
 * needs_docs:   => 0
 * owner:  nobody => baylee
 * needs_tests:   => 0
 * needs_better_patch:   => 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/064.212c9763633f3c604871b81c1a60697d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26586: makemigrations does not detect custom field subclassing change

2016-06-02 Thread Django

Comment (by baylee):

After discussion with Markus at PyCon sprints 2016:

This isn't possible. The closest we get is

[https://github.com/django/django/blob/master/django/db/migrations/autodetector.py#L879
here], where we could add a check for `get_internal_type()` of the two
fields. But that won't work because the old state and new state are
dynamically generated from the field definition in the migration files.
The only way to handle this would be if we saved internal type as part of
the migrations.

Propose closing this in favor of adding documentation in #26702

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

[Django] #26702: Document custom field subclass change requires new custom field class

2016-06-02 Thread Django

#26702: Document custom field subclass change requires new custom field class
--+
 Reporter:  baylee|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Related to #26586

 Can't alter a custom field to have a different base field type.
 Documentation should be updated to reflect this and proposed solution.

 Example before state:
 {{{
 class CustomCharField(models.CharField):
 def foo(self):
 pass

 class Author(models.Model):
 name = CustomCharField(max_length=255)
 }}}

 Example of what won't work:
 {{{
 class CustomCharField(models.TextField):
 def foo(self):
 pass

 class Author(models.Model):
 name = CustomCharField(max_length=255)
 }}}

 Example of what you should change to:
 {{{
 class CustomFieldMixin(object):
 def foo(self):
 pass

 class CustomCharField(CustomFieldMixin, models.CharField):
 pass

 class CustomTextField(CustomFieldMixin, models.TextField):
 pass

 class Author(models.Model):
 name = CustomTextField(max_length=255)
 }}}

 Should also include link to:
 https://docs.djangoproject.com/en/1.9/topics/migrations/#considerations-
 when-removing-model-fields to explain why user must keep old field
 definition around.

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

Re: [Django] #26604: Add example of simple multiple file upload in documentation

2016-06-02 Thread Django

#26604: Add example of simple multiple file upload in documentation
-+-
 Reporter:  zxcq544  |Owner:
 |  berkerpeksag
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  doumentation,| Triage Stage:  Accepted
  multiple file upload, upload many  |
  files  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by berkerpeksag):

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+-
 Reporter:  aaugustin  |Owner:  bjcubsfan
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  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 carljm):

 * needs_better_patch:  0 => 1


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

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

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

2016-06-02 Thread Django

#2: assertRedirects gives unhelpful error message expected URL is external
-+-
 Reporter:  inglesp  |Owner:
 Type:   |  tobiasmcnulty
  Cleanup/optimization   |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  closed => new
 * has_patch:  1 => 0
 * version:  1.9 => master
 * resolution:  fixed =>


Comment:

 Tobias is working on fixing the test failures that the patched introduced.

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

Re: [Django] #12666: Setting for sending email using localtime instead of UTC

2016-06-02 Thread Django

Comment (by carljm):

I'm not convinced of the value of the refactoring proposed in
https://code.djangoproject.com/ticket/12666#comment:9 -- if someone really
wants some strange handling for the Date header, they can just set the
header themselves, which is likely easier than subclassing `Email` for
this purpose. Exposing the stdlib's `localtime` boolean flag is a simple
change which would be friendlier to those who want a local timezone in
their email headers, especially if it actually does respect the currently
active Django timezone (e.g. `TIME_ZONE` setting). (It's not clear to me
from the above whether it does or not; that deserves clarification.)

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

Re: [Django] #25616: Add note regarding missing dependencies on LookupError for migrations

2016-06-02 Thread Django

#25616: Add note regarding missing dependencies on LookupError for migrations
--+
Reporter: mcfletch |Owner: nip3o
Type: Cleanup/optimization | Status: assigned
Component: Migrations| 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 nip3o):

* needs_tests: 1 => 0

Comment:

New patch inspired from previous patch, including test:
https://github.com/django/django/pull/6699/

However, I realize that I'm not sure when this actually happens in
practice, which means that the new error message may actually be more
misleading then the old one.
* When trying to migrate model with a reference to an app which is not in
`INSTALLED_APPS`, we will typically get a `SystemCheckError` before the
migration even starts.
* When the app we depend upon is in `INSTALLED_APPS`, but the app is not
included in `dependencies`, we seems to get a `ValueError: Related model
... cannot be resolved`.
* When the name of an app in `dependencies` in the migration file does
not exist, we get a NodeNotFoundError.

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

Re: [Django] #26700: 1.10 release notes missing information on TEMPLATES setting

2016-06-02 Thread Django

#26700: 1.10 release notes missing information on TEMPLATES setting
-+-
 Reporter:  jrabbit  |Owner:  jrabbit
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  templates, settings  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jrabbit):

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

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

Re: [Django] #26607: Add InlineModelAdmin.get_formset_initial_data().

2016-06-02 Thread Django

#26607: Add InlineModelAdmin.get_formset_initial_data().
-+-
 Reporter:  dsanders11   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin inline | Triage Stage:  Accepted
  formset initial|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by phildini):

 * needs_better_patch:  0 => 1


Comment:

 Currently the PR has merge conflicts

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

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

Re: [Django] #26700: 1.10 release notes missing information on TEMPLATES setting

2016-06-02 Thread Django

#26700: 1.10 release notes missing information on TEMPLATES setting
-+-
 Reporter:  jrabbit  |Owner:  jrabbit
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  templates, settings  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jrabbit):

 * owner:  nobody => jrabbit
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 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/065.b92a9e2bf5b94b983224ff5f32a0ae10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26701: Improve link to issue tracker in the contributor guide

2016-06-02 Thread Django

#26701: Improve link to issue tracker in the contributor guide
--+
 Reporter:  shaunagm  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 timgraham):

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


Comment:

 I wouldn't include /query in the link.

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

[Django] #26701: Improve link to issue tracker in the contributor guide

2016-06-02 Thread Django

#26701: Improve link to issue tracker in the contributor guide
---+
 Reporter:  shaunagm   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In the contributor guide, the second link in "Report bugs in our ticket
 tracker", linked under "issue tracker", goes to
 https://code.djangoproject.com/newticket. If you're not logged in (which
 many new contributors will not be), you an "Error: Forbidden".

 I will replace it with a link to https://code.djangoproject.com/query

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

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

[Django] #26700: 1.10 release notes missing information on TEMPLATES setting

2016-06-02 Thread Django

#26700: 1.10 release notes missing information on TEMPLATES setting
--+-
 Reporter:  jrabbit   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal|   Keywords:  templates, settings
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+-
 Since the users actually have to do something it seems important to tell
 users what they need to do. Especially the auth context processor to keep
 old behavior. (`?: (admin.E402)
 'django.contrib.auth.context_processors.auth' must be in TEMPLATES in
 order to use the admin application.`)  which I only discovered after
 following the docs (the settings page) and hitting a check error.

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

Re: [Django] #12666: Setting for sending email using localtime instead of UTC

2016-06-02 Thread Django

#12666: Setting for sending email using localtime instead of UTC
-+
 Reporter:  net147   |Owner:  aisipos
 Type:  New feature  |   Status:  assigned
Component:  Core (Mail)  |  Version:  1.1
 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 aisipos):

 * status:  new => assigned
 * owner:  nobody => aisipos


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

Re: [Django] #19222: Clarify that custom managers don't apply to intermediate joins

2016-06-02 Thread Django

#19222: Clarify that custom managers don't apply to intermediate joins
--+
 Reporter:  andrewbadr|Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Hwesta):

 * status:  new => assigned
 * owner:  nobody => Hwesta
 * easy:  0 => 1
 * needs_docs:  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/068.4f0ffdbc3fb7616759dfe7db51da70fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-02 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dbshell  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by mieciu):

 I totally agree.

 However, I've found a way to actually have the fallback mechanism working
 for dbshell, so at least we're consistent here :)

 PR is already waiting.

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

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

2016-06-02 Thread Django

#2: assertRedirects gives unhelpful error message expected URL is external
-+-
 Reporter:  inglesp  |Owner:
 Type:   |  tobiasmcnulty
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann ):

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


Comment:

 In [changeset:"c7b1b81352533be9b7f4637c12219f59c0964a82" c7b1b81]:
 {{{
 #!CommitTicketReference repository=""
 revision="c7b1b81352533be9b7f4637c12219f59c0964a82"
 Fixed #2 -- Added more useful error message to assertRedirects
 }}}

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

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-02 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dbshell  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mieciu):

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

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

2016-06-02 Thread Django

#2: assertRedirects gives unhelpful error message expected URL is external
-+-
 Reporter:  inglesp  |Owner:
 Type:   |  tobiasmcnulty
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  1.9
 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 tobiasmcnulty):

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

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly

2016-06-02 Thread Django

#26005: uri_to_iri() perfoms percent decoding incorrectly
---+---
 Reporter:  Chronial   |Owner:  varunnaganathan
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.8
 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
---+---

Comment (by Chronial):

 Replying to [comment:8 phildini]:
 > Setting the 'patch_needs_improvement' bit as there are failing checks
 and open questions on the PR.

 What are the open questions?

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

Re: [Django] #26648: related_query_name is not checked for correctness

2016-06-02 Thread Django

#26648: related_query_name is not checked for correctness
--+
 Reporter:  konk  |Owner:  nobody
 Type:  Cleanup/optimization  |   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 carljm):

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

Re: [Django] #12666: Setting for sending email using localtime instead of UTC

2016-06-02 Thread Django

#12666: Setting for sending email using localtime instead of UTC
-+
 Reporter:  net147   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Mail)  |  Version:  1.1
 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 carljm):

 * easy:  0 => 1


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

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

Re: [Django] #25790: Add a way to disable column sorting in the admin

2016-06-02 Thread Django

#25790: Add a way to disable column sorting in the admin
-+-
 Reporter:  ramiro   |Owner:  sasha0
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sorting ordering | Triage Stage:  Accepted
  change list changelist admin   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_better_patch:  0 => 1
 * needs_docs:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 The documentation requires adjustments as the feature didn't make it in
 1.10.

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

Re: [Django] #26672: forms.HStoreField crashes on an empty JSON array

2016-06-02 Thread Django

#26672: forms.HStoreField crashes on an empty JSON array
--+--
 Reporter:  bradmerlin|Owner:  bradmerlin
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Release blocker   |   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:"3eb31867bb25d462634255e187001c0fffe2a032" 3eb3186]:
 {{{
 #!CommitTicketReference repository=""
 revision="3eb31867bb25d462634255e187001c0fffe2a032"
 [1.10.x] Fixed #26672 -- Fixed HStoreField to raise ValidationError
 instead of crashing on non-dict JSON input.

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

Re: [Django] #26672: forms.HStoreField crashes on an empty JSON array

2016-06-02 Thread Django

#26672: forms.HStoreField crashes on an empty JSON array
--+--
 Reporter:  bradmerlin|Owner:  bradmerlin
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Release blocker   |   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:"95ed1514f0947a6a8f461046d15bc9273517a754" 95ed1514]:
 {{{
 #!CommitTicketReference repository=""
 revision="95ed1514f0947a6a8f461046d15bc9273517a754"
 [1.9.x] Fixed #26672 -- Fixed HStoreField to raise ValidationError instead
 of crashing on non-dict JSON input.

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

Re: [Django] #26672: forms.HStoreField crashes on an empty JSON array

2016-06-02 Thread Django

#26672: forms.HStoreField crashes on an empty JSON array
--+--
 Reporter:  bradmerlin|Owner:  bradmerlin
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.9
 Severity:  Release blocker   |   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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"f6517a5335ccc4858ee540548a1bd162bec36c46" f6517a5]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6517a5335ccc4858ee540548a1bd162bec36c46"
 Fixed #26672 -- Fixed HStoreField to raise ValidationError instead of
 crashing on non-dict JSON input.
 }}}

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

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

Re: [Django] #26628: Log CSRF failures to django.security by default.

2016-06-02 Thread Django

Comment (by carljm):

I guess I'm not too concerned about back-compat, because it seems it would
only be an issue in a case where someone has configured logging to watch
`django.request` but ignore `django.security`, which seems like a pretty
strange choice. But I also don't feel strongly. I'd be inclined to merge
the doc fix that Hwesta has already submitted
(https://github.com/django/django/pull/6694/files) but as a `Refs`, and
leave this open for further discussion of the actual logger change.

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

Re: [Django] #25920: Add number formatting support for locales that use non-uniform digit grouping (e.g. India)

2016-06-02 Thread Django

#25920: Add number formatting support for locales that use non-uniform digit
grouping (e.g. India)
--+
 Reporter:  dbinoj|Owner:  jasisz
 Type:  New feature   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  en-IN | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jasisz):

 PR for this: https://github.com/django/django/pull/6693
 It basically adds possibility to use more robust NUMBER_GROUPING using
 style similar to POSIX locale grouping option.

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

Re: [Django] #25920: Add number formatting support for locales that use non-uniform digit grouping (e.g. India)

2016-06-02 Thread Django

#25920: Add number formatting support for locales that use non-uniform digit
grouping (e.g. India)
--+
 Reporter:  dbinoj|Owner:  jasisz
 Type:  New feature   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  en-IN | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jasisz):

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

Re: [Django] #25790: Add a way to disable column sorting in the admin

2016-06-02 Thread Django

#25790: Add a way to disable column sorting in the admin
-+-
 Reporter:  ramiro   |Owner:  sasha0
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sorting ordering | Triage Stage:  Ready for
  change list changelist admin   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by phildini):

 * stage:  Accepted => Ready for checkin


Comment:

 The PR looks good to me: the patch submitter has answered all questions,
 added tests, and all checks pass.

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

Re: [Django] #26628: Log CSRF failures to django.security by default.

2016-06-02 Thread Django

#26628: Log CSRF failures to django.security by default.
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timgraham):

 Are you concerned at all about backwards-compatibility in the case of some
 custom logging?

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

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly

2016-06-02 Thread Django

#26005: uri_to_iri() perfoms percent decoding incorrectly
---+---
 Reporter:  Chronial   |Owner:  varunnaganathan
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.8
 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 phildini):

 * needs_better_patch:  0 => 1


Comment:

 Setting the 'patch_needs_improvement' bit as there are failing checks and
 open questions on the PR.

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

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

Re: [Django] #26628: Log CSRF failures to django.security by default. (was: Document that CSRF violations are logged to the django.request logger)

2016-06-02 Thread Django

#26628: Log CSRF failures to django.security by default.
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by carljm):

 Sergio Campos (seocam) and I were just discussing this same issue at the
 PyCon sprint (in the context of looking at the broader context in #26688).
 I'm inclined to agree with mallyvai that this isn't just a doc bug -- we
 should be logging CSRF failures to django.security by default. Updating
 the ticket title accordingly -- please let me know if you don't agree, or
 think this should be discussed on the mailing list.

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

Re: [Django] #24781: lazy() may need a repr for Python 2

2016-06-02 Thread Django

#24781: lazy() may need a __repr__ for Python 2
---+-
 Reporter:  jdh13  |Owner:  chescales
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  py2| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+-
Changes (by chescales):

 * owner:  phildini => chescales


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

Re: [Django] #26359: explain dual ticket tracking system

2016-06-02 Thread Django

#26359: explain dual ticket tracking system
--+
 Reporter:  beckastar |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  wontfix
 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 timgraham):

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


Comment:

 As discussed on the PR, it's not clear that adding more information will
 help, given the info is already present on the new ticket page.

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+-
 Reporter:  aaugustin  |Owner:  bjcubsfan
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 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
---+-

Comment (by bjcubsfan):

 Replying to [comment:6 aaugustin]:
 > I believe this information would be more discoverable in the CSRF
 reference documentation, either in the "How to use it" section or in a new
 section.
 >
 > We should talk about:
 > - the API offered by built-in template backends
 > - requirements for third-party backends, as described in PEP 182
 (basically they have to provide a solution, but that solution isn't
 specified)
 >
 > This will likely require tweaking the content a bit to clarify that the
 main examples are specific to Django templates.

 I think you mean [https://github.com/django/deps/blob/master/final/0182
 -multiple-template-engines.rst DEP 182].

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

Re: [Django] #26586: makemigrations does not detect custom field subclassing change

2016-06-02 Thread Django

#26586: makemigrations does not detect custom field subclassing change
-+-
 Reporter:  tuffnatty|Owner:  baylee
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  migrations, custom   | Triage Stage:  Accepted
  fields |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by baylee):

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

Re: [Django] #24781: lazy() may need a repr for Python 2

2016-06-02 Thread Django

#24781: lazy() may need a __repr__ for Python 2
---+
 Reporter:  jdh13  |Owner:  phildini
 Type:  Bug|   Status:  assigned
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  py2| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by phildini):

 * owner:  nobody => phildini
 * status:  new => assigned


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

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

Re: [Django] #26656: Add timedelta support to DjangoJSONEncoder

2016-06-02 Thread Django

#26656: Add timedelta support to DjangoJSONEncoder
-+-
 Reporter:  willhardy|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  1.9
  (Serialization)|
 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
-+-

Comment (by toffer):

 Looks good! Reviewed as part of the Django sprint at PyCon.

 `tests.serializers.test_json:test_timedelta` passes with the patch. It
 fails without the patch.

 The new `TestParseISODurationRoundtrip` tests look good.

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

Re: [Django] #2750: ManyToManyField ignores 'default' option

2016-06-02 Thread Django

#2750: ManyToManyField ignores 'default' option
-+-
 Reporter:  bangcok_dangerus@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by phildini):

 Has there been any movement on this? When you say forms make use of the
 default option, what do you mean?

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

Re: [Django] #26656: Add timedelta support to DjangoJSONEncoder

2016-06-02 Thread Django

#26656: Add timedelta support to DjangoJSONEncoder
-+-
 Reporter:  willhardy|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core |  Version:  1.9
  (Serialization)|
 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 chescales):

 * cc: chescales (added)
 * stage:  Accepted => Ready for checkin


Comment:

 I gave a look at the code, and seems to solve the problem. Adds support
 for ISO durations. Includes new tests which seem to cover most of the
 cases (replicates previous duration tests, with the new ISO format).

 Only thing is I am not able to tell if the format should be included
 anywhere in the official docs of the serializers or if it's not necessary.

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

Re: [Django] #26628: Document that CSRF violations are logged to the django.request logger

2016-06-02 Thread Django

#26628: Document that CSRF violations are logged to the django.request logger
--+
 Reporter:  jacobian  |Owner:  Hwesta
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  csrf security | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Hwesta):

 * owner:  nobody => Hwesta
 * needs_docs:  0 => 1
 * status:  new => assigned
 * easy:  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.9c6ef0f3d94f7c5f7813045bffc49c0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24781: lazy() may need a repr for Python 2

2016-06-02 Thread Django

#24781: lazy() may need a __repr__ for Python 2
---+
 Reporter:  jdh13  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Utilities  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  py2| Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by carljm):

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

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-02 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dbshell  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 If we want Django refusing the default database name with Postgres, that
 should be the subject of a separate ticket (and maybe a discussion on the
 django-developers mailing list). But clearly, the `_escape_pgpass` should
 not crash when receiving a `None` value.

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

Re: [Django] #26337: Translations - No fallback used if requesting english variant

2016-06-02 Thread Django

#26337: Translations - No fallback used if requesting english variant
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  i18n translations| Triage Stage:  Ready for
  english|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"5641a80d49d31916828ef7478af1800d0469c46a" 5641a80]:
 {{{
 #!CommitTicketReference repository=""
 revision="5641a80d49d31916828ef7478af1800d0469c46a"
 [1.10.x] Fixed #26337 -- Added i18n note about using a non-English base
 language

 Thanks Cristiano Coelho for the report and Tim Graham for the review.
 Backport of f6fefbf8cb 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/070.f2274162ba6aae406800f90a4da89f53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26337: Translations - No fallback used if requesting english variant

2016-06-02 Thread Django

#26337: Translations - No fallback used if requesting english variant
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  i18n translations| Triage Stage:  Ready for
  english|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"f6fefbf8cb0f44126adcd052916bca4b872c565a" f6fefbf]:
 {{{
 #!CommitTicketReference repository=""
 revision="f6fefbf8cb0f44126adcd052916bca4b872c565a"
 Fixed #26337 -- Added i18n note about using a non-English base language

 Thanks Cristiano Coelho for the report and Tim Graham for the review.
 }}}

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

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

Re: [Django] #26642: ModelSignal.disconnect() does not work with lazy references

2016-06-02 Thread Django

#26642: ModelSignal.disconnect() does not work with lazy references
-+-
 Reporter:  AlexHill |Owner:  nobody
 Type:  Bug  |   Status:  closed
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:"f91247f59824522ceef67cac0def8253cf491f6a" f91247f]:
 {{{
 #!CommitTicketReference repository=""
 revision="f91247f59824522ceef67cac0def8253cf491f6a"
 [1.10.x] Fixed #26642 -- Made ModelSignal.disconnect() work with lazy
 references.

 Backport of ff6c6feae17120c2c7df74fb6a9dc76826a1e233 from master
 }}}

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

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

Re: [Django] #26686: django.core.checks.model_checks _check_lazy_references raises TypeError with NoneType model_key

2016-06-02 Thread Django

#26686: django.core.checks.model_checks _check_lazy_references raises TypeError
with NoneType model_key
--+
 Reporter:  bretth|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (System checks)  |  Version:  1.10
 Severity:  Release blocker   |   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:"85d2b80d5e84aa16454a4cac187b91fec2ec4e48" 85d2b80d]:
 {{{
 #!CommitTicketReference repository=""
 revision="85d2b80d5e84aa16454a4cac187b91fec2ec4e48"
 [1.10.x] Fixed #26686 -- Fixed crash when registering model signals with
 abstract senders.

 Backport of 08014fe75b4fc379523f340191a02147ec35f7a3 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/064.87d641224521cc8d3c25d8a1fa8c7a59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26686: django.core.checks.model_checks _check_lazy_references raises TypeError with NoneType model_key

2016-06-02 Thread Django

#26686: django.core.checks.model_checks _check_lazy_references raises TypeError
with NoneType model_key
--+
 Reporter:  bretth|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (System checks)  |  Version:  1.10
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"08014fe75b4fc379523f340191a02147ec35f7a3" 08014fe7]:
 {{{
 #!CommitTicketReference repository=""
 revision="08014fe75b4fc379523f340191a02147ec35f7a3"
 Fixed #26686 -- Fixed crash when registering model signals with abstract
 senders.
 }}}

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+-
 Reporter:  aaugustin  |Owner:  bjcubsfan
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 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 bjcubsfan):

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

Re: [Django] #25616: Add note regarding missing dependencies on LookupError for migrations

2016-06-02 Thread Django

#25616: Add note regarding missing dependencies on LookupError for migrations
--+
 Reporter:  mcfletch  |Owner:  nip3o
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Migrations|  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 nip3o):

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

Re: [Django] #26359: explain dual ticket tracking system

2016-06-02 Thread Django

#26359: explain dual ticket tracking system
--+
 Reporter:  beckastar |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 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 phildini):

 * has_patch:  0 => 1


Comment:

 Pull request here: https://github.com/django/django/pull/6692

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

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

2016-06-02 Thread Django

#26423: Make EmailValidator use HTML5 validation rather than more complicated
regular expressions
--+
 Reporter:  timgraham |Owner:  cjbcross
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  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 cjbcross):

 Taking ownership on this at PyCon2016 Sprint.  Discussed with Markus and
 have background on consensus direction a solution should take.

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

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

2016-06-02 Thread Django

#26423: Make EmailValidator use HTML5 validation rather than more complicated
regular expressions
--+
 Reporter:  timgraham |Owner:  cjbcross
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by cjbcross):

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

Re: [Django] #26683: Oracle DBs: Add option to use VARCHAR2 data type

2016-06-02 Thread Django

#26683: Oracle DBs: Add option to use VARCHAR2 data type
+--
 Reporter:  elarandjelovic  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Migrations  |  Version:  1.9
 Severity:  Normal  |   Resolution:
 Keywords:  Oracle  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by timgraham):

 If we move forward with this, I prefer the approach of a temporary setting
 to opt-in to the new behavior (which eventually becomes mandatory) rather
 than creating a backend with a new name (unless there are compelling
 arguments against this approach).

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

Re: [Django] #26688: Inconsistent logging of 5xx and 4xx requests to django.request

2016-06-02 Thread Django

#26688: Inconsistent logging of 5xx and 4xx requests to django.request
---+
 Reporter:  solarissmoke   |Owner:  seocam
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by seocam):

 * owner:  nobody => seocam
 * cc: seocam@… (added)
 * 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/070.e0a221b23efe408231161f2709e19c4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26688: Inconsistent logging of 5xx and 4xx requests to django.request

2016-06-02 Thread Django

#26688: Inconsistent logging of 5xx and 4xx requests to django.request
---+
 Reporter:  solarissmoke   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by seocam):

 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 The logging behavior is clearly inconsistent with the docs. The documented
 behavior is preferable over the current one so that's actually 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/070.dd6ae024cbb8e16c6f007a278a045183%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26698: dbshell crashes on Postgres backend with empty database name

2016-06-02 Thread Django

#26698: dbshell crashes on Postgres backend with empty database name
-+-
 Reporter:  IlyaSemenov  |Owner:  mieciu
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.9
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  dbshell  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by mieciu):

 It's something related to  postgresql's `DatabaseClient` class and
 temporary `.pgpass` file creation.

 IMO omitting such a vital parameter database name is a crucial mistake in
 configuration and nobody should rely here on any fallback mechanism...

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

Re: [Django] #26699: Contributing docs should highlight difference between locally-built docs and server docs

2016-06-02 Thread Django

#26699: Contributing docs should highlight difference between locally-built docs
and server docs
--+
 Reporter:  phildini  |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2c90981c5f06c0cb3d7a438dd9454ec94fefae17" 2c90981]:
 {{{
 #!CommitTicketReference repository=""
 revision="2c90981c5f06c0cb3d7a438dd9454ec94fefae17"
 Fixed #26699 -- Mentioned doc theming difference (locally-built vs.
 website).
 }}}

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

Re: [Django] #26699: Contributing docs should highlight difference between locally-built docs and server docs

2016-06-02 Thread Django

#26699: Contributing docs should highlight difference between locally-built docs
and server docs
--+
 Reporter:  phildini  |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.9
 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 phildini):

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

Re: [Django] #26699: Contributing docs should highlight difference between locally-built docs and server docs

2016-06-02 Thread Django

#26699: Contributing docs should highlight difference between locally-built docs
and server docs
--+
 Reporter:  phildini  |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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:  1 |UI/UX:  0
--+

Comment (by phildini):

 Pull request here: https://github.com/django/django/pull/6690

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

Re: [Django] #26666: assertRedirects gives unhelpful error message expected URL is external

2016-06-02 Thread Django

#2: assertRedirects gives unhelpful error message expected URL is external
-+-
 Reporter:  inglesp  |Owner:
 Type:   |  tobiasmcnulty
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  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 tobiasmcnulty):

 * status:  new => assigned
 * owner:  nobody => tobiasmcnulty


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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-06-02 Thread Django

#26526: Document QuerySet.latest() behavior for null values
--+
 Reporter:  int-ua|Owner:  g3rd
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 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 g3rd):

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

Re: [Django] #26699: Contributing docs should highlight difference between locally-built docs and server docs

2016-06-02 Thread Django

#26699: Contributing docs should highlight difference between locally-built docs
and server docs
--+
 Reporter:  phildini  |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * type:  Bug => 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/066.5a6ec6e999ad63e5a8e4f5f8705cd00d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26337: Translations - No fallback used if requesting english variant

2016-06-02 Thread Django

#26337: Translations - No fallback used if requesting english variant
-+-
 Reporter:  cristianocca |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  i18n translations| Triage Stage:  Ready for
  english|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #26526: Document QuerySet.latest() behavior for null values

2016-06-02 Thread Django

#26526: Document QuerySet.latest() behavior for null values
--+
 Reporter:  int-ua|Owner:  g3rd
 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 g3rd):

 Pull request: https://github.com/django/django/pull/6689

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

Re: [Django] #26617: Support distinct values aggregation in postgres.aggregates.StringAgg

2016-06-02 Thread Django

#26617: Support distinct values aggregation in postgres.aggregates.StringAgg
-+-
 Reporter:  rkashapov|Owner:  Tim
 |  Graham 
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"df8412d2e5c95fe8c8238ebde8e0dbb68fe2ec1d" df8412d2]:
 {{{
 #!CommitTicketReference repository=""
 revision="df8412d2e5c95fe8c8238ebde8e0dbb68fe2ec1d"
 Fixed #26617 -- Added distinct argument to contrib.postgres's StringAgg.
 }}}

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

Re: [Django] #26699: Contributing docs should highlight difference between locally-built docs and server docs

2016-06-02 Thread Django

#26699: Contributing docs should highlight difference between locally-built docs
and server docs
---+--
 Reporter:  phildini   |Owner:  phildini
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.9
 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 phildini):

 * owner:  nobody => phildini
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 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/066.0a2ac29f8f11db661c8cbb8991970394%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26699: Contributing docs should highlight difference between locally-built docs and server docs

2016-06-02 Thread Django

#26699: Contributing docs should highlight difference between locally-built docs
and server docs
---+
 Reporter:  phildini   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 If you build the docs locally and open them, they will look different than
 the docs on the server.

 This is expected but potentially confusing to new contributors. The
 contributing docs should talk about 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/051.4b755ce37c436ddd9a2b5195d301abe6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26359: explain dual ticket tracking system

2016-06-02 Thread Django

#26359: explain dual ticket tracking system
--+
 Reporter:  beckastar |Owner:  phildini
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by phildini):

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

Re: [Django] #26638: Allow callable in defaults argument for QuerySet.get_or_create

2016-06-02 Thread Django

#26638: Allow callable in defaults argument for QuerySet.get_or_create
-+-
 Reporter:  mlorant  |Owner:
 |  ddsnowboard
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * needs_docs:  1 => 0


Comment:

 Left comments for improvement on the PR. Please uncheck "Patch needs
 improvement" after updating.

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+-
 Reporter:  aaugustin  |Owner:  bjcubsfan
 Type:  Bug|   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
---+-
Changes (by bjcubsfan):

 * status:  new => assigned
 * owner:   => bjcubsfan


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

Re: [Django] #25920: Add number formatting support for locales that use non-uniform digit grouping (e.g. India)

2016-06-02 Thread Django

#25920: Add number formatting support for locales that use non-uniform digit
grouping (e.g. India)
--+
 Reporter:  dbinoj|Owner:  jasisz
 Type:  New feature   |   Status:  assigned
Component:  Internationalization  |  Version:  1.9
 Severity:  Normal|   Resolution:
 Keywords:  en-IN | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jasisz):

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+
 Reporter:  aaugustin  |Owner:
 Type:  Bug|   Status:  new
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
---+
Changes (by phildini):

 * owner:  phildini =>
 * status:  assigned => new


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

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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+
 Reporter:  aaugustin  |Owner:  phildini
 Type:  Bug|   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
---+
Changes (by phildini):

 * owner:  bjcubsfan => phildini


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

Re: [Django] #26596: Document {{ csrf_input }} in Jinja2 templates

2016-06-02 Thread Django

#26596: Document {{ csrf_input }} in Jinja2 templates
---+-
 Reporter:  aaugustin  |Owner:  bjcubsfan
 Type:  Bug|   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
---+-
Changes (by bjcubsfan):

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

1 2 >

1 - 100 of 127 matches

Mail list logo