date:20130629

Re: [Django] #8060: ncxbadmtyszd (was: Admin Inlines do not respect user permissions)

2013-06-29 Thread Django

#8060: ncxbadmtyszd
---+
 Reporter:  p.patruno@…|Owner:  sjaensch
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  gdjbpwwordot   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by rlnrdtcmnncv):

 * keywords:  inlines User authentication => gdjbpwwordot


Comment:

 thanks for a great post vantzlyrvb http://www.whlwshckmivd.com";>click here >:O wdtwaoj, :-X
 jaspphundx [url="http://www.whlwshckmivd.net"]or here[/url] :-0 afhqrhlv,
 :-0 lmzwiwpirg http://whlwshckmivd.info :-/ afhqrhlv, B| btgcmbhacx
 [url=http://whlwshckmivd.ru]gmotdnurve[/url] >:-O xminz, :-D zvqmlnymmk
 [link=http://whlwshckmivd.se]rapuqnuzjr[/link] :V wdtwaoj, =(

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

Re: [Django] #20667: Remove discussion of DEBUG from the tutorial

2013-06-29 Thread Django

#20667: Remove discussion of DEBUG from the tutorial
--+
 Reporter:  sosdog88@…|Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timo):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #20673: Improve HttpRequest.user documentation

2013-06-29 Thread Django

#20673: Improve HttpRequest.user documentation
--+
 Reporter:  littlepig |Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.5
 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 susan):

 To be honest, I'm not entirely sure what the docstring needs to be in
 "contrib.auth.backends.ModelBackend". Can someone point me in the right
 direction?

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

Re: [Django] #20663: Admin Now and Today buttons use confusing time / timezone

2013-06-29 Thread Django

#20663: Admin Now and Today buttons use confusing time / timezone
---+-
 Reporter:  imfletcher |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+-

Comment (by ramiro):

 See #7717, #14253 and #18768 for some previous, related discussion about
 the topic.

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

Re: [Django] #12493: settings.configure silently allows TEMPLATE_DIRS configuration error

2013-06-29 Thread Django

#12493: settings.configure silently allows TEMPLATE_DIRS configuration error
--+
 Reporter:  mckoss|Owner:  gwilson
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  1.1
 Severity:  Normal|   Resolution:  fixed
 Keywords:  settings, templates   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Ramiro Morales ):

 In [changeset:"64cdea68e71829905da6374a066d1700375255ec"]:
 {{{
 #!CommitTicketReference repository=""
 revision="64cdea68e71829905da6374a066d1700375255ec"
 Report wrongly-typed settings and abort, as originally planned.

 Thanks Claude for the heads up. Refs #12493 and commit 5e08b792.
 }}}

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

[django/django] 64cdea: Report wrongly-typed settings and abort, as origin...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 64cdea68e71829905da6374a066d1700375255ec
  
https://github.com/django/django/commit/64cdea68e71829905da6374a066d1700375255ec
  Author: Ramiro Morales 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/conf/__init__.py

  Log Message:
  ---
  Report wrongly-typed settings and abort, as originally planned.

Thanks Claude for the heads up. Refs #12493 and commit 5e08b792.



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

[django/django] d51b77: Removed django.contrib.auth.views.password_reset_c...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d51b7794bfd1ddfd92f71f71d07daf931421c5f7
  
https://github.com/django/django/commit/d51b7794bfd1ddfd92f71f71d07daf931421c5f7
  Author: Ramiro Morales 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/auth/tests/test_views.py
M django/contrib/auth/urls.py
M django/contrib/auth/views.py

  Log Message:
  ---
  Removed django.contrib.auth.views.password_reset_confirm_uidb36() view to 
finish its accelerated deprecation schedule.


  Commit: 5e3a6532aab7bf51aa5857c3de9479a7be0c2ae4
  
https://github.com/django/django/commit/5e3a6532aab7bf51aa5857c3de9479a7be0c2ae4
  Author: Ramiro Morales 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/auth/tests/test_views.py
M django/contrib/auth/urls.py
M django/contrib/auth/views.py

  Log Message:
  ---
  Merge pull request #1316 from ramiro/int_pk_pwd_reset


Compare: https://github.com/django/django/compare/3fd0ee5b4680...5e3a6532aab7

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

Re: [Django] #20662: Embedding views in templates

2013-06-29 Thread Django

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

Comment:

