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

[Django]

#23: Add support for ValidationWarning
-+
 Reporter:  adrian   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by sebastian):

 * cc: sebastian.goll@… (added)
 * 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] #17204: Link to diveintopython is incorrect

[Django]

#17204: Link to diveintopython is incorrect
---+--
 Reporter:  feinzeig@… |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by russellm):

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


Comment:

 Duplicate of #17201, #17095, #17028, and probably others.

-- 
Ticket URL: 
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] #17201: URL in slice description doesn't go anywhere

[Django]

#17201: URL in slice description doesn't go anywhere
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by russellm):

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


Comment:

 Duplicate of #17201, #17095, #17028, and probably others.

-- 
Ticket URL: 
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] #17203: cache topic should mention bypass

[Django]

#17203: cache topic should mention bypass
---+--
 Reporter:  kevchrsmi@…|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:
 Severity:  Normal |   Resolution:  invalid
 Keywords:  cache nocache  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by russellm):

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


Comment:

 Appending ?nocache doesn't bypass the cache at all. All you've done is
 request a different resource -- one that wasn't cached.  If you re-request
 the ?nocache URL, you should find that the result is again cached.

-- 
Ticket URL: 
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] #17200: "View on site" link breaks when quote(object_id) != object_id

[Django]

#17200: "View on site" link breaks when quote(object_id) != object_id
---+
 Reporter:  dchandek   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by julien):

 * component:  Uncategorized => contrib.admin
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Solution 1) is the right one. Could you provide a test case? 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 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] #17205: Typo in docs/topics/http/urls.txt

[Django]

#17205: Typo in docs/topics/http/urls.txt
-+-
 Reporter:  rabio|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:
 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 julien):

 * stage:  Unreviewed => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17206: Example of ViewDoesNotExist error page in tutorial is outdated

[Django]

#17206: Example of ViewDoesNotExist error page in tutorial is outdated
-+-
 Reporter:  rabio|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:
 Severity:  Normal   |   Resolution:
 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 julien):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Ready for checkin
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 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 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] #17198: In admin results can be omitted due to pagination and inadequate ordering clauses

[Django]

#17198: In admin results can be omitted due to pagination and inadequate 
ordering
clauses
---+
 Reporter:  lukeplant  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:
 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 akaariai):

 I tested this on PostgreSQL 9.0. The only case where appending pk to the
 order by clause could have serious performance implications is if you
 have:
   - a lot of rows
   - an index on the sort_col
   - no index on sort_col, pk

 The test shows that in the above case you will get a limit 20 index scan
 if you order by the sort_col, but you will get a sequential scan + sort if
 you order by sort_col, pk. Now, if you have a lot of rows, the sort is
 going to be expensive. Of course, dropping the index on sort_col and
 creating a sort_col, pk index will solve that performance issue. If you
 don't have any index on the sort_col to begin with, you will get a seq
 scan + sort anyways.

 For a 10 rows table I measured a difference of 1ms <-> 75ms. If you
 have million rows, then the difference was 1ms <-> 1 seconds. The
 difference is likely bigger if you have lots of columns (only 2 in the
 test). In the worst case you will need to do disk IO, and the difference
 will explode to much bigger numbers.

 The fix is an index on sort_col, pk in the rare cases where that is
 needed.

-- 
Ticket URL: 
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] #16819: list_editable breaks multipage changelists

[Django]

#16819: list_editable breaks multipage changelists
-+
 Reporter:  anossov@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  admin list_editable  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by julien):

 See also #17198.

-- 
Ticket URL: 
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] #17198: In admin results can be omitted due to pagination and inadequate ordering clauses

[Django]

#17198: In admin results can be omitted due to pagination and inadequate 
ordering
clauses
---+
 Reporter:  lukeplant  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:
 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 julien):

 I agree that it's the admin that should be fixed. In fact, this is causing
 other issues with list_editable as the forms aren't always processed in a
 deterministic order: see in #16819.

 As you've suggested, I think that appending 'pk' to the list of order
 fields is probably the way to go. That would solve those two tickets at
 once.

