date:20131014

Re: [Django] #7603: Add HttpRequest.scheme property

2013-10-14 Thread Django

#7603: Add HttpRequest.scheme property
-+-
 Reporter:  nslater  |Owner:
 Type:  New feature  |  unaizalakain
Component:  HTTP handling|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by aaugustin):

 LGTM.

 Why do the docs say "normally" and "usually"? The current implementation
 is always going to return 'http' or 'https'. Let's avoid vague terms.

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

Re: [Django] #18400: Unexpected {% if %} behavior

2013-10-14 Thread Django

#18400: Unexpected {% if %} behavior
--+
 Reporter:  apollo13  |Owner:  susan
 Type:  Bug   |   Status:  assigned
Component:  Template system   |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  template, if, length  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by susan):

 * cc: susan.tan.fleckerl@… (added)
 * owner:  nobody => susan
 * 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.ee8d91d991d712f92bb05b3538546934%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static files

2013-10-14 Thread Django

#21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static 
files
-+
 Reporter:  dblack+django@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  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
-+

Comment (by vajrasky):

 Apparently I did not fork the django repo first from my github account.
 Now I managed to make a pull request!
 https://github.com/django/django/pull/1747

-- 
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/085.6e1db2d2ef7a4863b049a5a730569bd7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19299: Foreign keys using to_field and having legitimate empty string values fail with NULL errors

2013-10-14 Thread Django

#19299: Foreign keys using to_field and having legitimate empty string values 
fail
with NULL errors
-+-
 Reporter:  evan@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by albertyw@…):

 * cc: albertyw@… (added)


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

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

Re: [Django] #21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static files

2013-10-14 Thread Django

#21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static 
files
-+
 Reporter:  dblack+django@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  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
-+

Comment (by vajrasky):

 $ git push origin ticket_21219
 error: The requested URL returned error: 403 Forbidden while accessing
 https://vajra...@github.com/django/django.git/info/refs?service=git-
 receive-pack
 fatal: HTTP request failed

 @timo, I am working on it. Probably it takes longer time since I need to
 learn how to solve this problem.

-- 
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/085.1491a2b5054e5832f6d5bd096d6c80c4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13245: manually set db_table should not validate if it needs to be truncated

2013-10-14 Thread Django

* easy: 1 => 0

Comment:

Hi Shai, I looked into this on PostgreSQL. Specifying `db_name="string
longer ... than 63 characters"` results in the table name being silently
truncated at 63 characters (does not use
`django.db.backends.utils.truncate_name`). Arguably this should be fixed,
perhaps there's already a ticket, although it seems quite uncommon and low
priority.

The action item I was proposing for this ticket was what Russ proposed in
comment 2: "I would expect to see a validation error if you ever tried to
synchronize a model with a db_table specification that exceeded the limits
of the backend."

Do you disagree with that? Of course, this ticket seems a bit trickier
than I expected given the Oracle specific logic in it's definition of
`quote_name` you mentioned regarding a quoted `db_name`.

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

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText

2013-10-14 Thread Django

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

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


Comment:

 I decided to fix the webdesign tag docstring. I don't expect normalized
 docstrings to start with indentation -- clearly the intent here wasn't to
 parse the "Example:" section as metadata.

-- 
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.195800bf4e924395e1f57eb12c04ca52%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6681: `admindocs` breaks compatibility with `docutils` when rendering reStructuredText

2013-10-14 Thread Django

#6681: `admindocs` breaks compatibility with `docutils` when rendering
reStructuredText
-+-
 Reporter:  mtredinnick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admindocs|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  restructuredtext | Triage Stage:  Accepted
  docutils   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"975415a8cef38cf2a49c3ce8234c15ef97a69b5f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="975415a8cef38cf2a49c3ce8234c15ef97a69b5f"
 Fixed a webdesign template tag docstring to prevent parsing as metadata.

 Previously admindocs would throw an error when processing it:
 "Error in "default-role" directive: no content permitted."

 refs #6681
 }}}

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

[django/django] 975415: Fixed a webdesign template tag docstring to preven...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 975415a8cef38cf2a49c3ce8234c15ef97a69b5f
  
https://github.com/django/django/commit/975415a8cef38cf2a49c3ce8234c15ef97a69b5f
  Author: Tim Graham 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M django/contrib/webdesign/templatetags/webdesign.py

  Log Message:
  ---
  Fixed a webdesign template tag docstring to prevent parsing as metadata.

Previously admindocs would throw an error when processing it:
"Error in "default-role" directive: no content permitted."

refs #6681



-- 
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/525c834c77bc9_23ec10b1d546106f%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7603: Add HttpRequest.scheme property

2013-10-14 Thread Django

#7603: Add HttpRequest.scheme property
-+-
 Reporter:  nslater  |Owner:
 Type:  New feature  |  unaizalakain
Component:  HTTP handling|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 This looks good to me, but since it's potentially security related I'd
 like one more +1 before committing.

-- 
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.8520600cfd1fda2c31499a79bc0427f3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21172: have LiveServerThread follow the semantics of threading.Thread.join()

2013-10-14 Thread Django

#21172: have LiveServerThread follow the semantics of threading.Thread.join()
-+-
 Reporter:  ldd  |Owner:
 Type:  Bug  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  live server, test|   Resolution:
  server, live wsgi  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by unaizalakain):

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

-- 
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/061.6d64b6e597bb6e2e250319c07c9ff7d8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7261: Support for html for Library interoperability

2013-10-14 Thread Django

#7261: Support for __html__ for Library interoperability
-+
 Reporter:  mitsuhiko|Owner:  unaizalakain
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  __html__ | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by unaizalakain):

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