An ajax view still returns a complete HTTP response. And I'm confused as
to how you would want that rendered in a template. If you want a tag that
renders a (sub)-template, that's called an inclusion tag
(https://docs.djangoproject.com/en/1.5/howto/custom-template-tags
/#inclusion-tags). Without specifics I have no idea what you are referring
to when you say you see an anti-pattern of pretty much the same code
duplicated under different names in different project, nor how some sort
of "render it" tag would fix that. Possibly you should take this
discussion to the django-developers mailing list to get feedback from
others; I'm sorry but what you are asking for here isn't making sense to
me.

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

Re: [Django] #20662: Embedding views in templates

2013-06-29 Thread Django

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

Comment:

What about ajax views? Think of the render_view using only ajax-natured
views: those returning partial content.

Let's rephrase that, if "view" doesn't make enough sense, and use
"function" instead of "view".

What I'm seeing as an anti-pattern, is the pretty-much-same code being
duplicated under different tag names in different projects. And I'd say
the "right" way is not that hard: Have a simple function/view/whatever-
suits renderer tag!

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

Re: [Django] #20662: Embedding views in templates

2013-06-29 Thread Django

#20662: Embedding views in templates
-+-
 Reporter:  Mehran Kholdi|Owner:  nobody
   |   Status:  closed
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kmtracey):

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


Comment:

 Django views take an HTTP request and return an HTTP response. A full HTTP
 response, including status code and headers, not a snippet of rendered
 HTML to fill in part of a complete response. Since views return full HTTP
 responses I don't see how a render_view template tag can make sense; you
 cannot embed a full HTTP response as part of a template you are rendering.
 If you want to do advanced processing of some sort in a re-usable way in
 your application, the way to do that is with a custom template tag.

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

Re: [Django] #20677: generic_inlineformset_factory details incorrect

2013-06-29 Thread Django

#20677: generic_inlineformset_factory details incorrect
+
 Reporter:  Riley Strong   |  Owner:  nobody
 Type:  Bug | Status:  closed
Component:  contrib.contenttypes|Version:  1.5
 Severity:  Normal  | Resolution:  fixed
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  1
UI/UX:  0   |
+

Comment (by Tim Graham ):

 In [changeset:"62a9abeff05e4af61878bff7ff615cd298cf0d7e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="62a9abeff05e4af61878bff7ff615cd298cf0d7e"
 [1.5.x] Fixed #20677 - Typos in generic_inlineformset_factory docs.

 Thanks Riley Strong for the report.

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

[django/django] 62a9ab: [1.5.x] Fixed #20677 - Typos in generic_inlineform...

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 62a9abeff05e4af61878bff7ff615cd298cf0d7e
  
https://github.com/django/django/commit/62a9abeff05e4af61878bff7ff615cd298cf0d7e
  Author: Tim Graham 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/contenttypes/generic.py
M docs/ref/contrib/contenttypes.txt

  Log Message:
  ---
  [1.5.x] Fixed #20677 - Typos in generic_inlineformset_factory docs.

Thanks Riley Strong for the report.

Backport of 3fd0ee5b46 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/51cf24cec5e86_b3af6bddc2329%40hookshot-fe6-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20677: generic_inlineformset_factory details incorrect

2013-06-29 Thread Django

#20677: generic_inlineformset_factory details incorrect
+
 Reporter:  Riley Strong   |  Owner:  nobody
 Type:  Bug | Status:  closed
Component:  contrib.contenttypes|Version:  1.5
 Severity:  Normal  | Resolution:  fixed
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  1
UI/UX:  0   |
+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"b930733a67cbc1235daf675de06d73e3b6406113"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b930733a67cbc1235daf675de06d73e3b6406113"
 [1.6.x] Fixed #20677 - Typos in generic_inlineformset_factory docs.

 Thanks Riley Strong for the report.

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

[django/django] b93073: [1.6.x] Fixed #20677 - Typos in generic_inlineform...

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b930733a67cbc1235daf675de06d73e3b6406113
  
https://github.com/django/django/commit/b930733a67cbc1235daf675de06d73e3b6406113
  Author: Tim Graham 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/contenttypes/generic.py
M docs/ref/contrib/contenttypes.txt

  Log Message:
  ---
  [1.6.x] Fixed #20677 - Typos in generic_inlineformset_factory docs.

Thanks Riley Strong for the report.

Backport of 3fd0ee5b46 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/51cf249b5cd21_3ee9f47dd8676d4%40hookshot-fe3-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 3fd0ee: Fixed #20677 - Typos in generic_inlineformset_fact...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3fd0ee5b46807c18c731045b4f5b360b5b091c61
  
https://github.com/django/django/commit/3fd0ee5b46807c18c731045b4f5b360b5b091c61
  Author: Tim Graham 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/contenttypes/generic.py
M docs/ref/contrib/contenttypes.txt

  Log Message:
  ---
  Fixed #20677 - Typos in generic_inlineformset_factory docs.

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

[Django] #20677: generic_inlineformset_factory details incorrect

2013-06-29 Thread Django

#20677: generic_inlineformset_factory details incorrect
+
 Reporter:  Riley Strong   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  contrib.contenttypes|Version:  1.5
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 
https://docs.djangoproject.com/en/1.5/ref/contrib/contenttypes/#django.contrib.contenttypes.generic.generic_inlineformset_factory

 Reads:
 > You must provide `ct_field` and '''`object_id`''' if they different from
 the defaults, `content_type` and `object_id` respectively.
 (emphasis added)

 1.  The bolded  `object_id` should be `fk_field`.
 2.  Should read "if they are different from the defaults"

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

[django/django] 741517: Simplified description of HttpResponse()

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 74151765073ce280cc5df0bfe411971c6212a0ff
  
https://github.com/django/django/commit/74151765073ce280cc5df0bfe411971c6212a0ff
  Author: Aymeric Augustin 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M docs/ref/request-response.txt

  Log Message:
  ---
  Simplified description of HttpResponse()

Related to 8b9b8d3b.



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

Re: [Django] #6527: A bug in HttpResponse with iterators

2013-06-29 Thread Django

#6527: A bug in HttpResponse  with iterators
-+-
 Reporter:  daonb   |Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  http iterators   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"8b9b8d3bda09eb1b447631182d06c6c5e51425f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b9b8d3bda09eb1b447631182d06c6c5e51425f6"
 Removed compatibility code for streaming responses.

 This code provided a deprecation path for old-style streaming responses.

 Refs #6527, #7581.
 }}}

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

