date:20120109

Re: [Django] #17526: Grammatical error in djangodocs.py?

2012-01-09 Thread Django

#17526: Grammatical error in djangodocs.py?
-+-
 Reporter:  datakid@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  documentation|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by anonymous):

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


Comment:

 Of course, when I said it should be removed, I meant it to say

 "Please see the release notes"

 rather than

 "Please read the release notes"

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17526: Grammatical error in djangodocs.py?

2012-01-09 Thread Django

#17526: Grammatical error in djangodocs.py?
--+---
 Reporter:  datakid@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.3
 Severity:  Normal|   Keywords:  documentation
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  1
--+---
 An email thread pointed to this page:
 https://docs.djangoproject.com/en/1.3/ref/forms/validation/

 Which has the leading note: "Changed in Django 1.2: Please, see the
 release notes"

 This is triggered in the code at lines 82-84 in
 
[https://code.djangoproject.com/browser/django/trunk/docs/_ext/djangodocs.py?rev=17365
 djangodocs.py]

 From everything I've read, and as an English as a first language
 background, I think that the comma should be removed:

 "Please read the release notes"

 I've not added a patch, since I don't have access to an svn co atm to
 create a diff, and it's a minor change that could be done by anyone.

 Minor grammar nazi bug?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17525: Fixes for django.contrib.auth tests

2012-01-09 Thread Django

#17525: Fixes for django.contrib.auth tests
--+-
 Reporter:  andrey@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.4-alpha-1
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 Found two bugs in my application:

 1. If any of my middleware works with session, test_session_not_accessed
 fails.
 2. (not a bug really) I use jinja in my project and form.as_ul returns
 method object. If you can change {{form.as_ul}} to {{form}} tests will
 also work with jinja2.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17524: self referential blocks

2012-01-09 Thread Django

#17524: self referential blocks
--+--
 Reporter:  pasquinelli@… |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Template system   |  Version:  1.3
 Severity:  Normal|   Resolution:  duplicate
 Keywords:  recursive blocks  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by russellm):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Duplicate of #4529, and others. I think you might be looking for the {%
 include %} 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16745: Different times on fields with auto_now and auto_now_add

2012-01-09 Thread Django

#16745: Different times on fields with auto_now and auto_now_add
-+-
 Reporter:  kantntreiber@…   |Owner:
 Type:  Bug  |  michaelmior
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  auto_now,| Triage Stage:  Accepted
  auto_now_add, DateTimeField,   |  Needs documentation:  1
  DateField, field   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by michaelmior):

 I suppose it could be helpful for debugging purposes and correlating logs.
 And maybe especially so in the case where one needs to integrate with
 legacy systems. The ability to use database time could be a plus. Although
 it seems like other parts for the core would need to be changed to have a
 consistent view of time. Actually. perhaps it would be easiest to allow
 {{{TIME_ZONE}}} to be configured such that it will use the DB server's TZ.
 In any case, this feels outside the scope of this issue, but I'm open to
 continuing work on something along these lines if it proves useful.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17156: QuerySet.contains needs documentation

2012-01-09 Thread Django

#17156: QuerySet.__contains__ needs documentation
--+
 Reporter:  guettli   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 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 sebastian):

 * cc: sebastian.goll@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17524: self referential blocks

2012-01-09 Thread Django

#17524: self referential blocks
-+--
 Reporter:  pasquinelli@…|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Template system  |Version:  1.3
 Severity:  Normal   |   Keywords:  recursive blocks
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+--
 say i have a '''{% block content %}''' in '''base.html''' and i'd like to
 refine it in another template '''refined.html''', while still exposing the
 block to other templates that extend from '''refined.html''' like so:


 {{{
 {% block content %}

   {% block content %}{% endblock content %}

 {% endblock content %}
 }}}


 currently this is impossible because there can be only one occurrence of a
 block in a template, which means i have to repeat myself. i think you
 should be able to override a block and still expose it for further
 extension.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17523: Slicing: EmptyQuerySet behaves differently from QuerySet

2012-01-09 Thread Django

#17523: Slicing: EmptyQuerySet behaves differently from QuerySet
-+-
 Reporter:  rluedeman|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  duplicate
 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 rluedeman):

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