-- 
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.52548e077a23cc7488a2690f134ad93f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:  saoili
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by Tim Graham ):

 In [changeset:"07ebd23254acab0677aca8baf76440811e9473e2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="07ebd23254acab0677aca8baf76440811e9473e2"
 [1.6.x] Fixed #21223 -- Added form.id_for_label to topic guide.

 Thanks ebertti at yahoo.com.br for the suggestion.

 Backport of 018e2c055a 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/078.a81bd17926fdcb008956072e89e5028b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 6e7de2: [1.5.x] Fixed #21223 -- Added form.id_for_label to...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 6e7de2edb0565e0ea2fd4ff6701e97ead67138b9
  
https://github.com/django/django/commit/6e7de2edb0565e0ea2fd4ff6701e97ead67138b9
  Author: Sorcha Bowler 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/topics/forms/index.txt

  Log Message:
  ---
  [1.5.x] Fixed #21223 -- Added form.id_for_label to topic guide.

Thanks ebertti at yahoo.com.br for the suggestion.

Backport of 018e2c055a from master



-- 
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/525c73acbb383_26c61165d54119757%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 018e2c: Fixed #21223 -- Added form.id_for_label to topic g...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 018e2c055a894c4869985b0fda64e52a6c368f32
  
https://github.com/django/django/commit/018e2c055a894c4869985b0fda64e52a6c368f32
  Author: Sorcha Bowler 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/topics/forms/index.txt

  Log Message:
  ---
  Fixed #21223 -- Added form.id_for_label to topic guide.

Thanks ebertti at yahoo.com.br for the suggestion.



-- 
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/525c7388dad97_6900d8bd50901d5%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 07ebd2: [1.6.x] Fixed #21223 -- Added form.id_for_label to...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 07ebd23254acab0677aca8baf76440811e9473e2
  
https://github.com/django/django/commit/07ebd23254acab0677aca8baf76440811e9473e2
  Author: Sorcha Bowler 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/topics/forms/index.txt

  Log Message:
  ---
  [1.6.x] Fixed #21223 -- Added form.id_for_label to topic guide.

Thanks ebertti at yahoo.com.br for the suggestion.

Backport of 018e2c055a from master



-- 
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/525c73b033fab_48301051d501259d5%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:  saoili
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"6e7de2edb0565e0ea2fd4ff6701e97ead67138b9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6e7de2edb0565e0ea2fd4ff6701e97ead67138b9"
 [1.5.x] Fixed #21223 -- Added form.id_for_label to topic guide.

 Thanks ebertti at yahoo.com.br for the suggestion.

 Backport of 018e2c055a 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/078.b6b362aa34f6961780c492225b4d7e46%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7261: Support for html for Library interoperability

2013-10-14 Thread Django

#7261: Support for __html__ for Library interoperability
-+
 Reporter:  mitsuhiko|Owner:  unaizalakain
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  __html__ | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by unaizalakain):

 * owner:   => unaizalakain
 * 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.92fa332b9cfa37d2559f0471991934a5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9722: Use pyinotify (where available) instead of polling filesystem every second to detect changes

2013-10-14 Thread Django

#9722: Use pyinotify (where available) instead of polling filesystem every 
second
to detect changes
-+-
 Reporter:  lamby|Owner:
 Type:  New feature  |  unaizalakain
Component:  Core (Management |   Status:  assigned
  commands)  |  Version:  1.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by unaizalakain):

 * owner:  nobody => unaizalakain
 * 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.4364180b3b8a4bb16078930bbd84816a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7603: Add HttpRequest.scheme property

2013-10-14 Thread Django

#7603: Add HttpRequest.scheme property
---+
 Reporter:  nslater|Owner:  unaizalakain
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 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 unaizalakain):

 * owner:  nslater => unaizalakain


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

[django/django] 83b9bf: Fixed #21266 -- Fixed E201,E202 pep8 warnings.

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 83b9bfea44e23c5770fa14a8921914839929233b
  
https://github.com/django/django/commit/83b9bfea44e23c5770fa14a8921914839929233b
  Author: Larry O'Neill 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M django/contrib/admin/validation.py
M django/contrib/comments/moderation.py
M django/contrib/gis/db/backends/postgis/introspection.py
M django/contrib/gis/db/models/sql/compiler.py
M django/contrib/gis/db/models/sql/where.py
M django/contrib/gis/gdal/error.py
M django/contrib/gis/gdal/field.py
M django/contrib/gis/gdal/geometries.py
M django/contrib/gis/gdal/tests/test_geom.py
M django/contrib/gis/geoip/prototypes.py
M django/contrib/gis/geos/mutable_list.py
M django/contrib/gis/geos/tests/test_mutable_list.py
M django/contrib/gis/maps/google/zoom.py
M django/contrib/gis/tests/distapp/tests.py
M django/contrib/gis/tests/geo3d/tests.py
M django/contrib/gis/tests/geoapp/tests.py
M django/core/context_processors.py
M django/dispatch/saferef.py
M django/template/debug.py
M django/test/_doctest.py
M django/utils/termcolors.py
M django/views/debug.py
M setup.cfg
M tests/admin_custom_urls/tests.py
M tests/admin_widgets/tests.py
M tests/cache/tests.py
M tests/defaultfilters/tests.py
M tests/forms_tests/tests/test_fields.py
M tests/forms_tests/tests/test_formsets.py
M tests/i18n/tests.py
M tests/model_forms/tests.py
M tests/template_tests/filters.py
M tests/template_tests/tests.py
M tests/utils_tests/test_http.py
M tests/utils_tests/test_text.py

  Log Message:
  ---
  Fixed #21266 -- Fixed E201,E202 pep8 warnings.



-- 
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/525c700f1461f_6ab2989d4c9923a%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21266: pep8 cleanup: whitespace before/after parens and braces

2013-10-14 Thread Django

#21266: pep8 cleanup: whitespace before/after parens and braces
--+
 Reporter:  timo  |Owner:  larryone
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  flake8| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"83b9bfea44e23c5770fa14a8921914839929233b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="83b9bfea44e23c5770fa14a8921914839929233b"
 Fixed #21266 -- Fixed E201,E202 pep8 warnings.
 }}}

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

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

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:  saoili
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by saoili):

 Pull Request https://github.com/django/django/pull/1742 sent

-- 
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/078.3109912cce257ae47a979c31783fe2b7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-10-14 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  nsmgr8
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In
 [changeset:"1be21651988374fc5b9b3cf8eb9afb76de229ff0/djangoproject.com"]:
 {{{
 #!CommitTicketReference repository="djangoproject.com"
 revision="1be21651988374fc5b9b3cf8eb9afb76de229ff0"
 Added CSS for sphinx snippet directive.

 refs #20910.
 }}}

-- 
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/078.995d080777d90422346a209224228ae2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21269: UnicodeDecodeError on makemessages -d djangojs

2013-10-14 Thread Django