Re: [Django] #7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse objects.

2013-06-29 Thread Django

#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-+-
 Reporter:  mrmachine|Owner:  ccahoon
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  stream HttpResponse  | Triage Stage:  Accepted
  Content-Length |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"8b9b8d3bda09eb1b447631182d06c6c5e51425f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b9b8d3bda09eb1b447631182d06c6c5e51425f6"
 Removed compatibility code for streaming responses.

 This code provided a deprecation path for old-style streaming responses.

 Refs #6527, #7581.
 }}}

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

[django/django] 8b9b8d: Removed compatibility code for streaming responses...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8b9b8d3bda09eb1b447631182d06c6c5e51425f6
  
https://github.com/django/django/commit/8b9b8d3bda09eb1b447631182d06c6c5e51425f6
  Author: Aymeric Augustin 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/http/__init__.py
M django/http/response.py
M django/views/static.py
M tests/httpwrappers/tests.py

  Log Message:
  ---
  Removed compatibility code for streaming responses.

This code provided a deprecation path for old-style streaming responses.

Refs #6527, #7581.


  Commit: acd7b34aafe352ef604edcb73f75041c5cbba6b9
  
https://github.com/django/django/commit/acd7b34aafe352ef604edcb73f75041c5cbba6b9
  Author: Aymeric Augustin 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/conf/urls/shortcut.py
M django/contrib/admin/options.py
M django/contrib/admin/views/main.py
M django/contrib/comments/__init__.py
M django/contrib/comments/templatetags/comments.py
M django/contrib/contenttypes/generic.py
M django/db/__init__.py
M django/db/backends/creation.py
M django/db/models/fields/related.py
M django/db/models/manager.py
M django/db/models/options.py
M django/db/transaction.py
M django/db/utils.py
M django/forms/forms.py
M django/forms/models.py
M django/forms/widgets.py
M django/middleware/cache.py
M django/middleware/common.py
M django/middleware/doc.py
M django/middleware/transaction.py
M django/template/defaulttags.py
M django/test/_doctest.py
M django/test/simple.py
M django/utils/image.py
M django/views/defaults.py
M django/views/generic/edit.py
M tests/admin_scripts/app_with_import/models.py
M tests/admin_scripts/tests.py
M tests/cache/tests.py
M tests/deprecation/tests.py
M tests/generic_views/test_edit.py
M tests/middleware/tests.py
M tests/model_forms/tests.py
M tests/model_forms_regress/tests.py
M tests/runtests.py
M tests/template_tests/tests.py
M tests/test_runner/tests.py
M tests/test_suite_override/tests.py
M tests/test_utils/tests.py
M tests/transactions/tests.py
M tests/transactions_regress/tests.py

  Log Message:
  ---
  Advanced deprecation warnings for Django 1.7.


Compare: https://github.com/django/django/compare/59b0c48ce279...acd7b34aafe3

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