-- 
Ticket URL: 
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] #17206: Example of ViewDoesNotExist error page in tutorial is outdated

[Django]

#17206: Example of ViewDoesNotExist error page in tutorial is outdated
---+
 Reporter:  rabio  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 Content of ViewDoesNotExist error page in third part of the tutorial is
 inconsistent with what user will actually see. Diff below corrects this.

 {{{
 --- a/docs/intro/tutorial03.txt
 +++ b/docs/intro/tutorial03.txt
 @@ -147,8 +147,7 @@ You should get a pleasantly-colored error page with
 the following message::

  ViewDoesNotExist at /polls/

 -Tried index in module polls.views. Error was: 'module'
 -object has no attribute 'index'
 +Could not import polls.views.index. View does not exist in module
 polls.views.

  This error happened because you haven't written a function ``index()`` in
 the
  module ``polls/views.py``.
 }}}

-- 
Ticket URL: 
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] #17205: Typo in docs/topics/http/urls.txt

[Django]

#17205: Typo in docs/topics/http/urls.txt
---+--
 Reporter:  rabio  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by rabio):

 * needs_docs:   => 0
 * has_patch:  0 => 1
 * component:  Uncategorized => Documentation
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17205: Typo in docs/topics/http/urls.txt

[Django]

#17205: Typo in docs/topics/http/urls.txt
---+
 Reporter:  rabio  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 There is simple typo in urls documentation as may be seen in patch below:

 {{{
 --- a/docs/topics/http/urls.txt
 +++ b/docs/topics/http/urls.txt
 @@ -688,7 +688,7 @@ This is completely valid, but it leads to problems
 when you try to do reverse
  URL matching (through the ``permalink()`` decorator or the :ttag:`url`
 template
  tag). Continuing this example, if you wanted to retrieve the URL for the
  ``archive`` view, Django's reverse URL matcher would get confused,
 because *two*
 -URLpatterns point at that view.
 +URL patterns point at that view.

  To solve this problem, Django supports **named URL patterns**. That is,
 you can
  give a name to a URL pattern in order to distinguish it from other
 patterns

 }}}

-- 
Ticket URL: 
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] #17204: Link to diveintopython is incorrect

[Django]

#17204: Link to diveintopython is incorrect
---+
 Reporter:  feinzeig@… |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 seems that diveintopython is no longer .org but now .net.  correct url is

 
http://www.diveintopython.net/regular_expressions/street_addresses.html#re.matching.2.3

-- 
Ticket URL: 
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] #17187: Incompatibility with Cherokee webserver's FastCGI handling

[Django]

#17187: Incompatibility with Cherokee webserver's FastCGI handling
-+-
 Reporter:  sciyoshi |Owner:  sam@…
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  cherokee flup| Triage Stage:
  fastcgi fcgi content-length uwsgi  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Leo):

 * easy:  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 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] #17187: Incompatibility with Cherokee webserver's FastCGI handling

[Django]

#17187: Incompatibility with Cherokee webserver's FastCGI handling
-+-
 Reporter:  sciyoshi |Owner:  sam@…
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  cherokee flup| Triage Stage:
  fastcgi fcgi content-length uwsgi  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Leo):

 * keywords:  cherokee flup fastcgi fcgi content-length => cherokee flup
 fastcgi fcgi content-length uwsgi


-- 
Ticket URL: 
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] #17187: Incompatibility with Cherokee webserver's FastCGI handling

[Django]

#17187: Incompatibility with Cherokee webserver's FastCGI handling
-+-
 Reporter:  sciyoshi |Owner:  sam@…
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  cherokee flup| Triage Stage:
  fastcgi fcgi content-length|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Leo):

 * cc: leos@… (added)