#21269: UnicodeDecodeError on makemessages -d djangojs
-+-
 Reporter:  kontakt@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:
  commands)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 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 Claude Paroz ):

 In [changeset:"ba9cf9596bb07d30614257a755f3e4fea426d2e2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ba9cf9596bb07d30614257a755f3e4fea426d2e2"
 [1.6.x] Fixed #21269 -- Don't crash when CommandError contains non-ascii

 Thanks kont...@eikefoken.de for the report.

 Backport of 42a67ec1cd 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/078.552bad9bb1d106b1f63de8b915cd1710%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ba9cf9: [1.6.x] Fixed #21269 -- Don't crash when CommandEr...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: ba9cf9596bb07d30614257a755f3e4fea426d2e2
  
https://github.com/django/django/commit/ba9cf9596bb07d30614257a755f3e4fea426d2e2
  Author: Claude Paroz 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M django/core/management/base.py
M tests/admin_scripts/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #21269 -- Don't crash when CommandError contains non-ascii

Thanks kont...@eikefoken.de for the report.

Backport of 42a67ec1cd from master.



-- 
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/525c466a11857_444745d4c920b7%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21230: Remove usage of direct settings manipulation in Django's tests

2013-10-14 Thread Django

#21230: Remove usage of direct settings manipulation in Django's tests
--+
 Reporter:  akaariai  |Owner:
 Type:  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:  1 |UI/UX:  0
--+
Changes (by Sephi):

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


Comment:

 Please don't forget to check the owner field before starting to work on a
 ticket (see https://docs.djangoproject.com/en/1.5/internals/contributing
 /writing-code/submitting-patches/#claiming-tickets). I'm unassigning it,
 feel free to reassign it to yourself.

-- 
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.26d16b58b0b5cb4d72015d2407ead215%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 42a67e: Fixed #21269 -- Don't crash when CommandError cont...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 42a67ec1cd8cbaffd87f0a7b34714f7d4a259cfb
  
https://github.com/django/django/commit/42a67ec1cd8cbaffd87f0a7b34714f7d4a259cfb
  Author: Claude Paroz 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M django/core/management/base.py
M tests/admin_scripts/tests.py

  Log Message:
  ---
  Fixed #21269 -- Don't crash when CommandError contains non-ascii

Thanks kont...@eikefoken.de for the report.



-- 
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/525c4445875ab_4831f45d58830e6%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21269: UnicodeDecodeError on makemessages -d djangojs

2013-10-14 Thread Django

#21269: UnicodeDecodeError on makemessages -d djangojs
-+-
 Reporter:  kontakt@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:
  commands)  |  1.6-beta-1
 Severity:  Normal   |   Resolution:  fixed
 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 Claude Paroz ):

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


Comment:

 In [changeset:"42a67ec1cd8cbaffd87f0a7b34714f7d4a259cfb"]:
 {{{
 #!CommitTicketReference repository=""
 revision="42a67ec1cd8cbaffd87f0a7b34714f7d4a259cfb"
 Fixed #21269 -- Don't crash when CommandError contains non-ascii

 Thanks kont...@eikefoken.de for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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/078.57e621f6befcc57324eaa99572722302%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5418: Add assertNoBrokenLinks() to test system

2013-10-14 Thread Django

#5418: Add assertNoBrokenLinks() to test system
-+-
 Reporter:  adrian   |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  feature  |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by unaizalakain):

 Pull request issued: https://github.com/django/django/pull/1740

 Check for broken links in a rendered page. By default only internal links
 are
 checked, if `only_internal` is `False`, external links are checked too.

 This commit adds the patch, the tests and the docs where the possible side
 effects of this test are noted.

-- 
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.4f7804fc5572d7bc1e29a97b7c57ac1b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8ab5f1: Close file after tests added in 945e033a69.

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8ab5f1fe4750105dae734764baed54bd4d22792b
  
https://github.com/django/django/commit/8ab5f1fe4750105dae734764baed54bd4d22792b
  Author: Ramiro Morales 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M tests/files/tests.py

  Log Message:
  ---
  Close file after tests added in 945e033a69.

Avoids failures on Windows. Refs #8918.



-- 
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/525c399ba37b6_26831251d581396e9%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8918: FileField upload_to should not be required for custom backends

2013-10-14 Thread Django

#8918: FileField upload_to should not be required for custom backends
-+-
 Reporter:  leahculver   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  FileField, files,|  Needs documentation:  0
  upload, S3, upload_to  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by Ramiro Morales ):

 In [changeset:"8ab5f1fe4750105dae734764baed54bd4d22792b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8ab5f1fe4750105dae734764baed54bd4d22792b"
 Close file after tests added in 945e033a69.

 Avoids failures on Windows. Refs #8918.
 }}}

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

Re: [Django] #21269: UnicodeDecodeError on makemessages -d djangojs

2013-10-14 Thread Django

#21269: UnicodeDecodeError on makemessages -d djangojs
-+-
 Reporter:  kontakt@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.6-beta-1
 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 claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Translations => Core (Management commands)
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I guess the issue is due to `CommandError` containing non-ascii content.
 I'll try to prepare a fix (probably adding more `unicode_literals`).

-- 
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/078.611fff730f37aa0d6377e6e762255532%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21268: pep8 cleanup: too many blank lines

2013-10-14 Thread Django

#21268: pep8 cleanup: too many blank lines
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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:  1 |UI/UX:  0
--+
Description changed by timo:

Old description:

> To find errors: `flake8
> --exclude=./django/utils/dictconfig.py,./django/contrib/comments/*,./django/utils/unittest.py,./tests/comment_tests/*,./django/test/_doctest.py
> --select=E303`
>
> Attaching a patch to get you started.
>
> Apply it:
>
> `patch -p1 -i E303.diff`

New description:

 To find errors, ensure you have an up-to-date master with the flake8
 config in setup.cfg, then remove E303 from the ignore list there. You can
 then run `flake8` from the directory with setup.cfg in it to list all
 errors.

 Attaching an example patch to get you started.

 Apply it, if you'd like:

 `patch -p1 -i E303.diff`

--

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

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

Re: [Django] #21267: pep8 cleanup: the backslash is redundant between brackets

2013-10-14 Thread Django

#21267: pep8 cleanup: the backslash is redundant between brackets
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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:  1 |UI/UX:  0
--+
Description changed by timo:

Old description:

> To find errors: `flake8
> --exclude=./django/utils/dictconfig.py,./django/contrib/comments/*,./django/utils/unittest.py,./tests/comment_tests/*,./django/test/_doctest.py
> --select=E502`
>
> Attaching a patch to get you started.
>
> Apply it:
>
> `patch -p1 -i E502.diff`

New description:

 To find errors, ensure you have an up-to-date master with the flake8
 config in setup.cfg, then remove E502 from the ignore list there. You can
 then run `flake8` from the directory with setup.cfg in it to list all
 errors.

 Attaching an example patch to get you started.

 Apply it, if you'd like:

 `patch -p1 -i E502.diff`

--

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

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

Re: [Django] #21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static files

2013-10-14 Thread Django

#21219: The FILE_UPLOAD_PERMISSIONS should not be used when deploying static 
files
-+
 Reporter:  dblack+django@…  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.staticfiles  |  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 timo):

 * has_patch:  0 => 1
 * type:  Cleanup/optimization => New feature


Comment:

 @vajrasky - any chance you can make a pull request on github so we can
 more easily comment on the patch?

 Also don't forget to tick "Has patch" so the ticket shows up for 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/085.bf22f0aabc6c41e85ed91f8ddbb7d695%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #23: Add support for ValidationWarning

2013-10-14 Thread Django

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  jgeskens
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:
 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:  1
-+
Changes (by rtnpro):

 * cc: rtnpro (added)


Comment:

 @aaugustin Sounds like a plan. I am researching on this issue and I will
 create a new ticket based on the current code and the things discussed in
 this thread and start fresh.

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

[django/django] 1ac534: Added flake8 info to setup.cfg.

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1ac534a92f8cabc209ccabe223344b43bc1b11d8
  