Re: [Django] #18592: Provide failure recovery for undocumented "_last_executed" in MySQLdb's cursor

2013-06-29 Thread Django

#18592: Provide failure recovery for undocumented "_last_executed" in MySQLdb's
cursor
-+-
 Reporter:  reames@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by Claude Paroz ):

 In [changeset:"59be2c6875eaf744798d14c9dc8498552c8d48d5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="59be2c6875eaf744798d14c9dc8498552c8d48d5"
 [1.6.x] Fixed #18592 -- Prevented crash when accessing MySQL
 _last_executed

 Thanks reames at asymmetricventures.com for the report.
 Backport of 59b0c48ce 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/087.25b8c6fc99b6ffa47126bfde836d927b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 59be2c: [1.6.x] Fixed #18592 -- Prevented crash when acces...

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 59be2c6875eaf744798d14c9dc8498552c8d48d5
  
https://github.com/django/django/commit/59be2c6875eaf744798d14c9dc8498552c8d48d5
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/db/backends/mysql/base.py
M tests/backends/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #18592 -- Prevented crash when accessing MySQL _last_executed

Thanks reames at asymmetricventures.com for the report.
Backport of 59b0c48ce 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/51cf102c57c19_63bec7bdd43175b%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 59b0c4: Fixed #18592 -- Prevented crash when accessing MyS...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 59b0c48ce27951048146358739baf08056c5e821
  
https://github.com/django/django/commit/59b0c48ce27951048146358739baf08056c5e821
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/db/backends/mysql/base.py
M tests/backends/tests.py

  Log Message:
  ---
  Fixed #18592 -- Prevented crash when accessing MySQL _last_executed

Thanks reames at asymmetricventures.com 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/51cf0faa4f008_639a541dd455247%40hookshot-fe4-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18592: Provide failure recovery for undocumented "_last_executed" in MySQLdb's cursor

2013-06-29 Thread Django

#18592: Provide failure recovery for undocumented "_last_executed" in MySQLdb's
cursor
-+-
 Reporter:  reames@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"59b0c48ce27951048146358739baf08056c5e821"]:
 {{{
 #!CommitTicketReference repository=""
 revision="59b0c48ce27951048146358739baf08056c5e821"
 Fixed #18592 -- Prevented crash when accessing MySQL _last_executed

 Thanks reames at asymmetricventures.com 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/087.306db1fad1d4b72dff04d74b3a56ef4a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20676: Wrong users highlighted as core devs in trac

2013-06-29 Thread Django

* has_patch: 0 => 1

Comment:

After digging a bit deeper into this issue, I'm starting to think the only
sane fix would be to make everone named Alex a core developer...

The problem we have is that trac sometimes likes to use the full name of a
user instead of his/her username when displaying a comment.
This means that we can't check reliably whether a user is a core dev or
not.

I "improved" the username-extracting code to reject everything containing
an "@" character.
This won't fix the core issue, but it should at least get rid of the false
positives.

I hope you enjoyed your "core dev" highlight while it lasted ;)

https://github.com/django/code.djangoproject.com/pull/7

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

Re: [Django] #20676: Wrong users highlighted as core devs in trac

2013-06-29 Thread Django

#20676: Wrong users highlighted as core devs in trac
-+-
 Reporter:  alexcouper   |Owner:  bmispelon
 Type:  Bug  |   Status:  assigned
Component:  *.djangoproject.com  |  Version:  1.5
 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 aaugustin):

 Computer.

 :D

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

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-29 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
-+-
 Reporter:  stanislas.guerra@…   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  FileField delete |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"b6aed803b20cc7898a82fd65845e97676276f3fa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b6aed803b20cc7898a82fd65845e97676276f3fa"
 [1.6.x] Fixed #20660 -- Do not try to delete an unset FieldFile

 Thanks stanislas.guerra at gmail.com for the report and
 Baptiste Mispelon for the review.
 Backport of ea3fe78a9d 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/084.24c012922074c22889ed10a341a8bfcc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-29 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
-+-
 Reporter:  stanislas.guerra@…   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  FileField delete |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"a9b5a1e506a9e8492407399b8bec1c2a8420be60"]:
 {{{
 #!CommitTicketReference repository=""
 revision="a9b5a1e506a9e8492407399b8bec1c2a8420be60"
 [1.6.x] Do not allow FileSystemStorage.delete to receive an empty name

 Refs #20660.
 Backport of 7fbab3eba 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/084.e9f5b13b0370e4c92fdbd892d834a099%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] b6aed8: [1.6.x] Fixed #20660 -- Do not try to delete an un...

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: b6aed803b20cc7898a82fd65845e97676276f3fa
  
https://github.com/django/django/commit/b6aed803b20cc7898a82fd65845e97676276f3fa
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/db/models/fields/files.py
M tests/model_fields/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #20660 -- Do not try to delete an unset FieldFile

Thanks stanislas.guerra at gmail.com for the report and
Baptiste Mispelon for the review.
Backport of ea3fe78a9d from master.


  Commit: a9b5a1e506a9e8492407399b8bec1c2a8420be60
  
https://github.com/django/django/commit/a9b5a1e506a9e8492407399b8bec1c2a8420be60
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/core/files/storage.py
M tests/file_storage/tests.py

  Log Message:
  ---
  [1.6.x] Do not allow FileSystemStorage.delete to receive an empty name

Refs #20660.
Backport of 7fbab3eba from master.


Compare: https://github.com/django/django/compare/c55cb6fa4524...a9b5a1e506a9

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

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-29 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
-+-
 Reporter:  stanislas.guerra@…   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  FileField delete |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"ea3fe78a9d742904f6902cdc353a11d795418105"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ea3fe78a9d742904f6902cdc353a11d795418105"
 Fixed #20660 -- Do not try to delete an unset FieldFile

 Thanks stanislas.guerra at gmail.com for the report and
 Baptiste Mispelon 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/084.472864a224c389013f55a4ccb332e655%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ea3fe7: Fixed #20660 -- Do not try to delete an unset Fiel...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ea3fe78a9d742904f6902cdc353a11d795418105
  
https://github.com/django/django/commit/ea3fe78a9d742904f6902cdc353a11d795418105
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/db/models/fields/files.py
M tests/model_fields/tests.py

  Log Message:
  ---
  Fixed #20660 -- Do not try to delete an unset FieldFile

Thanks stanislas.guerra at gmail.com for the report and
Baptiste Mispelon for the review.


  Commit: 7fbab3ebaf8b60bbe847b772f895df47067a60d3
  
https://github.com/django/django/commit/7fbab3ebaf8b60bbe847b772f895df47067a60d3
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/core/files/storage.py
M tests/file_storage/tests.py

  Log Message:
  ---
  Do not allow FileSystemStorage.delete to receive an empty name

Refs #20660.


Compare: https://github.com/django/django/compare/b5f709e6f4c6...7fbab3ebaf8b

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

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-29 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
-+-
 Reporter:  stanislas.guerra@…   |Owner:  claudep
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  master
  uploads/storage|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  FileField delete |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"7fbab3ebaf8b60bbe847b772f895df47067a60d3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fbab3ebaf8b60bbe847b772f895df47067a60d3"
 Do not allow FileSystemStorage.delete to receive an empty name

 Refs #20660.
 }}}

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