Comment:

 nevermind. just discovered this is a dupe of #10139

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17523: Slicing: EmptyQuerySet behaves differently from QuerySet

2012-01-09 Thread Django

#17523: Slicing: EmptyQuerySet behaves differently from QuerySet
-+-
 Reporter:  rluedeman|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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 rluedeman):

 * component:  Uncategorized => Database layer (models, ORM)
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17523: Slicing: EmptyQuerySet behaves differently from QuerySet

2012-01-09 Thread Django

#17523: Slicing: EmptyQuerySet behaves differently from QuerySet
---+
 Reporter:  rluedeman  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I noticed a slight (but annoying) difference between slicing an
 EmptyQuerySet and slicing a standard QuerySet. It seems like slicing an
 EmptyQuerySet should return an EmptyQuerySet, rather than returning a
 list.

 Example:
 {{{
 >> from django.contrib.auth.models import User
 >>
 >> type(User.objects.all())
 
 >> type(User.objects.all()[:0])
 
 >> type(User.objects.all()[:10])
 
 >>
 >> type(User.objects.none())
 
 >> type(User.objects.none()[:0])
 
 >> type(User.objects.none()[:10])
 
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16745: Different times on fields with auto_now and auto_now_add

2012-01-09 Thread Django

#16745: Different times on fields with auto_now and auto_now_add
-+-
 Reporter:  kantntreiber@…   |Owner:
 Type:  Bug  |  michaelmior
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  auto_now,| Triage Stage:  Accepted
  auto_now_add, DateTimeField,   |  Needs documentation:  1
  DateField, field   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 In the case of PostgreSQL, the server configured time zone doesn't matter,
 the time zone used in the connection is what matters. And Django knows
 that.

 But I might be pushing this a bit too far, maybe using database.now()
 should be a separate field option, and done in separate ticket. I am not
 sure if transaction start time is easily available when using other
 databases.

 It seems I will be really busy at least until weekend. Have to see if I
 can find time to review this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #4680: Fixes problem in initial_sql where "--" is in a string

2012-01-09 Thread Django

#4680: Fixes problem in initial_sql where "--" is in a string
-+-
 Reporter:  Tim Chase|Owner:  anonymous
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  initial-sql  |  Needs documentation:  0
  manage.py sprintdec01  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * cc: claude@… (added)
 * needs_better_patch:  1 => 0
 * ui_ux:   => 0
 * easy:   => 0


Comment:

 A possible patch, inspired from the initial patch regex to clean 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10762: Gzip Middleware Should Compress 201 (Created) Responses

2012-01-09 Thread Django

#10762: Gzip Middleware Should Compress 201 (Created) Responses
-+-
 Reporter:  rwagner@…|Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  SVN
Component:  HTTP handling|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  middleware gzip  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by aaugustin):

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


Comment:

 In [17365]:
 {{{
 #!CommitTicketReference repository="" revision="17365"
 Fixed #10762, #17514 -- Prevented the GZip middleware from returning a
 response longer than the original content, allowed compression of non-200
 responses, and added tests (there were none). Thanks cannona for the
 initial patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17514: GZip middleware lacks tests and sends compressed responses when larger than the original

2012-01-09 Thread Django

#17514: GZip middleware lacks tests and sends compressed responses when larger 
than
the original
-+-
 Reporter:  cannona  |Owner:  aaugustin
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  SVN
Component:  Uncategorized|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  gzip, tests  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 In [17365]:
 {{{
 #!CommitTicketReference repository="" revision="17365"
 Fixed #10762, #17514 -- Prevented the GZip middleware from returning a
 response longer than the original content, allowed compression of non-200
 responses, and added tests (there were none). Thanks cannona for the
 initial patch.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r17365 - in django/trunk: django/middleware docs/ref tests/regressiontests/middleware

2012-01-09 Thread noreply

Author: aaugustin
Date: 2012-01-09 13:42:03 -0800 (Mon, 09 Jan 2012)
New Revision: 17365

Modified:
   django/trunk/django/middleware/gzip.py
   django/trunk/docs/ref/middleware.txt
   django/trunk/tests/regressiontests/middleware/tests.py
Log:
Fixed #10762, #17514 -- Prevented the GZip middleware from returning a response 
longer than the original content, allowed compression of non-200 responses, and 
added tests (there were none). Thanks cannona for the initial patch.


Modified: django/trunk/django/middleware/gzip.py
===
--- django/trunk/django/middleware/gzip.py  2012-01-08 21:36:22 UTC (rev 
17364)
+++ django/trunk/django/middleware/gzip.py  2012-01-09 21:42:03 UTC (rev 
17365)
@@ -12,8 +12,8 @@
 on the Accept-Encoding header.
 """
 def process_response(self, request, response):
-# It's not worth compressing non-OK or really short responses.
-if response.status_code != 200 or len(response.content) < 200:
+# It's not worth attempting to compress really short responses.
+if len(response.content) < 200:
 return response
 
 patch_vary_headers(response, ('Accept-Encoding',))
@@ -32,7 +32,12 @@
 if not re_accepts_gzip.search(ae):
 return response
 
-response.content = compress_string(response.content)
+# Return the compressed content only if it's actually shorter.
+compressed_content = compress_string(response.content)
+if len(compressed_content) >= len(response.content):
+return response
+
+response.content = compressed_content
 response['Content-Encoding'] = 'gzip'
 response['Content-Length'] = str(len(response.content))
 return response

Modified: django/trunk/docs/ref/middleware.txt
===
--- django/trunk/docs/ref/middleware.txt2012-01-08 21:36:22 UTC (rev 
17364)
+++ django/trunk/docs/ref/middleware.txt2012-01-09 21:42:03 UTC (rev 
17365)
@@ -82,23 +82,30 @@
 Django's :doc:`automatic documentation system `.
 Depends on :class:`~django.contrib.auth.middleware.AuthenticationMiddleware`.
 
-GZIP middleware
+GZip middleware
 ---
 
 .. module:: django.middleware.gzip
-   :synopsis: Middleware to serve gziped content for performance.
+   :synopsis: Middleware to serve GZipped content for performance.
 
 .. class:: GZipMiddleware
 
-Compresses content for browsers that understand gzip compression (all modern
+Compresses content for browsers that understand GZip compression (all modern
 browsers).
 
 It is suggested to place this first in the middleware list, so that the
-compression of the response content is the last thing that happens. Will not
-compress content bodies less than 200 bytes long, when the response code is
-something other than 200, JavaScript files (for IE compatibility), or
-responses that have the ``Content-Encoding`` header already specified.
+compression of the response content is the last thing that happens.
 
+It will not compress content bodies less than 200 bytes long, when the
+``Content-Encoding`` header is already set, or when the browser does not send
+an ``Accept-Encoding`` header containing ``gzip``.
+
+Content will also not be compressed when the browser is Internet Explorer and
+the ``Content-Type`` header contains ``javascript`` or starts with anything
+other than ``text/``. This is done to overcome a bug present in early versions
+of Internet Explorer which caused decompression not to be performed on certain
+content types.
+
 GZip compression can be applied to individual views using the
 :func:`~django.views.decorators.http.gzip_page()` decorator.
 

Modified: django/trunk/tests/regressiontests/middleware/tests.py
===
--- django/trunk/tests/regressiontests/middleware/tests.py  2012-01-08 
21:36:22 UTC (rev 17364)
+++ django/trunk/tests/regressiontests/middleware/tests.py  2012-01-09 
21:42:03 UTC (rev 17365)
@@ -1,6 +1,9 @@
 # -*- coding: utf-8 -*-
 
+import gzip
 import re
+import random
+import StringIO
 
 from django.conf import settings
 from django.core import mail
@@ -9,6 +12,7 @@
 from django.middleware.clickjacking import XFrameOptionsMiddleware
 from django.middleware.common import CommonMiddleware
 from django.middleware.http import ConditionalGetMiddleware
+from django.middleware.gzip import GZipMiddleware
 from django.test import TestCase
 
 
@@ -495,3 +499,86 @@
 r = OtherXFrameOptionsMiddleware().process_response(HttpRequest(),
HttpResponse())
 self.assertEqual(r['X-Frame-Options'], 'DENY')
+
+
+class GZipMiddlewareTest(TestCase):
+"""
+Tests the GZip middleware.
+"""
+short_string = "This string is too short to be worth compressing."
+compressible_string = 'a' * 500
+

Re: [Django] #16256: More class based views: formsets derived generic views

2012-01-09 Thread Django

#16256: More class based views: formsets derived generic views
---+
 Reporter:  rasca  |Owner:  rasca
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by darkpixel):

 * cc: aaron@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17522: ModelAdmin.ordering validation too strict

2012-01-09 Thread Django

#17522: ModelAdmin.ordering validation too strict
-+-
 Reporter:   |  Owner:  nobody
  sebastian  | Status:  new
 Type:  Bug  |Version:  SVN
Component:   |   Keywords:  admin, validation, ordering, strict
  contrib.admin  |  Has patch:  1
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 `ModelAdmin.ordering` checks whether all elements are the names of valid
 fields on the model. This is too strict as we can also define methods on
 the model or admin class and set `admin_order_field`. In fact, if such
 columns are used in `list_display` they are sortable by clicking on the
 corresponding column in the change list view.

 The attached patch relaxes the admin validation so that the names of such
 methods are allowed for the default sorting. It also adds several tests to
 check this relaxed validation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17514: GZip middleware lacks tests and sends compressed responses when larger than the original

2012-01-09 Thread Django

#17514: GZip middleware lacks tests and sends compressed responses when larger 
than
the original
-+-
 Reporter:  cannona  |Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  gzip, tests  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10762: Gzip Middleware Should Compress 201 (Created) Responses

2012-01-09 Thread Django

#10762: Gzip Middleware Should Compress 201 (Created) Responses
-+-
 Reporter:  rwagner@…|Owner:  aaugustin
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  SVN
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  middleware gzip  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin


Comment:

 See also #17514.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17514: GZip middleware lacks tests and sends compressed responses when larger than the original

2012-01-09 Thread Django

#17514: GZip middleware lacks tests and sends compressed responses when larger 
than
the original
--+
 Reporter:  cannona   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Uncategorized |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  gzip, tests   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 This would supersede #10762.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17521: Only use minified JavaScript when DEBUG is off

2012-01-09 Thread Django

#17521: Only use minified JavaScript when DEBUG is off
-+-
 Reporter:  tswicegood   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  contrib.admin|  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  javascript, admin| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17520: write queries on related managers use the db_for_read database

2012-01-09 Thread Django

#17520: write queries on related managers use the db_for_read database
-+-
 Reporter:  tobias   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tobias):

 * needs_better_patch:  0 => 1


Comment:

 The patch only has a test currently (not sure why that got unset, I didn't
 uncheck anything).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17521: Only use minified JavaScript when DEBUG is off

2012-01-09 Thread Django

#17521: Only use minified JavaScript when DEBUG is off
-+-
 Reporter:  tswicegood   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  contrib.admin|  1.4-alpha-1
 Severity:  Normal   |   Resolution:
 Keywords:  javascript, admin| Triage Stage:
Has patch:  1|  Unreviewed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by tswicegood):

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


Comment:

 See also https://github.com/django/django/pull/103


 > Open to ideas on testing this...?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17520: write queries on related managers use the db_for_read database

2012-01-09 Thread Django

#17520: write queries on related managers use the db_for_read database
-+-
 Reporter:  tobias   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 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 tobias):

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


Comment:

 The issue appears to be that query._db gets set when the queryset is
 created from a related manager.  As such, when the !QuerySet.db property
 checks to see what write db to use, it assumes using() has been called
 manually and does not call db_for_write on the router as it should.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17521: Only use minified JavaScript when DEBUG is off

2012-01-09 Thread Django

#17521: Only use minified JavaScript when DEBUG is off
--+---
 Reporter:  tswicegood|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.admin |Version:  1.4-alpha-1
 Severity:  Normal|   Keywords:  javascript, admin
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+---
 This makes it easier to inspect the code that is being used when trying to
 track down a problem in the JavaScript.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17520: write queries on related managers use the db_for_read database

2012-01-09 Thread Django

#17520: write queries on related managers use the db_for_read database
--+
 Reporter:  tobias|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If you execute a write query (update() or delete()) on a queryset obtained
 from a related manager, it appears to use the db_for_read database instead
 of the db_for_write database for that query.

 The attached patch reproduces the issue on trunk.  It also exists in
 1.3.1.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16745: Different times on fields with auto_now and auto_now_add

2012-01-09 Thread Django

#16745: Different times on fields with auto_now and auto_now_add
-+-
 Reporter:  kantntreiber@…   |Owner:
 Type:  Bug  |  michaelmior
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  auto_now,| Triage Stage:  Accepted
  auto_now_add, DateTimeField,   |  Needs documentation:  1
  DateField, field   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by michaelmior):

 @aaugustin Would I be correct in understanding that
 {{{django.utils.timezone.localtime}}} performs the conversion to the
 default time zone?

 @kaaria Agreed that the transaction start time may be unreliable, but it
 should be roughly accurate. As far as I can tell, Django has no guarantees
 on the delta of these times from their actual values anyway. (Although
 perhaps calling the time {{{transaction_start}}} is a bit of a misnomer.)
 My concern with using `NOW()` from the database end is that it requires
 knowledge of the server's configured time zone, which I don't believe
 Django currently has. Correct me if I'm wrong.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5446: New model fields for languages and countries at least

2012-01-09 Thread Django

#5446: New model fields for languages and countries at least
-+-
 Reporter:  Raphaël Hertzog  |Owner:  marinho
  |   Status:  reopened
 Type:  New feature  |  Version:  SVN
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  feature_request  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by gezuru@…):

 * cc: gezuru@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9025: Nested Inline Support in Admin

2012-01-09 Thread Django

#9025: Nested Inline Support in Admin
-+-
 Reporter:  pixelcort|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  1
-+-

Comment (by anonymous):

 +1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #373: Add support for multiple-column primary keys

2012-01-09 Thread Django

#373: Add support for multiple-column primary keys
-+-
 Reporter:  jacob|Owner:  konk
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by konk):

 Well, the current status is, the `soc2011/composite-fields` branch is
 stable and I'm just keeping it up-to-date with master. There is some
 documentation, though I'm afraid it is not complete. Anyway, it only works
 with non-relationship fields.

 As for relationship fields and the `auxiliary_fk_fields` branch, it is
 still only in the refactoring phase. I had to modify `ForeignKey`
 extensively and it's still not there but I'm trying to fix the bugs one by
 one. Once the whole test suite succeeds (except for `CompositeField`
 tests) I can resume working on composite fields themselves.

 Note that this is quite a tedious process since most of the remaining
 failing test cases require individual handling, therefore I'll appreciate
 any help with this. Feel free to fork me on github and send pull requests.
 I don't always find enough free time to work on this myself, I've still
 got some exams to do and also a Bc. thesis to work on...

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #373: Add support for multiple-column primary keys

2012-01-09 Thread Django

#373: Add support for multiple-column primary keys
-+-
 Reporter:  jacob|Owner:  konk
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by lau):

 We're still a bunch of hopeful people holding our breaths for this feature
 to enter django. What's the status? Looks like there's lots of activity on
 github, is the code at a state where it's reasonably stable? In which case
 I'd be happy to start testing on some real-life data.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #373: Add support for multiple-column primary keys

2012-01-09 Thread Django

#373: Add support for multiple-column primary keys
-+-
 Reporter:  jacob|Owner:  konk
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  database |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by pawel.suwala@…):

 * cc: pawel.suwala@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8448: Collapse Tabular Inline

2012-01-09 Thread Django

#8448: Collapse Tabular Inline
---+--
 Reporter:  mdpetry|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admin  |  Version:  SVN
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  inline | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Could be very helpful for me as 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17519: Missing SQL constraint to proxy models

2012-01-09 Thread Django

#17519: Missing SQL constraint to proxy models
--+
 Reporter:  thibaultj |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:  sql mysql
 Triage Stage:  Unreviewed|  constraint
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 In a model class, when you add a ForeignKey to a proxy model, the sql
 reference will no be created in Mysql. This is a severe issue, since the
 integrity structure of the database cannot be ensured.

 Moreover, as stated in #16128, the django admin will not gather related
 proxy model objects when deleting something. This is a separate issue
 though, since we are talking of the sql generation here.


 {{{
 # file constraint_test/models.py
 class Parent(models.Model):
 name = models.CharField(max_length=25)

 class Father(Parent):
 class Meta:
 proxy = True

 def __unicode__(self):
 return "I'm your father, luke"

 class Child(models.Model):
 name = models.CharField(max_length=25)
 parent = models.ForeignKey(Parent, related_name='child_parent_set')
 father = models.ForeignKey(Father, related_name='child_father_set')
 }}}


 {{{
 python manage.py sql constaint_test
 }}}


 {{{
 BEGIN;
 CREATE TABLE `constraint_test_parent` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `name` varchar(25) NOT NULL
 )
 ;
 CREATE TABLE `constraint_test_child` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `name` varchar(25) NOT NULL,
 `parent_id` integer NOT NULL,
 `father_id` integer NOT NULL
 )
 ;
 ALTER TABLE `constraint_test_child` ADD CONSTRAINT
 `parent_id_refs_id_875b6ff2` FOREIGN KEY (`parent_id`) REFERENCES
 `constraint_test_parent` (`id`);
 -- Missing constraint to the father table
 COMMIT;
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #4682: [patch] Add UuidField

2012-01-09 Thread Django

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
     |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (added)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17495: Release Notes for 1.4: Table auth_message is gone

2012-01-09 Thread Django

#17495: Release Notes for 1.4: Table auth_message is gone
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Documentation|  1.4-alpha-1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * status:  new => closed
 * cc: hv@… (removed)
 * resolution:   => invalid


Comment:

 OK, you are right.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17129: Model FAQ: Link to south

2012-01-09 Thread Django

#17129: Model FAQ: Link to south
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  south| Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16698: Docs: QuerySet slicing (SQL LIMIT)

2012-01-09 Thread Django

#16698: Docs: QuerySet slicing (SQL LIMIT)
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:  wontfix
 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 guettli):

 * cc: hv@… (removed)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15593: Docs: result of reverse() is already urlquoted

2012-01-09 Thread Django

#15593: Docs: result of reverse() is already urlquoted
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11402: exists() method on QuerySets

2012-01-09 Thread Django

#11402: exists() method on QuerySets
-+-
 Reporter:  Alex |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.0
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9987: get_profile documentation: Autocreate by signal

2012-01-09 Thread Django

#9987: get_profile documentation: Autocreate by signal
-+-
 Reporter:  guettli  |Owner:  kkubasik
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  profile signal   | Triage Stage:  Accepted
  kkmegapatch|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9964: Transaction middleware closes the transaction only when it's marked as dirty

2012-01-09 Thread Django

#9964: Transaction middleware closes the transaction only when it's marked as
dirty
-+-
 Reporter:  ishirav  |Owner:
 Type:  Uncategorized|  mtredinnick
Component:  Database layer   |   Status:  closed
  (models, ORM)  |  Version:
 Severity:  Normal   |  1.0-beta-1
 Keywords:  transactions |   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
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9577: Debug page's Request URL hides SCRIPT_NAME

2012-01-09 Thread Django

#9577: Debug page's Request URL hides SCRIPT_NAME
---+
 Reporter:  guettli|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  HTTP handling  |  Version:  1.0
 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 guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9503: "Model instance reference" docs don't really discuss delete.

2012-01-09 Thread Django

#9503: "Model instance reference" docs don't really discuss delete.
---+
 Reporter:  Beetle_B   |Owner:  jacob
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.0
 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 guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9384: en/dev/ref/forms/validation 2 typos

2012-01-09 Thread Django

#9384: en/dev/ref/forms/validation 2 typos
-+-
 Reporter:  romke|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9366: date and time filters do not use localized strings, missing datetime filter

2012-01-09 Thread Django

#9366: date and time filters do not use localized strings, missing datetime 
filter
-+-
 Reporter:  bthomas  |Owner:
 Type:  Uncategorized|  garcia_marc
Component:   |   Status:  closed
  Internationalization   |  Version:  1.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  i18n-fixed   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9216: Forms: Assert that js and css attributes of Media contain list or tuple

2012-01-09 Thread Django

#9216: Forms: Assert that js and css attributes of Media contain list or tuple
---+--
 Reporter:  guettli|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.0
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9089: urlencode should support MutliValueDict

2012-01-09 Thread Django

#9089: urlencode should support MutliValueDict
-+-
 Reporter:  guettli  |Owner:  gptvnt
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  1.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9031: Small bug if typo in testcase

2012-01-09 Thread Django

#9031: Small bug if typo in testcase
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Testing framework|  Version:  1.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8962: Make `input_formats` and `format` work consistently across `date`, `datetime`, and `time` fields and widgets.

2012-01-09 Thread Django

#8962: Make `input_formats` and `format` work consistently across `date`,
`datetime`, and `time` fields and widgets.
-+-
 Reporter:  mrmachine|Owner:  kmtracey
 Type:  Uncategorized|   Status:  closed
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  datetime format  | Triage Stage:  Accepted
  widget i18n-rf |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8901: Django's guessed postgresql sequence name is incorrect if the resulting sequence name is longer than max_identifier_length

2012-01-09 Thread Django

#8901: Django's guessed postgresql sequence name is incorrect if the resulting
sequence name is longer than max_identifier_length
-+-
 Reporter:  adam@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  postgresql   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8164: Custom field order in ModelForms

2012-01-09 Thread Django

#8164: Custom field order in ModelForms
-+-
 Reporter:  kire |Owner:  Alex
 Type:  Uncategorized|   Status:  closed
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelform, field | Triage Stage:  Accepted
  order  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7930: FORCE_SCRIPT_NAME does not work with dev server

2012-01-09 Thread Django

#7930: FORCE_SCRIPT_NAME does not work with dev server
---+
 Reporter:  ElliottM   |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  HTTP handling  |  Version:  SVN
 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 guettli):

 * cc: hv@… (removed)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7539: Add ON DELETE and ON UPDATE support to Django

2012-01-09 Thread Django

#7539: Add ON DELETE and ON UPDATE support to Django
-+-
 Reporter:  glassfordm   |Owner:  carljm
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  feature  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7287: Newforms' initial values as models, for ModelChoiceField etc

2012-01-09 Thread Django

#7287: Newforms' initial values as models, for ModelChoiceField etc
-+-
 Reporter:  Simon Litchfield |Owner:  nobody
    |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6766: TEMPLATE_STRING_IF_INVALID should work for loops

2012-01-09 Thread Django

#6766: TEMPLATE_STRING_IF_INVALID should work for loops
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  SVN
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6675: Better error message if cleaned_data is missing (unbound Form)

2012-01-09 Thread Django

#6675: Better error message if cleaned_data is missing (unbound Form)
---+
 Reporter:  guettli|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  SVN
 Severity:  Normal |   Resolution:  wontfix
 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 guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Related https://code.djangoproject.com/ticket/5524 (stop cleaned_data from
 disappearing).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6621: build_absolute_uri in HttpRequest breaks with colon in URL path

2012-01-09 Thread Django

#6621: build_absolute_uri in HttpRequest breaks with colon in URL path
-+-
 Reporter:  Greg Thornton|Owner:  nobody
     |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  HTTP handling|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  http url colon   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6474: conditional_escape: Try to convert to a string first, then check if SafeData

2012-01-09 Thread Django

#6474: conditional_escape: Try to convert to a string first, then check if
SafeData
--+
 Reporter:  guettli   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  SVN
 Severity:  Normal|   Resolution:  invalid
 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 guettli):

 * cc: hv@… (removed)
 * status:  new => closed
 * ui_ux:   => 0
 * resolution:   => invalid


Comment:

 The unittest of the patch still fails, but I (original reporter) close 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6454: request.path is a unicode string

2012-01-09 Thread Django

#6454: request.path is a unicode string
---+--
 Reporter:  guettli|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  SVN
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6449: datetime filter to access the settings/locales datetime format

2012-01-09 Thread Django

#6449: datetime filter to access the settings/locales datetime format
-+-
 Reporter:  Harm Geerts  |Owner:
 Type:  Uncategorized|  garcia_marc
Component:   |   Status:  closed
  Internationalization   |  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  i18n-fixed   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6108: send all_objects_to_be_deleted in the pre_delete signal

2012-01-09 Thread Django

#6108: send all_objects_to_be_deleted in the pre_delete signal
-+-
 Reporter:  Gábor Farkas |Owner:  nobody
    |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Core (Other) |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5925: Unable to use urlresolvers (url, reverse ) feature in redirect argument of decorator user_passes_test

2012-01-09 Thread Django

#5925: Unable to use urlresolvers (url,reverse ) feature in redirect argument of
decorator user_passes_test
-+-
 Reporter:  anonymous|Owner:
 Type:   |  SmileyChris
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  urlresolver,reverse,decorator,url,permalink|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5390: Add signals to ManyRelatedManager

2012-01-09 Thread Django

#5390: Add signals to ManyRelatedManager
-+-
 Reporter:  Ludovico |Owner:  rvdrijst
  Magnocavallo   |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  manytomanyfield  |  Needs documentation:  0
  feature signals|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5350: urlresolvers: Fallback, if urls.py don't have handle404 and friends

2012-01-09 Thread Django

#5350: urlresolvers: Fallback, if urls.py don't have handle404 and friends
-+-
 Reporter:  Thomas Güttler   |Owner:  nobody
   |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5028: unicode: str(s) can fail if s is an AssertionError

2012-01-09 Thread Django

#5028: unicode: str(s) can fail if s is an AssertionError
-+-
 Reporter:  Thomas Güttler   |Owner:  nobody
   |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Uncategorized|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  unicode  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #4992: Alter cache key based on GET parameters

2012-01-09 Thread Django

#4992: Alter cache key based on GET parameters
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Cache system)  |  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #4786: Debug page traceback should highlight local code vs. framework code

2012-01-09 Thread Django

#4786: Debug page traceback should highlight local code vs. framework code
-+-
 Reporter:  Thomas Güttler   |Owner:  kevin
   |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Core (Other) |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  aug22sprint  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3672: newforms: DateField doesn't handle date output formats

2012-01-09 Thread Django

#3672: newforms: DateField doesn't handle date output formats
-+-
 Reporter:  orestis@…|Owner:  ajs
 Type:  Uncategorized|   Status:  closed
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  DateField l10n   | Triage Stage:  Accepted
  localization format input output   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #3512: Add "required" & "error" CSS classes to form rows in as_* methods

2012-01-09 Thread Django

#3512: Add "required" & "error" CSS classes to form rows in as_* methods
-+-
 Reporter:  Waylan Limberg   |Owner:  nobody
   |   Status:  closed
 Type:  Uncategorized|  Version:  SVN
Component:  Forms|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

2012-01-09 Thread Django

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
+
 Reporter:  spr@…   |Owner:  nobody
 Type:  enhancement |   Status:  closed
Component:  Contrib apps|  Version:  SVN
 Severity:  normal  |   Resolution:  wontfix
 Keywords:  ldap,usernames  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #2231: Boolean fields don't honor 'default' parameter

2012-01-09 Thread Django

#2231: Boolean fields don't honor 'default' parameter
-+-
 Reporter:  russellm |Owner:  russellm
 Type:  defect   |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  invalid
 Severity:  normal   | Triage Stage:
 Keywords:  boolean default  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16745: Different times on fields with auto_now and auto_now_add

2012-01-09 Thread Django

#16745: Different times on fields with auto_now and auto_now_add
-+-
 Reporter:  kantntreiber@…   |Owner:
 Type:  Bug  |  michaelmior
Component:  Database layer   |   Status:  new
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  auto_now,| Triage Stage:  Accepted
  auto_now_add, DateTimeField,   |  Needs documentation:  1
  DateField, field   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by akaariai):

 I will try to get some time reviewing this patch. Recording the
 transaction start time reliably could be surprisingly hard, as generally
 Django has pretty bad knowledge of when in transaction and when not. But
 it seems the proposed patch will work.

 I would like it even more if there were some way to get the actual
 database transaction start time ("SELECT now()" in PostgreSQL). But even
 as is, I think this patch has merit.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #1371: defining default settings for apps

2012-01-09 Thread Django

#1371: defining default settings for apps
--+--
 Reporter:  django@…  |Owner:  adrian
 Type:  defect|   Status:  closed
Component:  Core (Other)  |  Version:  SVN
 Severity:  normal|   Resolution:  wontfix
 Keywords:| Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by guettli):

 * cc: hv@… (removed)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #632: database stored templates

2012-01-09 Thread Django

#632: database stored templates
-+
 Reporter:  hugo |Owner:  adrian
 Type:  enhancement  |   Status:  closed
Component:  Template system  |  Version:
 Severity:  minor|   Resolution:  wontfix
 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 guettli):

 * cc: hv@… (removed)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

75 matches

Mail list logo