https://github.com/django/django/commit/1ac534a92f8cabc209ccabe223344b43bc1b11d8
  Author: Tim Graham 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M setup.cfg

  Log Message:
  ---
  Added flake8 info to setup.cfg.

This config allows a clean run of flake8. Some of the ignored
codes will be remove over time as we clean things up.



-- 
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/525c2d92e43e2_4d4ec9d48596a4%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17193: Send templated email.

2013-10-14 Thread Django

#17193: Send templated email.
-+---
 Reporter:  tomchristie  |Owner:  julianapplebaum
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---

Comment (by charettes):

 @anon yes, you could use the
 [https://docs.djangoproject.com/en/dev/ref/templates/api/#the-render-to-
 string-shortcut render_to_string] function to build the `html_message`
 kwarg passed to `send_mail`.

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

Re: [Django] #14974: Add support for translation backends other than gettext

2013-10-14 Thread Django

#14974: Add support for translation backends other than gettext
--+
 Reporter:  marinho   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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 rtnpro):

 * cc: rtnpro (added)


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

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

Re: [Django] #14974: Add support for translation backends other than gettext

2013-10-14 Thread Django

#14974: Add support for translation backends other than gettext
--+
 Reporter:  marinho   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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 rtnpro):

 Is any one working on this feature request?

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

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

Re: [Django] #21267: pep8 cleanup: the backslash is redundant between brackets

2013-10-14 Thread Django

#21267: pep8 cleanup: the backslash is redundant between brackets
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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:  1 |UI/UX:  0
--+
Description changed by timo:

Old description:

> To find errors: `flake8 --select=E502`
>
> Attaching a patch to get you started.
>
> Apply it:
>
> `patch -p1 -i E502.diff`

New description:

 To find errors: `flake8
 
--exclude=./django/utils/dictconfig.py,./django/contrib/comments/*,./django/utils/unittest.py,./tests/comment_tests/*,./django/test/_doctest.py
 --select=E502`

 Attaching a patch to get you started.

 Apply it:

 `patch -p1 -i E502.diff`

--

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

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

Re: [Django] #21268: pep8 cleanup: too many blank lines

2013-10-14 Thread Django

#21268: pep8 cleanup: too many blank lines
--+
 Reporter:  timo  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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:  1 |UI/UX:  0
--+
Changes (by timo):

 * easy:  0 => 1


Old description:

> To find errors: `flake8 --select=E303`
>
> Attaching a patch to get you started.
>
> Apply it:
>
> `patch -p1 -i E303.diff`

New description:

 To find errors: `flake8
 
--exclude=./django/utils/dictconfig.py,./django/contrib/comments/*,./django/utils/unittest.py,./tests/comment_tests/*,./django/test/_doctest.py
 --select=E303`

 Attaching a patch to get you started.

 Apply it:

 `patch -p1 -i E303.diff`

--

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

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

[Django] #21269: UnicodeDecodeError on makemessages -d djangojs

2013-10-14 Thread Django