Re: [Django] #20649: Add an easier way to override the blank option for CharFields with choices

2013-06-29 Thread Django

Comment (by alexcouper):

I have submitted a PR to attempt to address this problem, using my
understanding of what timo suggested.

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

I have a slight concern that we are breaking MVC somewhat, in that we're
defining presentation properties on the model as a matter of convenience.
Although having said that, we already do that somewhat with choices, so
perhaps this is seen as OK.

As this is my first contribution to Django, I thought it would be a good
idea to get feedback at this point before making any documentation
changes.

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

Re: [Django] #20660: Filefield.delete() on empty field delete MEDIA_ROOT

2013-06-29 Thread Django

#20660: Filefield.delete() on empty field delete MEDIA_ROOT
-+-
 Reporter:  stanislas.guerra@…   |Owner:  claudep
 Type:  Bug  |   Status:  assigned
Component:  File |  Version:  master
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  FileField delete |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bmispelon):

 * stage:  Accepted => Ready for checkin


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

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

Re: [Django] #20676: Wrong users highlighted as core devs in trac (was: Trac gave Core dev status to Anon user)

2013-06-29 Thread Django

#20676: Wrong users highlighted as core devs in trac
-+-
 Reporter:  alexcouper   |Owner:  bmispelon
 Type:  Bug  |   Status:  assigned
Component:  *.djangoproject.com  |  Version:  1.5
 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 bmispelon):

 * status:  new => assigned
 * cc: bmispelon@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => bmispelon
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 The highlighting of core developers is done client-side with javascript.

 As it turns out, the regular expression used to detect usernames stops at
 whitespace so your username ends up being `Alex`, a username belonging to
 Alex Gaynor who is indeed a core developer.

 I'll look into this and see if the regex can be fixed or if we need to
 change something in trac.

 Thanks.

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

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