Comment:

 A similar issue happens when running against uWSGI. Django attempts to do
 a read() even if the content-length us explicitly set to zero. The result
 is that the read() call blocks.

 It should properly distinguish between unknown content-length (when trying
 to read might make sense) and one explicitly set to zero.

 The repro in my case is really simple. Get the latest uWSGI, spin up
 simple django app, send a post with nothing in 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.

[Django] #17203: cache topic should mention bypass

[Django]

#17203: cache topic should mention bypass
---+---
 Reporter:  kevchrsmi@…|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Documentation  |Version:
 Severity:  Normal |   Keywords:  cache nocache
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+---
 I've recently implemented '''caching''' on a project.  But, I really
 needed to be able to bypass the cache on an ad-hoc basis.  Just on a lark
 I tried appending "'''?nocache'''" to the URL and it worked.  This tidbit
 should be mentioned in the cache topic.  Thanks.

 K.C.

-- 
Ticket URL: 
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] #17201: URL in slice description doesn't go anywhere

[Django]

#17201: URL in slice description doesn't go anywhere
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by jfilipe):

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


Comment:

 Url is supposed to be:
 http://diveintopython.net/native_data_types/lists.html#odbchelper.list.slice
 instead of .org.

-- 
Ticket URL: 
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] #17202: Double max_length using inspectdb with Oracle

[Django]

#17202: Double max_length using inspectdb with Oracle
-+-
 Reporter:  rodolfo.3+django@…   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Database layer   |Version:  1.3
  (models, ORM)  |   Keywords:  inspectdb oracle
 Severity:  Normal   |  max_length
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I created a table in a Oracle database with a "NVARCHAR2" field with
 size=150:

 {{{
 CREATE table "TEST" (
 "CHAR_150"   NVARCHAR2(150)
 )
 }}}

 Then, when I run "manage.py inspectdb", the generated code is:

 {{{
 class Test(models.Model):
 char_150 = models.CharField(max_length=300, blank=True)
 class Meta:
 db_table = u'test'
 }}}

 A field type "'''NVARCHAR2(150)'''" generate a "'''max_length=300'''"
 CharField.

-- 
Ticket URL: 
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] #17194: Auth tests failing on non-US locales

[Django]

#17194: Auth tests failing on non-US locales
+
 Reporter:  hcarvalhoalves  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:  SVN
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+

Comment (by claudep):

 Note also that the latest patch might also fix #13394 and #16366. (see
 also #9156)

-- 
Ticket URL: 
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] #17200: "View on site" link breaks when quote(object_id) != object_id

[Django]

#17200: "View on site" link breaks when quote(object_id) != object_id
---+--
 Reporter:  dchandek   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  SVN
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by dchandek):

 * cc: dchandek (added)
 * needs_better_patch:   => 0
 * 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.

Re: [Django] #10853: Django unit test fails when using the dummy cache backend.

[Django]

#10853: Django unit test fails when using the dummy cache backend.
---+
 Reporter:  stavros|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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 claudep):

 * needs_better_patch:  1 => 0
 * ui_ux:   => 0
 * easy:   => 0


Comment:

 Attached patch try to explicitely set the cache to LocMem instead of
 skipping the test when the dummy backend is setup.

-- 
Ticket URL: 
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] #17201: URL in slice description doesn't go anywhere

[Django]

#17201: URL in slice description doesn't go anywhere
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Documentation on template builtins:
 https://docs.djangoproject.com/en/1.3/ref/templates/builtins/?from=olddocs

 Refers to a URL in the '''slice''' documentation:

 See
 http://diveintopython.org/native_data_types/lists.html#odbchelper.list.slice
 for an introduction.

 And that URL is dead.

-- 
Ticket URL: 
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] #17200: "View on site" link breaks when quote(object_id) != object_id

[Django]

#17200: "View on site" link breaks when quote(object_id) != object_id
---+
 Reporter:  dchandek   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  SVN
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  0
---+
 The change_view method of django.contrib.admin.options.ModelAdmin returns
 object_id as passed in.  This means that the "View on site" link breaks in
 cases where the django.contrib.admin.util.quote(object_id) != object_id.

 There are two possible solutions:
 1) Call django.contrib.admin.util.unquote() on object_id before returning
 to change_view template;
 2) Call django.contrib.admin.util.unquote() on object_id in
 django.contrib.contenttypes.views.shortcut in this line: obj =
 content_type.get_object_for_this_type(pk=object_id).

 Attached are svn diffs for each.

-- 
Ticket URL: 
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] #17194: Auth tests failing on non-US locales

[Django]

#17194: Auth tests failing on non-US locales
+
 Reporter:  hcarvalhoalves  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:  SVN
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+

Comment (by claudep):

 After discussion with Julien on irc, I've come with a radically different
 approach, with a new DefaultSettingsTestCase class that strives to
 completely isolate the contrib.auth tests from custom project settings.

-- 
Ticket URL: 
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] #17199: Base Template Loader should return the origin

[Django]

#17199: Base Template Loader should return the origin
-+--
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Kronuz):

 I'm now not sure if template loaders should return the tempalte and the
 origin, or the template and the display_name. I guess they should return
 the origin instead, as it has more information... as BaseLoader returns
 display_name, but seemingly, cached template loader returns origin... My
 patch returns display_name (from origin.name).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #17199: Base Template Loader should return the origin

[Django]

#17199: Base Template Loader should return the origin
-+--
 Reporter:  Kronuz   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Kronuz):

 * cc: Kronuz (added)
 * needs_better_patch:   => 0
 * component:  Uncategorized => Template system
 * needs_tests:   => 0
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => 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] #17199: Base Template Loader should return the origin

[Django]

#17199: Base Template Loader should return the origin
---+
 Reporter:  Kronuz |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I've been trying to get the origin from the loaders, but the origin was
 lost when BaseLoader didn't return it. I believe it should return
 origin... any thoughts? I'm attaching a 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.

[Django] #17198: In admin results can be omitted due to pagination and inadequate ordering clauses

[Django]

#17198: In admin results can be omitted due to pagination and inadequate 
ordering
clauses
-+
   Reporter:  lukeplant  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 In the admin, pagination is achieved using LIMIT/OFFSET. However, if the
 ordering specified in the SQL does not totally define an order of rows,
 LIMIT/OFFSET is not deterministic with respect to exactly which rows are
 returned.

 For example, using django.contrib.auth, and suppose you have hundreds of
 users with `is_staff == False`. Then,
 `User.objects.order_by('is_staff')[0:20]` must return those with `is_staff
 == False`, (since these sort first), but it can return any of them. If you
 then ask it for `User.objects.order_by('is_staff')[20:40]`, it is
 perfectly free to give you same 20 as the first time - since by the same
 token it can return any of them.

 This means that if you are in the admin, looking at the `User` list and
 you have ordered by `is_staff`, paging through the results is not
 guaranteed to show you all rows - it could duplicate some and omit others.

 I have observed this behaviour in the wild with Postgres. The client in
 question was extremely confused as to why, when sorting by a certain
 boolean field, some results disappeared, and I was stumped for a while. I
 also confirmed from a Django shell that a series of consecutive 'slices'
 of a `QuerySet` can return some rows twice and some not at all.

 We can argue that the database is being completely correct in what it is
 returning, because the question asked is a silly question - you can't
 deterministically take items X to Y of a set that doesn't have a strict
 total order. But I don't think we can argue that this is not a bug in the
 admin - the admin should not be asking the database silly questions.

 It applies to any situation where the ordering does not totally define the
 order of results returned. It's especially serious for booleans, because
 at least half your dataset will share a value.

 One possible solution would be to add an ordering by 'pk' to whatever is
 explicitly chosen - so you would have `User.objects.order_by('is_staff',
 'pk')`. I don't know what performance impact this would have, however.

-- 
Ticket URL: 
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] #16903: Add '--no-location' option for 'makemessages' command

[Django]

#16903: Add '--no-location' option for 'makemessages' command
-+-
 Reporter:  alpar|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by julien):

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


Comment:

 In [17081]:
 {{{
 #!CommitTicketReference repository="" revision="17081"
 Fixed #16903 -- Added `--no-location` option to the `makemessages` command
 to not write '#: filename:line' comment lines in language files. Thanks to
 alpar for the suggestion and 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] r17081 - in django/trunk: django/core/management/commands docs/ref docs/releases tests/regressiontests/i18n tests/regressiontests/i18n/commands

[noreply]

Author: julien
Date: 2011-11-11 05:07:14 -0800 (Fri, 11 Nov 2011)
New Revision: 17081

Modified:
   django/trunk/django/core/management/commands/makemessages.py
   django/trunk/docs/ref/django-admin.txt
   django/trunk/docs/releases/1.4.txt
   django/trunk/tests/regressiontests/i18n/commands/extraction.py
   django/trunk/tests/regressiontests/i18n/tests.py
Log:
Fixed #16903 -- Added `--no-location` option to the `makemessages` command to 
not write '#: filename:line' comment lines in language files. Thanks to alpar 
for the suggestion and patch.

Modified: django/trunk/django/core/management/commands/makemessages.py
===
--- django/trunk/django/core/management/commands/makemessages.py
2011-11-11 12:25:53 UTC (rev 17080)
+++ django/trunk/django/core/management/commands/makemessages.py
2011-11-11 13:07:14 UTC (rev 17081)
@@ -115,6 +115,7 @@
 
 def make_messages(locale=None, domain='django', verbosity='1', all=False,
 extensions=None, symlinks=False, ignore_patterns=[], no_wrap=False,
+no_location=False,
 no_obsolete=False):
 """
 Uses the locale directory from the Django SVN tree or an application/
@@ -163,6 +164,7 @@
 languages = [os.path.basename(l) for l in locale_dirs]
 
 wrap = no_wrap and '--no-wrap' or ''
+location = no_location and '--no-location' or ''
 
 for locale in languages:
 if verbosity > 0:
@@ -191,11 +193,11 @@
 finally:
 f.close()
 cmd = (
-'xgettext -d %s -L C %s --keyword=gettext_noop '
+'xgettext -d %s -L C %s %s --keyword=gettext_noop '
 '--keyword=gettext_lazy --keyword=ngettext_lazy:1,2 '
 '--keyword=pgettext:1c,2 --keyword=npgettext:1c,2,3 '
 '--from-code UTF-8 --add-comments=Translators -o - "%s"' % 
(
-domain, wrap, os.path.join(dirpath, thefile)
+domain, wrap, location, os.path.join(dirpath, thefile)
 )
 )
 msgs, errors = _popen(cmd)
@@ -235,14 +237,14 @@
 if verbosity > 1:
 sys.stdout.write('processing file %s in %s\n' % (file, 
dirpath))
 cmd = (
-'xgettext -d %s -L Python %s --keyword=gettext_noop '
+'xgettext -d %s -L Python %s %s --keyword=gettext_noop '
 '--keyword=gettext_lazy --keyword=ngettext_lazy:1,2 '
 '--keyword=ugettext_noop --keyword=ugettext_lazy '
 '--keyword=ungettext_lazy:1,2 --keyword=pgettext:1c,2 '
 '--keyword=npgettext:1c,2,3 --keyword=pgettext_lazy:1c,2 '
 '--keyword=npgettext_lazy:1c,2,3 --from-code UTF-8 '
 '--add-comments=Translators -o - "%s"' % (
-domain, wrap, os.path.join(dirpath, thefile))
+domain, wrap, location, os.path.join(dirpath, thefile))
 )
 msgs, errors = _popen(cmd)
 if errors:
@@ -272,8 +274,8 @@
 os.unlink(os.path.join(dirpath, thefile))
 
 if os.path.exists(potfile):
-msgs, errors = _popen('msguniq %s --to-code=utf-8 "%s"' %
-  (wrap, potfile))
+msgs, errors = _popen('msguniq %s %s --to-code=utf-8 "%s"' %
+  (wrap, location, potfile))
 if errors:
 os.unlink(potfile)
 raise CommandError(
@@ -284,8 +286,8 @@
 f.write(msgs)
 finally:
 f.close()
-msgs, errors = _popen('msgmerge %s -q "%s" "%s"' %
-  (wrap, pofile, potfile))
+msgs, errors = _popen('msgmerge %s %s -q "%s" "%s"' %
+  (wrap, location, pofile, potfile))
 if errors:
 os.unlink(potfile)
 raise CommandError(
@@ -301,8 +303,8 @@
 f.close()
 os.unlink(potfile)
 if no_obsolete:
-msgs, errors = _popen('msgattrib %s -o "%s" --no-obsolete 
"%s"' %
-  (wrap, pofile, pofile))
+msgs, errors = _popen('msgattrib %s %s -o "%s" --no-obsolete 
"%s"' %
+  (wrap, location, pofile, pofile))
 if errors:
 raise CommandError(
 "errors happened while running msgattrib\n%s" % errors)
@@ -327,6 +329,8 @@
 default=True, help="Don't ignore the common glob-style patterns 
'CVS', '.*' and '*~'."),
 make_option('--no-wrap', action='store_true', dest='no_wrap',
 default=False, help="Don't break long message lines into sever

Re: [Django] #17194: Auth tests failing on non-US locales

[Django]

#17194: Auth tests failing on non-US locales
+
 Reporter:  hcarvalhoalves  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.auth|  Version:  SVN
 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 claudep):

 * has_patch:  0 => 1


Comment:

 Here's my proposal to fix it. Just setting LANGUAGE_CODE isn't sufficient
 to change current language, that's why I changed override_settings to
 special-case LANGUAGE_CODE setting change. Might be useful in other tests,
 too.

 The other solution would be to enclose each string comparison test with
 translation.override, but it seems not very DRY 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 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] #16903: Add '--no-location' option for 'makemessages' command

[Django]

#16903: Add '--no-location' option for 'makemessages' command
-+-
 Reporter:  alpar|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by julien):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks great, thank you!

-- 
Ticket URL: 
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] #17197: Fix translation leakage in the test_suite

[Django]

#17197: Fix translation leakage in the test_suite
---+--
 Reporter:  apollo13   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  SVN
 Severity:  Release blocker|   Resolution:  fixed
 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 julien):

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


Comment:

 In [17080]:
 {{{
 #!CommitTicketReference repository="" revision="17080"
 Fixed #17197 -- Prevented a locale leakage from an i18n test causing
 collateral failures in the rest of the test suite. Thanks to Florian
 Apolloner for the report and 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] r17080 - django/trunk/tests/regressiontests/views/tests

[noreply]

Author: julien
Date: 2011-11-11 04:25:53 -0800 (Fri, 11 Nov 2011)
New Revision: 17080

Modified:
   django/trunk/tests/regressiontests/views/tests/i18n.py
Log:
Fixed #17197 -- Prevented a locale leakage from an i18n test causing collateral 
failures in the rest of the test suite. Thanks to Florian Apolloner for the 
report and patch.

Modified: django/trunk/tests/regressiontests/views/tests/i18n.py
===
--- django/trunk/tests/regressiontests/views/tests/i18n.py  2011-11-10 
08:41:21 UTC (rev 17079)
+++ django/trunk/tests/regressiontests/views/tests/i18n.py  2011-11-11 
12:25:53 UTC (rev 17080)
@@ -6,7 +6,7 @@
 
 from django.conf import settings
 from django.test import TestCase
-from django.utils.translation import override, activate
+from django.utils.translation import override, activate, get_language
 from django.utils.text import javascript_quote
 
 from ..urls import locale_dir
@@ -25,6 +25,7 @@
 
 def test_jsi18n(self):
 """The javascript_catalog can be deployed with language settings"""
+saved_lang = get_language()
 for lang_code in ['es', 'fr', 'ru']:
 activate(lang_code)
 catalog = gettext.translation('djangojs', locale_dir, [lang_code])
@@ -37,6 +38,7 @@
 if lang_code == 'fr':
 # Message with context (msgctxt)
 self.assertContains(response, "['month name\x04May'] = 
'mai';", 1)
+activate(saved_lang)
 
 
 class JsI18NTests(TestCase):

-- 
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] #17196: Typo on staticfiles page

[Django]

#17196: Typo on staticfiles page
---+
 Reporter:  caa|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:
 Severity:  Normal |   Resolution:
 Keywords:  Typo   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by julien):

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


Comment:

 Thank you for the report. If you could provide a patch that would be
 great.

-- 
Ticket URL: 
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] #17197: Fix translation leakage in the test_suite

[Django]

#17197: Fix translation leakage in the test_suite
---+--
 Reporter:  apollo13   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  SVN
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by apollo13):

 Updated patch as suggested by julien.

-- 
Ticket URL: 
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] #17197: Fix translation leakage in the test_suite

[Django]

#17197: Fix translation leakage in the test_suite
---+--
 Reporter:  apollo13   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  SVN
 Severity:  Release blocker|   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by apollo13):

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


Comment:

 New patch which doesn't make the fixed test a noop ;)

-- 
Ticket URL: 
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] #17197: Fix translation leakage in the test_suite

[Django]

#17197: Fix translation leakage in the test_suite
---+
 Reporter:  apollo13   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  SVN
 Severity:  Release blocker|   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  0  |  UI/UX:  0
---+
 As currently seen by http://ci.django-cms.org/job/Django/ we do have a
 translation leakage in the testsuite. Although it doesn't seem to manifest
 on all systems a paired testrun should give you errors as soon as you pair
 it with views, or just run the testsuite for "views admin_filters".
 Attached is a patch which fixes the translation leakage.

-- 
Ticket URL: 
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] #16426: sqlite: Cannot delete more than 999 things if there is a relation pointing to them

[Django]

#16426: sqlite: Cannot delete more than 999 things if there is a relation 
pointing
to them
-+-
 Reporter:  kmtracey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (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:  0|
-+-

Comment (by anonymous):

 Never mind, it was easier just to recompile python and then copy the
 sqlite3.dll and _sqlite.pyd files into my install. I changed the limit to
 MAX_INT. A better solution would be for the sqlite3 python module to
 expose the int sqlite3_limit(sqlite3*, int id, int newVal) runtime method.

-- 
Ticket URL: 
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] #17196: Typo on staticfiles page

[Django]

#17196: Typo on staticfiles page
---+
 Reporter:  caa|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:
 Severity:  Normal |   Keywords:  Typo
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I just happened to notice in the
 [https://docs.djangoproject.com/en/dev/ref/contrib/staticfiles/#s-static
 Template Tags section] that configured is misspelled as configued

 I can make a patch if required

-- 
Ticket URL: 
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] #9586: Shall upload_to return an urlencoded string or not?

[Django]

#9586: Shall upload_to return an urlencoded string or not?
-+-
 Reporter:  eibaan   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  1.0
  uploads/storage|   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
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
 * 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] #16630: Support for HTML5 input types

[Django]

#16630: Support for HTML5 input types
-+
 Reporter:  jonash   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  html5| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by rm_):

 * cc: riccardo.magliocchetti@… (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.