#21269: UnicodeDecodeError on makemessages -d djangojs
--+
 Reporter:  kontakt@… |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  1.6-beta-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I'm getting an UnicodeDecodeError when running `makemessages -d djangojs
 -l de`.

 {{{
 processing locale de
 Traceback (most recent call last):
   File "/home/eike/public_html/test/env2/bin/django-admin.py", line 5, in
 
 management.execute_from_command_line()
   File "/home/eike/public_html/test/env2/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 397, in
 execute_from_command_line
 utility.execute()
   File "/home/eike/public_html/test/env2/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 390, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/eike/public_html/test/env2/lib/python2.7/site-
 packages/django/core/management/base.py", line 247, in run_from_argv
 stderr.write('%s: %s' % (e.__class__.__name__, e))
 UnicodeEncodeError: 'ascii' codec can't encode character u'\xd6' in
 position 47: ordinal not in range(128)
 }}}

 I'm using Python 2.7.5 and the latest beta. I tested this with Django 1.5
 too and it works without any problems.

-- 
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.32bef0e23b05a673084f0984d76be7c0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] d07d6a: Fixed #20910 -- Added a "snippet" sphinx directive...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d07d6ae1167f93f2e88b3743c070003a66a31b35
  
https://github.com/django/django/commit/d07d6ae1167f93f2e88b3743c070003a66a31b35
  Author: M Nasimul Haque 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M AUTHORS
M docs/_ext/djangodocs.py
M docs/_theme/djangodocs/static/djangodocs.css
M docs/intro/reusable-apps.txt
M docs/intro/tutorial01.txt
M docs/intro/tutorial02.txt
M docs/intro/tutorial03.txt
M docs/intro/tutorial04.txt
M docs/intro/tutorial05.txt
M docs/intro/tutorial06.txt

  Log Message:
  ---
  Fixed #20910 -- Added a "snippet" sphinx directive to allow prefixing a 
filename.

Thanks Marc Tamlyn for the suggestion.



-- 
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/525c2364c7aed_4519b3d543869a%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20910: Specify the filename (when appropriate) with code snippets

2013-10-14 Thread Django

#20910: Specify the filename (when appropriate) with code snippets
-+-
 Reporter:  jggramlich@… |Owner:  nsmgr8
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tutorial, afraid-|  Needs documentation:  0
  to-commit  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d07d6ae1167f93f2e88b3743c070003a66a31b35"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d07d6ae1167f93f2e88b3743c070003a66a31b35"
 Fixed #20910 -- Added a "snippet" sphinx directive to allow prefixing a
 filename.

 Thanks Marc Tamlyn for the suggestion.
 }}}

-- 
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/078.38fe1e2f927d6cbd225a4a15a884e614%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21258: Spanish locale should accept %Y-%m-%d format for dates

2013-10-14 Thread Django

#21258: Spanish locale should accept %Y-%m-%d format for dates
---+--
 Reporter:  pegler |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  invalid
 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 claudep):

 * resolution:  needsinfo => invalid


Comment:

 No problem, thanks for checking.

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

Re: [Django] #21022: Ensure URL naming is always preferred everywhere in the docs

2013-10-14 Thread Django

#21022: Ensure URL naming is always preferred everywhere in the docs
--+
 Reporter:  mjtamlyn  |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

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


Comment:

 @pkafei I'm going to deassign this ticket since there hasn't been any
 update from you in 5 weeks. Please let us know if you made any progress on
 it.

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

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

[Django] #21268: pep8 cleanup: too many blank lines

2013-10-14 Thread Django

#21268: pep8 cleanup: too many blank lines
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 To find errors: `flake8 --select=E303`

 Attaching a patch to get you started.

 Apply it:

 `patch -p1 -i E303.diff`

-- 
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/047.05ed8434b1ec7498d1a7d3115a3c56fc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21267: pep8 cleanup: the backslash is redundant between brackets

2013-10-14 Thread Django

#21267: pep8 cleanup: the backslash is redundant between brackets
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+
 To find errors: `flake8 --select=E502`

 Attaching a patch to get you started.

 Apply it:

 `patch -p1 -i E502.diff`

-- 
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/047.68b6a56f29ab92b6fcbe421699d82f5d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21266: pep8 cleanup: whitespace before/after parens and braces

2013-10-14 Thread Django

#21266: pep8 cleanup: whitespace before/after parens and braces
--+
 Reporter:  timo  |Owner:  larryone
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  flake8| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by larryone):

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


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

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

[Django] #21266: pep8 cleanup: whitespace before/after parens and braces

2013-10-14 Thread Django

#21266: pep8 cleanup: whitespace before/after parens and braces
+
   Reporter:  timo  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:  flake8
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 To find errors: `flake8 --select=E201,E202`

 Attaching a patch to get you started.

 Apply it:

 `patch -p1 -i E201.diff`

-- 
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/047.30e8a5631ea71ee17252393dff89ea24%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17193: Send templated email.

2013-10-14 Thread Django

#17193: Send templated email.
-+---
 Reporter:  tomchristie  |Owner:  julianapplebaum
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---

Comment (by anonymous):

 timo, does `html_message` parameter allow django templates to be used?

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

Re: [Django] #17193: Send templated email.

2013-10-14 Thread Django

#17193: Send templated email.
-+---
 Reporter:  tomchristie  |Owner:  julianapplebaum
 Type:  New feature  |   Status:  closed
Component:  Core (Mail)  |  Version:
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---
Changes (by timo):

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


Comment:

 Marking this as a duplicate of #20817 which added an `html_message`
 parameter to `send_mail()`.

-- 
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.8d44cc1585fd942fd29039e0da9dc183%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20962: Documentation on template tag render() methods is inconsistent with core tags.

2013-10-14 Thread Django

#20962: Documentation on template tag render() methods is inconsistent with core
tags.
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  afraid-to-commit |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"7f566fdb4c8453c8fa4b44d0fe5cc28472acc2ff"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f566fdb4c8453c8fa4b44d0fe5cc28472acc2ff"
 [1.6.x] Fixed #20962 -- Documented that template tag render() may raise
 exceptions.

 Thanks Keryn Knight for the report.

 Backport of e077224f4a 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/095.ebc3c62d0086394323fe1bc83de4e90f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7f62d7: [1.5.x] Fixed #20962 -- Documented that template t...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 7f62d794b303bedfd094742a84dcc8b85df3ba8b
  
https://github.com/django/django/commit/7f62d794b303bedfd094742a84dcc8b85df3ba8b
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M AUTHORS
M docs/howto/custom-template-tags.txt

  Log Message:
  ---
  [1.5.x] Fixed #20962 -- Documented that template tag render() may raise 
exceptions.

Thanks Keryn Knight for the report.

Backport of e077224f4a from master



-- 
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/525c13e8bbc44_6908779d5410339%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20962: Documentation on template tag render() methods is inconsistent with core tags.

2013-10-14 Thread Django

#20962: Documentation on template tag render() methods is inconsistent with core
tags.
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  afraid-to-commit |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Tim Graham ):

 In [changeset:"7f62d794b303bedfd094742a84dcc8b85df3ba8b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f62d794b303bedfd094742a84dcc8b85df3ba8b"
 [1.5.x] Fixed #20962 -- Documented that template tag render() may raise
 exceptions.

 Thanks Keryn Knight for the report.

 Backport of e077224f4a 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/095.e8afe02789f3eb54541a793981c46742%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7f566f: [1.6.x] Fixed #20962 -- Documented that template t...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 7f566fdb4c8453c8fa4b44d0fe5cc28472acc2ff
  
https://github.com/django/django/commit/7f566fdb4c8453c8fa4b44d0fe5cc28472acc2ff
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M AUTHORS
M docs/howto/custom-template-tags.txt

  Log Message:
  ---
  [1.6.x] Fixed #20962 -- Documented that template tag render() may raise 
exceptions.

Thanks Keryn Knight for the report.

Backport of e077224f4a from master



-- 
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/525c13ec9900c_1de5a77d586133a%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20962: Documentation on template tag render() methods is inconsistent with core tags.

2013-10-14 Thread Django

#20962: Documentation on template tag render() methods is inconsistent with core
tags.
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  closed
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:  fixed
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  afraid-to-commit |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"e077224f4ad69a68ae58a373ef69941272d3656c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e077224f4ad69a68ae58a373ef69941272d3656c"
 Fixed #20962 -- Documented that template tag render() may raise
 exceptions.

 Thanks Keryn Knight for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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/095.1e421b10a4b8052b71e2a1f7304f6b0b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e07722: Fixed #20962 -- Documented that template tag rende...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e077224f4ad69a68ae58a373ef69941272d3656c
  
https://github.com/django/django/commit/e077224f4ad69a68ae58a373ef69941272d3656c
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M AUTHORS
M docs/howto/custom-template-tags.txt

  Log Message:
  ---
  Fixed #20962 -- Documented that template tag render() may raise exceptions.

Thanks Keryn Knight for the report.



-- 
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/525c13aa9968d_1d8ee25d4c1216ab%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:  saoili
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by saoili):

 * owner:  anonymous => saoili


-- 
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/078.4439cd6b2ecada4f8c0826380c50e3b0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by anonymous):

 * owner:   => anonymous
 * 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/078.de309c404c0e9800cd2053ecba8c92e6%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by anonymous):

 * owner:  anonymous =>
 * 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/078.0a01513ae32a62d4a223b9eb3c48ab6c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21223: Add id_for_label in Django forms topic documentation

2013-10-14 Thread Django

#21223: Add id_for_label in Django forms topic documentation
-+-
 Reporter:  ebertti@…|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  form, afraid-to- |  Needs documentation:  0
  commit |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by saoili):

 * owner:  nobody => anonymous
 * 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/078.8040fc24593ace39f9c4dc60a70961c1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #5418: Add assertNoBrokenLinks() to test system

2013-10-14 Thread Django

#5418: Add assertNoBrokenLinks() to test system
-+-
 Reporter:  adrian   |Owner:
 Type:  New feature  |  unaizalakain
Component:  Testing framework|   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  feature  |   Resolution:
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by unaizalakain):

 * owner:  kkubasik => unaizalakain
 * 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.8cc6ecce3daa30587126dda5ff2ddbbe%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 8222a4: [1.6.x] Clarfied the ModelForm docs with respect t...

2013-10-14 Thread GitHub

Branch: refs/heads/stable/1.6.x
Home: https://github.com/django/django
Commit: 8222a48253e61f4d3c1d30156a5f9e0d59a7c56c

https://github.com/django/django/commit/8222a48253e61f4d3c1d30156a5f9e0d59a7c56c
Author: Loic Bistuer
Date: 2013-10-14 (Mon, 14 Oct 2013)

Changed paths:
M docs/topics/forms/modelforms.txt

Log Message:
---
[1.6.x] Clarfied the ModelForm docs with respect to generated vs. declared
fields.

The ModelForm docs suggested that fields defined declaratively override
default fields generated from the form Meta.

This is conceptually wrong, especially with inheritance in mind. Meta is
usually defined on the topmost ModelForm subclass, while fields can come
from anywhere in the MRO, especially base classes; therefore we suggested
that something defined in a base class override something from a subclass.

This patch rephrases the docs around the idea that Meta is used to generate
*missing* fields.

Refs #8620, #19617.

Thanks @mjtamlyn and @timgraham for the review.

Backport of 54cd930baf from master

--
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/525c0602217d3_49ab77d4863395%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

2013-10-14 Thread Django

Comment (by Tim Graham ):

In [changeset:"8222a48253e61f4d3c1d30156a5f9e0d59a7c56c"]:
{{{
#!CommitTicketReference repository=""
revision="8222a48253e61f4d3c1d30156a5f9e0d59a7c56c"
[1.6.x] Clarfied the ModelForm docs with respect to generated vs. declared
fields.

The ModelForm docs suggested that fields defined declaratively override
default fields generated from the form Meta.

This patch rephrases the docs around the idea that Meta is used to
generate
*missing* fields.

Refs #8620, #19617.

Thanks @mjtamlyn and @timgraham for the review.

Backport of 54cd930baf 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.17578d068c55575fdc88ac1f8d9dc04f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 54cd93: Clarfied the ModelForm docs with respect to genera...

2013-10-14 Thread GitHub

Branch: refs/heads/master
Home: https://github.com/django/django
Commit: 54cd930baf49c45e3e91338a9f4a56d19090ff25

https://github.com/django/django/commit/54cd930baf49c45e3e91338a9f4a56d19090ff25
Author: Loic Bistuer
Date: 2013-10-14 (Mon, 14 Oct 2013)

Changed paths:
M docs/topics/forms/modelforms.txt

Log Message:
---
Clarfied the ModelForm docs with respect to generated vs. declared fields.

The ModelForm docs suggested that fields defined declaratively override
default fields generated from the form Meta.

This patch rephrases the docs around the idea that Meta is used to generate
*missing* fields.

Refs #8620, #19617.

Thanks @mjtamlyn and @timgraham for the review.

--
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/525c05e4aa666_6cca68bd481231ed%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19617: mixins on ModelForms

2013-10-14 Thread Django

Comment (by Tim Graham ):

The ModelForm docs suggested that fields defined declaratively override
default fields generated from the form Meta.

This patch rephrases the docs around the idea that Meta is used to
generate
*missing* fields.

Refs #8620, #19617.

Thanks @mjtamlyn and @timgraham for the review.

Backport of 54cd930baf 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.91482d9523ba0eab3bb074a77981e657%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8620: ModelForm.Meta.exclude only excludes model fields, not form fields

2013-10-14 Thread Django

Comment (by Tim Graham ):

In [changeset:"54cd930baf49c45e3e91338a9f4a56d19090ff25"]:
{{{
#!CommitTicketReference repository=""
revision="54cd930baf49c45e3e91338a9f4a56d19090ff25"
Clarfied the ModelForm docs with respect to generated vs. declared fields.

The ModelForm docs suggested that fields defined declaratively override
default fields generated from the form Meta.

This patch rephrases the docs around the idea that Meta is used to
generate
*missing* fields.

Refs #8620, #19617.

Thanks @mjtamlyn and @timgraham 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/064.c499bf9584ed2e2a16556b0903e8a4b1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19617: mixins on ModelForms

2013-10-14 Thread Django

Comment (by Tim Graham ):

The ModelForm docs suggested that fields defined declaratively override
default fields generated from the form Meta.

This patch rephrases the docs around the idea that Meta is used to
generate
*missing* fields.

Refs #8620, #19617.

Thanks @mjtamlyn and @timgraham 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/065.370a70868e40fc51873de3b93de4037a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21210: Custom template tags documentation should note that a restart of runserver is neede after creating the templatetags directory

2013-10-14 Thread Django

#21210: Custom template tags documentation should note that a restart of 
runserver
is neede after creating the templatetags directory
--+
 Reporter:  gergely@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"5c1be8a870f9783c4164cf09b1e9db3205ad1f1e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c1be8a870f9783c4164cf09b1e9db3205ad1f1e"
 [1.5.x] Fixed #21210 -- Documented when runserver doesn't auto-restart.

 Thanks gergely at polonkai.eu for the suggestion.

 Backport of 9b7d38ed5a 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/077.77f7b8f1cff5a1b9aab9773f9542375b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21210: Custom template tags documentation should note that a restart of runserver is neede after creating the templatetags directory

2013-10-14 Thread Django

#21210: Custom template tags documentation should note that a restart of 
runserver
is neede after creating the templatetags directory
--+
 Reporter:  gergely@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"da181056a9e111c7564127cb67df6f186a485c17"]:
 {{{
 #!CommitTicketReference repository=""
 revision="da181056a9e111c7564127cb67df6f186a485c17"
 [1.6.x] Fixed #21210 -- Documented when runserver doesn't auto-restart.

 Thanks gergely at polonkai.eu for the suggestion.

 Backport of 9b7d38ed5a 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/077.1ad463938bf55dbf29d72e3e371e333f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5c1be8: [1.5.x] Fixed #21210 -- Documented when runserver ...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5c1be8a870f9783c4164cf09b1e9db3205ad1f1e
  
https://github.com/django/django/commit/5c1be8a870f9783c4164cf09b1e9db3205ad1f1e
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/intro/tutorial01.txt
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.5.x] Fixed #21210 -- Documented when runserver doesn't auto-restart.

Thanks gergely at polonkai.eu for the suggestion.

Backport of 9b7d38ed5a from master



-- 
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/525c01f13b1be_6cca68bd48122580%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] da1810: [1.6.x] Fixed #21210 -- Documented when runserver ...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: da181056a9e111c7564127cb67df6f186a485c17
  
https://github.com/django/django/commit/da181056a9e111c7564127cb67df6f186a485c17
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/intro/tutorial01.txt
M docs/ref/django-admin.txt

  Log Message:
  ---
  [1.6.x] Fixed #21210 -- Documented when runserver doesn't auto-restart.

Thanks gergely at polonkai.eu for the suggestion.

Backport of 9b7d38ed5a from master



-- 
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/525c01ef8672_278cda1d58390f%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21210: Custom template tags documentation should note that a restart of runserver is neede after creating the templatetags directory

2013-10-14 Thread Django

#21210: Custom template tags documentation should note that a restart of 
runserver
is neede after creating the templatetags directory
--+
 Reporter:  gergely@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9b7d38ed5a9eed21c496abb1b874cfe53da9c9c9"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9b7d38ed5a9eed21c496abb1b874cfe53da9c9c9"
 Fixed #21210 -- Documented when runserver doesn't auto-restart.

 Thanks gergely at polonkai.eu for the suggestion.
 }}}

-- 
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/077.149f360dd7ef6a29f977e803676f9984%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 9b7d38: Fixed #21210 -- Documented when runserver doesn't ...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9b7d38ed5a9eed21c496abb1b874cfe53da9c9c9
  
https://github.com/django/django/commit/9b7d38ed5a9eed21c496abb1b874cfe53da9c9c9
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/intro/tutorial01.txt
M docs/ref/django-admin.txt

  Log Message:
  ---
  Fixed #21210 -- Documented when runserver doesn't auto-restart.

Thanks gergely at polonkai.eu for the suggestion.



-- 
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/525c0175f2d66_6912507d50906d9%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21258: Spanish locale should accept %Y-%m-%d format for dates

2013-10-14 Thread Django

#21258: Spanish locale should accept %Y-%m-%d format for dates
---+--
 Reporter:  pegler |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by pegler):

 Sorry, I mistakenly checked against 1.4, not 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.b0b9b7c12e568b2275dcc7f6e2254b4e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2013-10-14 Thread Django

#21231: Limiting the number of variables and files that a POST request can
contain
---+--
Reporter: epandurski@… |Owner: nobody
Type: New feature| Status: closed
Component: HTTP handling | Version: master
Severity: Normal | Resolution: needsinfo
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 mjtamlyn):

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

Comment:

Ok, I'm going to close this for now, largely as I agree with Aymeric that
this will likely be exceedingly difficult (if possible) to implement in
python, and I personally don't see it as a major weakness as it can be
managed fairly easily by nginx or a similar web server.

If you do at some point write a patch which manages this directly in
Django, please feel free to reopen this issue with a concrete patch and
we'll see what happens.

--
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/078.cc97831a734e6a6b15e64c84f48ff17a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21230: Remove usage of direct settings manipulation in Django's tests

2013-10-14 Thread Django

#21230: Remove usage of direct settings manipulation in Django's tests
--+
 Reporter:  akaariai  |Owner:  Sephi
 Type:  Cleanup/optimization  |   Status:  assigned
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:  1 |UI/UX:  0
--+

Comment (by bouke):

 I started off with some changes (mostly low hanging fruits), as for some
 cases the manipulations are very concise. See the PR:
 https://github.com/django/django/pull/1739

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

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

2013-10-14 Thread Django

#21231: Limiting the number of variables and files that a POST request can 
contain
---+--
 Reporter:  epandurski@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by epandurski@…):

 I do not have a patch, and probably will not have soon, if ever. I
 discovered this problem while I was analysing the possible weaknesses of a
 web-app of mine that *may in the future* be installed as a business
 critical web-app (http://sourceforge.net/projects/cmb/).

 So I decided to report my findings.

-- 
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/078.7de5a1f7cc82a4e01edaa9b9fbfeb412%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19740: Make sure only posts not marked as defunct show up in feed

2013-10-14 Thread Django

#19740: Make sure only posts not marked as defunct show up in feed
-+
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  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 Aymeric Augustin ):

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


Comment:

 In
 [changeset:"f4ce13eb3c4f79632bf62f17584d4d2a582db490/djangoproject.com"]:
 {{{
 #!CommitTicketReference repository="djangoproject.com"
 revision="f4ce13eb3c4f79632bf62f17584d4d2a582db490"
 Merge pull request #60 from django/19740a

 Fixed #19740 -- Ensured that denied feeds are unsubscribed.
 }}}

-- 
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.822a2acc7213503e25b7f7d34d4c5e77%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19740: Make sure only posts not marked as defunct show up in feed

2013-10-14 Thread Django

#19740: Make sure only posts not marked as defunct show up in feed
-+
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  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
-+

Comment (by timo):

 Thanks, I've updated both per your comments.

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

Re: [Django] #19740: Make sure only posts not marked as defunct show up in feed

2013-10-14 Thread Django

#19740: Make sure only posts not marked as defunct show up in feed
-+
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  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
-+

Comment (by brutasse):

 @timo I just commented on both PRs.

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

Re: [Django] #18866: model Meta verbose_name too long error message not obvious

2013-10-14 Thread Django

#18866: model Meta verbose_name too long error message not obvious
--+
 Reporter:  elena |Owner:  toyg
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 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 joaoxsouls ):

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


Comment:

 In [changeset:"1ab27e9a65015373a49688f3ff6723cf85d5de56"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ab27e9a65015373a49688f3ff6723cf85d5de56"
 Fixed #18866 -- added validation error for verbose_name longer than 39
 characters

 Added a validation error check when creating the permissions for model, to
 avoid
 cryptic database error when the verbose_name is longer than 39 characters
 thanks elena for reporting it
 }}}

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

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

[django/django] 1ab27e: Fixed #18866 -- added validation error for verbose...

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1ab27e9a65015373a49688f3ff6723cf85d5de56
  
https://github.com/django/django/commit/1ab27e9a65015373a49688f3ff6723cf85d5de56
  Author: joaoxsouls 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M AUTHORS
M django/contrib/auth/management/__init__.py
M django/contrib/auth/tests/test_management.py

  Log Message:
  ---
  Fixed #18866 -- added validation error for verbose_name longer than 39 
characters

Added a validation error check when creating the permissions for model, to avoid
cryptic database error when the verbose_name is longer than 39 characters
thanks elena for reporting it


  Commit: 8ce3c3a9282ac19282060ddf6928b34a09d26672
  
https://github.com/django/django/commit/8ce3c3a9282ac19282060ddf6928b34a09d26672
  Author: Marc Tamlyn 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M AUTHORS
M django/contrib/auth/management/__init__.py
M django/contrib/auth/tests/test_management.py

  Log Message:
  ---
  Merge pull request #1733 from joaoxsouls/#18866

Fixed #18866 -- added validation error for verbose_name longer than 39 
characters


Compare: https://github.com/django/django/compare/8fc63087f6ad...8ce3c3a9282a

-- 
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/525befbc411e9_6cca68bd4811383f%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18866: model Meta verbose_name too long error message not obvious

2013-10-14 Thread Django

#18866: model Meta verbose_name too long error message not obvious
--+
 Reporter:  elena |Owner:  toyg
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Marc Tamlyn ):

 In [changeset:"8ce3c3a9282ac19282060ddf6928b34a09d26672"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8ce3c3a9282ac19282060ddf6928b34a09d26672"
 Merge pull request #1733 from joaoxsouls/#18866

 Fixed #18866 -- added validation error for verbose_name longer than 39
 characters
 }}}

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

Re: [Django] #19740: Make sure only posts not marked as defunct show up in feed

2013-10-14 Thread Django

#19740: Make sure only posts not marked as defunct show up in feed
-+
 Reporter:  aaugustin|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  *.djangoproject.com  |  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 timo):

 * has_patch:  0 => 1


Comment:

 Here's an untested [https://github.com/django/djangoproject.com/pull/60
 PR].

 Also a [https://github.com/django/djangoproject.com/pull/59 related
 cleanup ] to remove `is_defunct`.

-- 
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.586ce96eea967b63041d1d589cb1ec2c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21230: Remove usage of direct settings manipulation in Django's tests

2013-10-14 Thread Django

#21230: Remove usage of direct settings manipulation in Django's tests
--+
 Reporter:  akaariai  |Owner:  Sephi
 Type:  Cleanup/optimization  |   Status:  assigned
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:  1 |UI/UX:  0
--+

Comment (by bouke):

 The listed `git grep` didn't work for me (Git 1.8.2.2 on OS X), but `git
 grep 'settings\.[a-zA-Z_]* ='` provides a starting point.

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

Re: [Django] #20962: Documentation on template tag render() methods is inconsistent with core tags.

2013-10-14 Thread Django

#20962: Documentation on template tag render() methods is inconsistent with core
tags.
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Documentation| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  afraid-to-commit |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by bouke):

 * has_patch:  0 => 1


Comment:

 I've proposed a change in this PR:
 https://github.com/django/django/pull/1737.

-- 
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/095.ff3e63b38a71c7c144c6c4134eff6ead%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21210: Custom template tags documentation should note that a restart of runserver is neede after creating the templatetags directory

2013-10-14 Thread Django

#21210: Custom template tags documentation should note that a restart of 
runserver
is neede after creating the templatetags directory
--+
 Reporter:  gergely@… |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by bouke):

 * has_patch:  0 => 1


Comment:

 Submitted my second Django PR:
 [https://github.com/django/django/pull/1736]

-- 
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/077.f9de60a80038b55060228e8cc253a905%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21264: RST error in docs at /dev/topics/class-based-views

2013-10-14 Thread Django

#21264: RST error in docs at /dev/topics/class-based-views
--+
 Reporter:  EvilDMP   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | 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:"e3c8db61f3d1e86ac523fc76095d7f3dd1cbe760"]:
 {{{
 #!CommitTicketReference repository=""
 revision="e3c8db61f3d1e86ac523fc76095d7f3dd1cbe760"
 [1.6.x] Fixed #21264 -- Incorrect RST usage in docs

 Backport of 8fc63087f6 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.7b779e95d4f7c546f0337ee6864bafc5%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e3c8db: [1.6.x] Fixed #21264 -- Incorrect RST usage in doc...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: e3c8db61f3d1e86ac523fc76095d7f3dd1cbe760
  
https://github.com/django/django/commit/e3c8db61f3d1e86ac523fc76095d7f3dd1cbe760
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/topics/class-based-views/index.txt
M docs/topics/http/shortcuts.txt

  Log Message:
  ---
  [1.6.x] Fixed #21264 -- Incorrect RST usage in docs

Backport of 8fc63087f6 from master



-- 
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/525be0a6ec410_4519b3d542118f%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b26848: [1.5.x] Fixed #21264 -- Incorrect RST usage in doc...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: b268488806bd0cbfd29a874069ece89f61585935
  
https://github.com/django/django/commit/b268488806bd0cbfd29a874069ece89f61585935
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/topics/class-based-views/index.txt
M docs/topics/http/shortcuts.txt

  Log Message:
  ---
  [1.5.x] Fixed #21264 -- Incorrect RST usage in docs

Backport of 8fc63087f6 from master



-- 
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/525be0c96bef1_45b54bd48304cf%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21264: RST error in docs at /dev/topics/class-based-views

2013-10-14 Thread Django

#21264: RST error in docs at /dev/topics/class-based-views
--+
 Reporter:  EvilDMP   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | 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:"b268488806bd0cbfd29a874069ece89f61585935"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b268488806bd0cbfd29a874069ece89f61585935"
 [1.5.x] Fixed #21264 -- Incorrect RST usage in docs

 Backport of 8fc63087f6 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.5e9cf7c1ecdef2481a2136627069e87e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21264: RST error in docs at /dev/topics/class-based-views

2013-10-14 Thread Django

#21264: RST error in docs at /dev/topics/class-based-views
--+
 Reporter:  EvilDMP   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  fixed
 Keywords:  afraid-to-commit  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8fc63087f6ad888b68dff17ee0c527774332d932"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8fc63087f6ad888b68dff17ee0c527774332d932"
 Fixed #21264 -- Incorrect RST usage in docs
 }}}

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

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

[django/django] 8fc630: Fixed #21264 -- Incorrect RST usage in docs

2013-10-14 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8fc63087f6ad888b68dff17ee0c527774332d932
  
https://github.com/django/django/commit/8fc63087f6ad888b68dff17ee0c527774332d932
  Author: Bouke Haarsma 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/topics/class-based-views/index.txt
M docs/topics/http/shortcuts.txt

  Log Message:
  ---
  Fixed #21264 -- Incorrect RST usage in docs



-- 
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/525be044b2be8_26c71433d4c50099%40hookshot-fe2-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21265: on_update foreign key

2013-10-14 Thread Django

#21265: on_update foreign key
-+-
 Reporter:  mirzadelic1@…|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  on_dalete,   |  Unreviewed
  foreignkey |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 Sorry, this isn't a support channel. Try to ask for help at #django IRC
 channel or django-users 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/079.c21082f61ea9033df54bece4d147c658%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20928: djangoproject.com is no longer picking up the Django Packages RSS feed

2013-10-14 Thread Django

#20928: djangoproject.com is no longer picking up the Django Packages RSS feed
-+
 Reporter:  pydanny  |Owner:  jezdez
 Type:  Bug  |   Status:  closed
Component:  *.djangoproject.com  |  Version:
 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 timo):

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


Comment:

 Following deployment of the PR above, a package update has now appeared in
 our feed.

-- 
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.467054281f85809eb634c37b69b94ed9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] e532d1: [1.5.x] Fixed #21027 -- Updated tutorial 5 docs to...

2013-10-14 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: e532d1e38f30689f6483ee5fd580eaf8d08a6b1e
  
https://github.com/django/django/commit/e532d1e38f30689f6483ee5fd580eaf8d08a6b1e
  Author: Max Vizard 
  Date:   2013-10-14 (Mon, 14 Oct 2013)

  Changed paths:
M docs/intro/tutorial05.txt

  Log Message:
  ---
  [1.5.x] Fixed #21027 -- Updated tutorial 5 docs to link to management shell 
command page.

Backport of 13ddf0e002 from master



-- 
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/525bdf54993c_1cf112b5d5889923%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

1 2 >

1 - 100 of 137 matches

Mail list logo