[django/django] b5f709: Removed comment from setup.cfg which broke newer w...

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: b5f709e6f4c67020bedb141b9b18c5cd1e05f829
  
https://github.com/django/django/commit/b5f709e6f4c67020bedb141b9b18c5cd1e05f829
  Author: Florian Apolloner 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M setup.cfg

  Log Message:
  ---
  Removed comment from setup.cfg which broke newer wheel versions.



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

[django/django] c55cb6: [1.6.x] Removed comment from setup.cfg which broke...

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: c55cb6fa4524884c8b881b255ed0bb20f5e0b26a
  
https://github.com/django/django/commit/c55cb6fa4524884c8b881b255ed0bb20f5e0b26a
  Author: Florian Apolloner 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M setup.cfg

  Log Message:
  ---
  [1.6.x] Removed comment from setup.cfg which broke newer wheel versions.

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

Re: [Django] #20230: Can't send unicode email (HTML emails using EmailMultiAlternatives)

2013-06-29 Thread Django

#20230: Can't send unicode email (HTML emails using EmailMultiAlternatives)
-+
 Reporter:  jaddison |Owner:
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 No, only Python < 2.6.6 is affected.

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

Re: [Django] #20230: Can't send unicode email (HTML emails using EmailMultiAlternatives)

2013-06-29 Thread Django

#20230: Can't send unicode email (HTML emails using EmailMultiAlternatives)
-+
 Reporter:  jaddison |Owner:
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Axel Davíð Ingólfsson ):

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


Comment:

 I can't reproduce this in python2.7, django 1.4.

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

[Django] #20676: Trac gave Core dev status to Anon user

2013-06-29 Thread Django

#20676: Trac gave Core dev status to Anon user
-+
 Reporter:  alexcouper   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  *.djangoproject.com  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I assigned a ticket to myself anonymously and was given Core status:

 https://code.djangoproject.com/ticket/20649#comment:4

 I've now reassigned it to a registered version of me and all is well.

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

Re: [Django] #20649: Add an easier way to override the blank option for CharFields with choices

2013-06-29 Thread Django

#20649: Add an easier way to override the blank option for CharFields with 
choices
-+--
 Reporter:  brillgen |Owner:  alexcouper
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 alexcouper):

 * owner:  anonymous => alexcouper


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

Re: [Django] #20649: Add an easier way to override the blank option for CharFields with choices

2013-06-29 Thread Django

#20649: Add an easier way to override the blank option for CharFields with 
choices
-+-
 Reporter:  brillgen |Owner:  anonymous
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 Alex Couper ):

 I am implementing an API change for CharFields with choices such that an
 empty_label can be specified.

 {{{#!python
 CHOICES = (
 ('p', 'Python'),
 ('j', 'Java')
 )

 class DummyModel(models.Model):
 language = models.CharField(choices=CHOICES, blank=True, max_length=2,
  empty_label="Please select one")
 }}}

 Which would result in

 {{{
 Language: 
 Please select one
 Python
 Java
 
 }}}

 I'd be interested to hear of a use case where you would want to tell the
 difference between a null and a blank string on a choice field.

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

Re: [Django] #20230: Can't send unicode email (HTML emails using EmailMultiAlternatives)

2013-06-29 Thread Django

#20230: Can't send unicode email (HTML emails using EmailMultiAlternatives)
-+-
 Reporter:  jaddison |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by axelingolfsson@…):

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


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

Re: [Django] #18553: Django multipart parser creates mutable QueryDict

2013-06-29 Thread Django

#18553: Django multipart parser creates mutable QueryDict
---+
 Reporter:  k_bx   |Owner:  fred
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.4
 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 fred):

 * cc: fred (added)
 * status:  new => assigned
 * owner:  nobody => fred


Comment:

 I can confirm the following behavior in 1.7.dev20130628193320, using the
 following view:

 {{{#!python
 from django.views.decorators.csrf import csrf_exempt
 from django.views.generic import View
 from django.http import HttpResponse


 class IndexView(View):
 def post(self, request):
 return HttpResponse(bool(request.POST._mutable))

 @csrf_exempt
 def dispatch(self, *args, **kwargs):
 return super(IndexView, self).dispatch(*args, **kwargs)
 }}}


 The behavior is as follows:

 * When this view is called with a POST of type application/x-www-form-
 urlencoded, it returns "False" (the POST is mutable).
 * When this view is called with a POST of type multipart/form-data POST,
 it returns "True".
 * Likewise, when calling the view through `self.client.post('/view')`, it
 returns "True".  This confirms that the bug may lead to code that passes
 tests and fails in production.

 I'd like to further look into this issue.

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

[django/django] 6118d6: More import removals

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6118d6d1c982e428cf398ac998eb9f0baba15bad
  
https://github.com/django/django/commit/6118d6d1c982e428cf398ac998eb9f0baba15bad
  Author: Claude Paroz 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/auth/forms.py
M django/contrib/auth/models.py
M django/contrib/auth/tests/test_models.py
M django/contrib/sitemaps/views.py
M django/shortcuts/__init__.py
M django/test/testcases.py
M docs/ref/utils.txt
M tests/.coveragerc
M tests/test_utils/tests.py

  Log Message:
  ---
  More import removals

Following the series of commits removing deprecated features in
Django 1.7, here are some more unneeded imports removed and other
minor cleanups.



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

Re: [Django] #20671: Custom backend get_user function is assumed to search by primary key

2013-06-29 Thread Django

#20671: Custom backend get_user function is assumed to search by primary key
-+-
 Reporter:  elliot.smith91@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  session, auth,   | Triage Stage:  Accepted
  custom |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * needs_better_patch:   => 0
 * component:  contrib.sessions => contrib.auth
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Bug => New feature
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 The source of the problem is `contrib.auth.login`, which has the following
 line [1]:
 {{{#!python
 request.session[SESSION_KEY] = user.pk
 }}}

 This limitation is somewhat documented, as the documentation states that
 [2]:
 > user_id [...] has to be the primary key of your User object

 I think it'd be interesting to explore what we could do to lift this
 limitation (and if not, I agree that it should be documented more
 prominently).

 However, I don't think that the user model is the right place for it.
 From my understanding, it's the responsibility of the backend (not the
 user model) to store in the session whatever it needs to fetch the full
 user object later on.

 [1]
 
https://github.com/django/django/blob/master/django/contrib/auth/__init__.py#L84
 [2] https://docs.djangoproject.com/en/dev/topics/auth/customizing
 /#writing-an-authentication-backend

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

Re: [Django] #20079: Improve security of password reset tokens

2013-06-29 Thread Django

#20079: Improve security of password reset tokens
-+-
 Reporter:  jacob|Owner:  Erik
 Type:  Bug  |  Romijn 
Component:  contrib.auth |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  dceu13   |   Resolution:  fixed
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 Aymeric Augustin ):

 In [changeset:"6908b6593949a205d05da342060a9d952bd7b77c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="6908b6593949a205d05da342060a9d952bd7b77c"
 [1.6.x] Removed obsolete comment. Refs #20079.

 Thanks Gavin Wahl.
 }}}

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

[django/django] 6908b6: [1.6.x] Removed obsolete comment. Refs #20079.

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 6908b6593949a205d05da342060a9d952bd7b77c
  
https://github.com/django/django/commit/6908b6593949a205d05da342060a9d952bd7b77c
  Author: Aymeric Augustin 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/auth/models.py

  Log Message:
  ---
  [1.6.x] Removed obsolete comment. Refs #20079.

Thanks Gavin Wahl.



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

[django/django] c8756e: Removed obsolete comment. Refs #20079.

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c8756e17fbd5293ee1e0582201c41e2febc58ae1
  
https://github.com/django/django/commit/c8756e17fbd5293ee1e0582201c41e2febc58ae1
  Author: Aymeric Augustin 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M django/contrib/auth/models.py

  Log Message:
  ---
  Removed obsolete comment. Refs #20079.

Thanks Gavin Wahl.



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

Re: [Django] #20079: Improve security of password reset tokens

2013-06-29 Thread Django

#20079: Improve security of password reset tokens
-+-
 Reporter:  jacob|Owner:  Erik
 Type:  Bug  |  Romijn 
Component:  contrib.auth |   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:  dceu13   |   Resolution:  fixed
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 Aymeric Augustin ):

 In [changeset:"c8756e17fbd5293ee1e0582201c41e2febc58ae1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c8756e17fbd5293ee1e0582201c41e2febc58ae1"
 Removed obsolete comment. Refs #20079.

 Thanks Gavin Wahl.
 }}}

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

Re: [Django] #20600: Subqueries should retain ORDER BY when using DISTINCT ON

2013-06-29 Thread Django

#20600: Subqueries should retain ORDER BY when using DISTINCT ON
-+-
 Reporter:  brianglass   |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by koddsson):

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


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

Re: [Django] #20667: Remove discussion of DEBUG from the tutorial

2013-06-29 Thread Django

#20667: Remove discussion of DEBUG from the tutorial
--+
 Reporter:  sosdog88@…|Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * needs_better_patch:  0 => 1


Comment:

 +1 to remove the matching sections in the tutorial. However, in the
 checklist, I'd rather stress the usefulness of custom templates
 (`404.html`, `500.html`) instead of custom views (which as stated are OK
 for 99% of cases).

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

Re: [Django] #20649: Add an easier way to override the blank option for CharFields with choices

2013-06-29 Thread Django

#20649: Add an easier way to override the blank option for CharFields with 
choices
-+-
 Reporter:  brillgen |Owner:  anonymous
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 brillgen):

 IMHO, its a bug because the documentation for choices does not say
 anywhere that the blank is a special case etc. While designing a solution,
 I would also suggest that you keep in mind this use case (we're not
 affected by this one yet)

 For a Nullable char field with choices, the select options created should
 be as below:
 Null should be represented lets say by the default - (and
 overridable)
 "" should also be represented lets say by the default "" (and overridable)
 

 These are all database valid options which should be possible. How its
 done keeping backward compatibility is why you guys chose to be the core
 team :)

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

[django/django] adc6f3: Fixed 1.6 release notes.

2013-06-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: adc6f38867dd5b57c9e1c50395eec01f6bdd651f
  
https://github.com/django/django/commit/adc6f38867dd5b57c9e1c50395eec01f6bdd651f
  Author: Florian Apolloner 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  Fixed 1.6 release notes.



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

[django/django] 7bd9c3: [1.6.x] Fixed 1.6 release notes.

2013-06-29 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 7bd9c32f14a0a56089358f7927a3326e78bee093
  
https://github.com/django/django/commit/7bd9c32f14a0a56089358f7927a3326e78bee093
  Author: Florian Apolloner 
  Date:   2013-06-29 (Sat, 29 Jun 2013)

  Changed paths:
M docs/releases/1.6.txt

  Log Message:
  ---
  [1.6.x] Fixed 1.6 release notes.

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

Re: [Django] #20673: Improve HttpRequest.user documentation

2013-06-29 Thread Django

#20673: Improve HttpRequest.user documentation
--+
 Reporter:  littlepig |Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.5
 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 susan):

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

Re: [Django] #20667: Remove discussion of DEBUG from the tutorial

2013-06-29 Thread Django

#20667: Remove discussion of DEBUG from the tutorial
--+
 Reporter:  sosdog88@…|Owner:  susan
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by susan):

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

Re: [Django] #18314: request.build_absolute_uri() functions incorrectly when the path starts with //

2013-06-29 Thread Django

#18314: request.build_absolute_uri() functions incorrectly when the path starts
with //
---+
 Reporter:  anonymous  |Owner:  susan
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+

Comment (by susan):

 https://github.com/django/django/pull/1314 PR is here.

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

Re: [Django] #20675: `ModelBackend.authenticate` raises an assertion error when no password is specified.

2013-06-29 Thread Django

#20675: `ModelBackend.authenticate` raises an assertion error when no password 
is
specified.
-+-
 Reporter:  charettes|Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  master
 Severity:  Release blocker  |   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 bmispelon):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 It's perfectly valid not to pass a `password` kwarg to `authenticate`, so
 I think this is a bug.

 As you noted, prior to the commit, `authenticate` would just move on to
 the next backend in the list, eventually returning `None` if no matching
 user was found.

 Now, the `ModelBackend` raises an `AssertionError` and breaks the chain,
 rendering non-password-based backends unusable.

 Consequently, I think it's a release blocker.

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

Re: [Django] #8060: uylovaybfnyq (was: Admin Inlines do not respect user permissions)

2013-06-29 Thread Django

#8060: uylovaybfnyq
---+
 Reporter:  p.patruno@…|Owner:  sjaensch
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  mvwuubvcqujo   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by bfouqdiwnzhr):

 * keywords:  inlines User authentication => mvwuubvcqujo


Comment:

 woah, awesome site thanks sqkbjliqkl http://www.sseqfwhmcgpm.com";>click here ;) qjfub, ;) onbwklfqlv
 [url="http://www.sseqfwhmcgpm.net"]or here[/url] :-D qjfub, >:-O
 kugbxdaiqe http://sseqfwhmcgpm.info :/ jlmouax, :3 moakxbaswx
 [url=http://sseqfwhmcgpm.ru]xlihqtyzyj[/url] :D cqwcpmhx, :-D bnckdrawpi
 [link=http://sseqfwhmcgpm.se]dzjtovkixy[/link] >:-O jlmouax, :-X

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

60 matches

Mail list logo