date:20110413

[Django] #15825: File-based caching doesn't cull truly randomly

2011-04-13 Thread Django

#15825: File-based caching doesn't cull truly randomly
---+
 Reporter:  gkuenning  | Owner:  nobody
 Type:  Bug|Status:  new
Milestone: | Component:  Core (Cache system)
  Version:  1.2|  Severity:  Normal
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+
 The culling algorithm in filebased.py uses an essentially random culling
 method, which is well known to lead to an approximation to LRU.  However,
 the randomness is improperly applied.  For example, consider a frequently-
 accessed page that, by luck, happens to sort first in the file list (due
 to an alphatbetically low hash value).  The culling code will always
 delete this file, while a truly random algorithm would only do so 1/n of
 the time.

 The fix is easy: at approximately line 131 in filebased.py, "== 0" should
 be replaced with "== ranno" where ranno is chosen in the immediately
 preceding line with:

 ranno = random.randint(0, self._cull_frequency)

-- 
Ticket URL: 
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] #15824: Modpython should catch EPIPE (produces 500 Internal Server Error)

2011-04-13 Thread Django

#15824: Modpython should catch EPIPE (produces 500 Internal Server Error)
---+--
 Reporter:  gkuenning  | Owner:  nobody
 Type:  Bug|Status:  new
Milestone: | Component:  Uncategorized
  Version:  1.2|  Severity:  Normal
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+--
 When a browser client is receiving a page and decides to go away for
 whatever reason, Apache throws an internal server error that
 eventually produces an e-mail message to the admin.  It took me quite
 a while to figure out why I was getting these random error messages.

 The problem is in modpython at around line 220:

 try:
 for chunk in response:
 req.write(chunk)
 finally:
 response.close()

 If the client closes the connection during this loop, the write will
 throw an exception.  It is my belief that this code should include an
 except clause to catch and discard EPIPE, since it's not a server
 error when clients go away.

-- 
Ticket URL: 
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] #13142: Add support for SSL connections in core.mail.backends.smtp

2011-04-13 Thread Django

#13142: Add support for SSL connections in core.mail.backends.smtp
---+---
   Reporter:  serg.partizan@…  |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Mail)
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  1|
---+---
Changes (by net147):

 * cc: net147 (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] #15050: FormWizard URLConf documentation misleading

2011-04-13 Thread Django

#15050: FormWizard URLConf documentation misleading
-+-
   Reporter:  root+django@…  |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  contrib.formtools
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:  wizard
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #4287: FloatField will not handle infinity values

2011-04-13 Thread Django

#4287: FloatField will not handle infinity values
-+-
   Reporter:  oBeattie   |Owner:  nobody
  (oliver@…  |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  infinity, mysql,
   Triage Stage:  Accepted   |  float
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by calmez):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #11052: Q-Object disjunction join promotion .. bug

2011-04-13 Thread Django

#11052: Q-Object disjunction join promotion .. bug
-+-
   Reporter:  emulbreh   |Owner:  mtredinnick
   Type:  Bug|   Status:  assigned
  Milestone:  1.3|Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:  m2m, join, null, q
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  1
-+-

Comment (by dcwatson):

 I think the problem I described in the post above is actually slightly
 different than this issue, so I've opened a new ticket: #15823

-- 
Ticket URL: 
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] #15823: incorrect join condition when combining Q objects

2011-04-13 Thread Django

#15823: incorrect join condition when combining Q objects
+-
 Reporter:  dcwatson| Owner:  dcwatson
 Type:  Bug |Status:  new
Milestone:  1.3 | Component:  Database layer (models, ORM)
  Version:  SVN |  Severity:  Normal
 Keywords:  query, q, join  |  Triage Stage:  Unreviewed
Has patch:  1   |
+-
 Originally described the issue in https://groups.google.com/d/msg/django-
 developers/4wMNF61oQNM/hqspS-Jp5rwJ but copied here for reference.

 Models:
 {{{
 class Item (models.Model):
 title = models.CharField(max_length=100)

 class PropertyValue (models.Model):
 label = models.CharField(max_length=100)

 class Property (models.Model):
 item = models.ForeignKey(Item, related_name='props')
 key = models.CharField(max_length=100)
 value = models.ForeignKey(PropertyValue, null=True)
 }}}

 Code:
 {{{
 item = Item.objects.create(title='Some Item')
 pv = PropertyValue.objects.create(label='Some Value')
 item.props.create(key='a', value=pv)
 item.props.create(key='b')
 q1 = Q(props__key='a', props__value=pv)
 q2 = Q(props__key='b', props__value__isnull=True)
 qs1 = Item.objects.filter(q1) & Item.objects.filter(q2)
 qs2 = Item.objects.filter(q2) & Item.objects.filter(q1)
 }}}

 The problem is that `qs1` and `qs2` do not evaluate to the same thing, as
 they should (`qs1` is empty). The SQL generated for `qs1` is:

 {{{
 SELECT "app_item"."id", "app_item"."title" FROM "app_item"
 INNER JOIN "app_property" ON ("app_item"."id" = "app_property"."item_id")
 LEFT OUTER JOIN "app_property" T4 ON ("app_item"."id" = T4."item_id")
 LEFT OUTER JOIN "app_propertyvalue" T5 ON ("app_property"."value_id" =
 T5."id")
 WHERE (("app_property"."value_id" = 1  AND "app_property"."key" = 'a' )
 AND (T5."id" IS NULL AND T4."key" = 'b'))
 }}}

 The problem is that the first `app_property` join corresponds to `q1`, and
 the second corresponds to `q2`. However, the `app_propertyvalue` join
 (corresponding to the `isnull` from `q2`) refers to
 `app_property.value_id` (i.e. from `q1`) instead of `T4.value_id` (i.e.
 from `q2`).

 The attached patch checks the left side of the join when combining
 queries, and if it has already been re-aliased, uses the new alias. That
 way, join conditions should reference what they referenced before the
 combination. It also has a regression test, and all tests pass.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14273: Development server does not shutdown cleanly

2011-04-13 Thread Django

#14273: Development server does not shutdown cleanly
-+-
   Reporter:  rmboggs|Owner:  nobody
   Type: |   Status:  reopened
  Cleanup/optimization   |Component:  Core (Other)
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:  runserver
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by rmboggs):

 Replying to [comment:7 julien]:
 > I think the attached patch is a bit better. Could you test it under
 OpenBSD?
 Yeah, I'll give it a try today...

-- 
Ticket URL: 
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] #15821: Django 1.3 release notes links to wrong "security issues" page

2011-04-13 Thread Django

#15821: Django 1.3 release notes links to wrong "security issues" page
--+-
   Reporter:  semenov |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Documentation
Version:  SVN | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by aaugustin):

 * has_patch:  0 => 1
 * version:  1.2 => SVN


-- 
Ticket URL: 
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] #15822: Remove references to the postgresql (v1) database backend

2011-04-13 Thread Django

#15822: Remove references to the postgresql (v1) database backend
--+--
 Reporter:  aaugustin | Owner:  nobody
 Type:  Cleanup/optimization  |Status:  new
Milestone:| Component:  Documentation
  Version:  SVN   |  Severity:  Normal
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  1 |
--+--
 The postgresql backend was removed, but some references remained in the
 documentation and project templates.

 Attached patch removes them all.

-- 
Ticket URL: 
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] #4287: FloatField will not handle infinity values

2011-04-13 Thread Django

#4287: FloatField will not handle infinity values
-+-
   Reporter:  oBeattie   |Owner:  nobody
  (oliver@…  |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  infinity, mysql,
   Triage Stage:  Accepted   |  float
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-

Comment (by calmez):

 I looked at this with django from trunk and could reproduce the bug
 (working in sqlite3, not working in mysql).[[BR]]
 I had a look at mysql an found out that it is not possible to store
 infinity values in DOUBLE columns because "Standard SQL's FLOAT (not just
 MySQL's) is *not* an IEEE754 float" [#ref1 (1)].[[BR]]
 I patched it by using the smallest (-2147483648) and the biggest
 (2147483647) float value as -inf and inf.

 Would it be okay to fix that bug that way?

 
 [=#ref1 (1)] http://forums.mysql.com/read.php?39,220571,220573#msg-220573

-- 
Ticket URL: 
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] #15049: Using annotation before and after filter gives wrong results

2011-04-13 Thread Django

#15049: Using annotation before and after filter gives wrong results
+---
   Reporter:  Alex  |Owner:
   Type:  Bug   |   Status:  new
  Milestone:|Component:  ORM aggregation
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+---
Changes (by jaddison):

 * type:   => Bug
 * severity:   => Normal
 * milestone:  1.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] #15040: Boolean fields return 0 and 1 when loaded through select_related

2011-04-13 Thread Django

#15040: Boolean fields return 0 and 1 when loaded through select_related
-+-
   Reporter:  homm   |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal
 * milestone:  1.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] #15039: The current download link redirection breaks wget making Linux download inconvenient

2011-04-13 Thread Django

#15039: The current download link redirection breaks wget making Linux download
inconvenient
-+-
   Reporter: |Owner:  nobody
  jonathanberger |   Status:  new
   Type:  Bug|Component:  Djangoproject.com Web
  Milestone: |  site
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #15033: sqlindexes doesn't create indexes for ForeignKeys on normal ManyToManyFields

2011-04-13 Thread Django

#15033: sqlindexes doesn't create indexes for ForeignKeys on normal
ManyToManyFields
-+-
   Reporter: |Owner:  nobody
  cdestigter |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  1  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #15020: Redundant joins generated when using reverse foreign key

2011-04-13 Thread Django

#15020: Redundant joins generated when using reverse foreign key
-+-
   Reporter:  adurdin|Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #15015: Mixing read-only with ability to add new instances using a FormSet

2011-04-13 Thread Django

#15015: Mixing read-only with ability to add new instances using a FormSet
--+---
   Reporter:  coleifer|Owner:  nobody
   Type:  New feature |   Status:  new
  Milestone:  |Component:  Forms
Version:  1.2 | Severity:  Normal
 Resolution:  | Keywords:  formset
   Triage Stage:  Design decision needed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+---
Changes (by anonymous):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
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] #15821: Django 1.3 release notes links to wrong "security issues" page

2011-04-13 Thread Django

#15821: Django 1.3 release notes links to wrong "security issues" page
--+-
   Reporter:  semenov |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Documentation
Version:  1.2 | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by semenov):

 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * 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] #15821: Django 1.3 release notes links to wrong "security issues" page

2011-04-13 Thread Django

#15821: Django 1.3 release notes links to wrong "security issues" page
---+--
 Reporter:  semenov| Owner:  nobody
 Type:  Uncategorized  |Status:  new
Milestone: | Component:  Uncategorized
  Version:  1.2|  Severity:  Normal
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+--
 In [[http://docs.djangoproject.com/en/dev/releases/1.3/#backwards-
 incompatible-changes-1-3|Django 1.3 release notes]], it says: "Prior to
 Django 1.2.5, the Django administrative interface allowed filtering on any
 model field or relation -- not just those specified in list_filter -- via
 query string manipulation. Due to
 [[http://www.djangoproject.com/weblog/2011/feb/08/security/|security
 issues]] reported to us, however, query string lookup arguments in the
 admin must be for fields or relations specified in list_filter or
 date_hierarchy."

 However, the linked "security issues" page doesn't mention anything about
 the admin area and list_filter. The link should either be fixed, or
 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] #15008: Convert admin views to use TemplateResponse

2011-04-13 Thread Django

#15008: Convert admin views to use TemplateResponse
-+-
   Reporter:  acdha  |Owner:  acdha
   Type: |   Status:  assigned
  Cleanup/optimization   |Component:  contrib.admin
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  templateresponse
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-
Changes (by anonymous):

 * type:   => Cleanup/optimization
 * severity:   => Normal
 * milestone:  1.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] #15007: Wrong message-tag when successfully adding an entry

2011-04-13 Thread Django

#15007: Wrong message-tag when successfully adding an entry
+-
   Reporter:  parsch|Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:|Component:  contrib.admin
Version:  1.2   | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #14976: Add is_html flag to contrib.messages

2011-04-13 Thread Django

#14976: Add is_html flag to contrib.messages
-+-
   Reporter:  tedtieken  |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  contrib.messages
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:  safe, messages, html
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  1  |
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
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] #14974: Contrib application for i18n functions

2011-04-13 Thread Django

#14974: Contrib application for i18n functions
-+-
   Reporter:  marinho|Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Internationalization
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
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] #14930: `values_list()` fails on queryset ordered by extra column

2011-04-13 Thread Django

#14930: `values_list()` fails on queryset ordered by extra column
-+-
   Reporter:  lsaffre|Owner:  nobody
   Type:  Bug|   Status:  reopened
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #14970: Inconsistency in handling of managed/unmanaged transactions

2011-04-13 Thread Django

#14970: Inconsistency in handling of managed/unmanaged transactions
-+-
   Reporter:  mwrobel|Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => New feature
 * severity:   => Normal


Comment:

 marking as new feature due to backward-compatibility concerns.

-- 
Ticket URL: 
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] #14968: handle BaseExceptions with middleware, or at least KeyboardInterrupt

2011-04-13 Thread Django

#14968: handle BaseExceptions with middleware, or at least KeyboardInterrupt
+
   Reporter:  Suor  |Owner:  Suor
   Type:  Bug   |   Status:  new
  Milestone:|Component:  Core (Other)
Version:  1.2   | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #15765: Serving static files in development doesn't work with staticfiles activated

2011-04-13 Thread Django

#15765: Serving static files in development doesn't work with staticfiles 
activated
-+-
   Reporter:  Semmel |Owner:  nobody
   Type: |   Status:  closed
  Uncategorized  |Component:  contrib.staticfiles
  Milestone: | Severity:  Normal
Version:  1.3| Keywords:
 Resolution: |Has patch:  0
  worksforme |  Needs tests:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by jezdez):

 Replying to [comment:2 Semmel]:
 > I've added a little test project to demonstrate the behavior. Just run
 it and point your browser to http://localhost:8000/static/myfolder/. Of
 course I could use `staticfiles_urlpatterns` for serving files in
 development. For this example I used `static` and added `show_indexes` as
 an easy way to see that the folder really is there
 (http://localhost:8000/static/ works as expected) but navigating to
 anything else just doesn't work.

 As I said, if you use staticfiles, the STATIC_ROOT directory won't be
 served directly but will use the staticfiles finders instead to find the
 files linked via STATIC_URL. Feel free to not use staticfiles but the
 django.core.views.static view if you just want to serve files located in
 the STATIC_ROOT directory.

 > Is there any resource for a standard staticfiles layout? I tried to peek
 at djangoproject.com but was surprised to see that it doesn't even use
 staticfiles.

 Yes, as described in the docs, by default staticfiles will look at the
 static/ directories of each app and all the directories listed in
 STATICFILES_DIRS -- similarly to how templates are structured. If you have
 "common files" that don't fit any of your apps, put them in a separate
 directory and add that directory to the STATICFILES_DIRS setting.

-- 
Ticket URL: 
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] #14967: django.contrib.auth.admin.UserAdmin.response_add changed in 1.2.4

2011-04-13 Thread Django

#14967: django.contrib.auth.admin.UserAdmin.response_add changed in 1.2.4
--+-
   Reporter:  jonas.obrist@…  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Documentation
Version:  1.2 | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Accepted|Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #14964: create_attachment support for unicode symbols in filename

2011-04-13 Thread Django

#14964: create_attachment support for unicode symbols in filename
-+-
   Reporter:  Anton  |Owner:  nobody
  Chaporgin  |   Status:  new
   Type:  New|Component:  Core (Mail)
  feature| Severity:  Normal
  Milestone: | Keywords:  email attachment,
Version:  SVN|  filenames, i18n
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by anonymous):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
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] #14958: FastCGI socket permission

2011-04-13 Thread Django

#14958: FastCGI socket permission
---+
   Reporter:  joerg|Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Other)
Version:  1.2  | Severity:  Normal
 Resolution:   | Keywords:  fastcgi
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+
Changes (by anonymous):

 * type:   => New feature
 * severity:   => Normal


-- 
Ticket URL: 
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] #14950: Javascript errors when building CHM file from django docs using Sphinx

2011-04-13 Thread Django

#14950: Javascript errors when building CHM file from django docs using Sphinx
-+-
   Reporter:  Aryeh  |Owner:  nobody
  Leib Taurog |   Status:  new
   Type:  Bug|Component:  Documentation
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:  chm javascript
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
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] #11052: Q-Object disjunction join promotion .. bug

2011-04-13 Thread Django

#11052: Q-Object disjunction join promotion .. bug
-+-
   Reporter:  emulbreh   |Owner:  mtredinnick
   Type:  Bug|   Status:  assigned
  Milestone:  1.3|Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:  m2m, join, null, q
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  1
-+-
Changes (by dcwatson):

 * type:   => Bug
 * severity:   => Normal


Comment:

 Another description of the problem and code to reproduce it is here:
 https://groups.google.com/d/msg/django-developers/4wMNF61oQNM/hqspS-Jp5rwJ

-- 
Ticket URL: 
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] #15813: STATES_NORMALIZED dict for India does not include all states

2011-04-13 Thread Django

#15813: STATES_NORMALIZED dict for India does not include all states
-+-
   Reporter:  jsdalton   |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  contrib.localflavor
  Milestone:  1.4| Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by jsdalton):

 Just a note on the patch, for some reason svn diff did not include the
 __init__.py file in the in_ directory I created, presumably because the
 file is blank? Anyhow that file obviously needs to be created for the
 tests to work.

-- 
Ticket URL: 
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] #15813: STATES_NORMALIZED dict for India does not include all states

2011-04-13 Thread Django

#15813: STATES_NORMALIZED dict for India does not include all states
-+-
   Reporter:  jsdalton   |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  contrib.localflavor
  Milestone:  1.4| Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by jsdalton):

 Okay, patch with tests included. There were no tests whatsoever for India
 previously, but I only added tests to cover the changes I made.

-- 
Ticket URL: 
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] #5833: Custom FilterSpecs

2011-04-13 Thread Django

#5833: Custom FilterSpecs
-+-
   Reporter: |Owner:  jkocherhans
  Honza_Kral |   Status:  assigned
   Type:  New|Component:  contrib.admin
  feature| Severity:  Normal
  Milestone: | Keywords:  nfa-someday
Version:  SVN|  list_filter filterspec nfa-
 Resolution: |  changelist ep2008
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by julien):

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


Comment:

 Hi guys, so I've just posted a patch with some comprehensive tests and
 doc. As it is, I think the patch is pretty robust and works as
 advertised... that is, if we agree on the various sub-features and on the
 API. So I really need to get some feedback now. If you're interested in
 getting this feature shipped in core, please come join us in this django-
 dev thread: http://groups.google.com/group/django-
 developers/browse_thread/thread/ec7c4124e7317145

 Cheers! ;)

-- 
Ticket URL: 
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] #15765: Serving static files in development doesn't work with staticfiles activated

2011-04-13 Thread Django

#15765: Serving static files in development doesn't work with staticfiles 
activated
-+-
   Reporter:  Semmel |Owner:  nobody
   Type: |   Status:  closed
  Uncategorized  |Component:  contrib.staticfiles
  Milestone: | Severity:  Normal
Version:  1.3| Keywords:
 Resolution: |Has patch:  0
  worksforme |  Needs tests:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by Semmel):

 Replying to [comment:1 jezdez]:
 > Quoting from the [http://docs.djangoproject.com/en/1.3/howto/static-
 files/#using-django-contrib-staticfiles docs]:
 >
 > "Many projects will also have static assets that aren’t tied to a
 particular app; you can give staticfiles additional directories to search
 via the STATICFILES_DIRS setting ."
 >
 > The automatic serving during development via staticfiles' runserver
 command doesn't set `show_indexes=True`. You don't have to manually add
 the static pattern to your URLs.

 I've added a little test project to demonstrate the behavior. Just run it
 and point your browser to http://localhost:8000/static/myfolder/. Of
 course I could use `staticfiles_urlpatterns` for serving files in
 development. For this example I used `static` and added `show_indexes` as
 an easy way to see that the folder really is there
 (http://localhost:8000/static/ works as expected) but navigating to
 anything else just doesn't work.

 Is there any resource for a standard staticfiles layout? I tried to peek
 at djangoproject.com but was surprised to see that it doesn't even use
 staticfiles.

-- 
Ticket URL: 
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] #13017: generic relation generates needless join

2011-04-13 Thread Django

#13017: generic relation generates needless join
-+-
   Reporter:  MS |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  database joins
   Triage Stage:  Accepted   |  generic relation
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by blacklwhite):

 * stage:  Ready for checkin => 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] #14903: wsgiref usage

2011-04-13 Thread Django

#14903: wsgiref usage
-+-
   Reporter:  maxbublis  |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  Core (Other)
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by aaugustin):

 Just updated the patch to fix a re-indentation issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #13017: generic relation generates needless join

2011-04-13 Thread Django

#13017: generic relation generates needless join
-+-
   Reporter:  MS |Owner:  nobody
   Type: |   Status:  new
  Cleanup/optimization   |Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  database joins
   Triage Stage:  Ready for  |  generic relation
  checkin|Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by blacklwhite):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #14091: Fix incorrect quoting in connection.queries

2011-04-13 Thread Django

#14091: Fix incorrect quoting in connection.queries
-+-
   Reporter:  danielr|Owner:
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by aaugustin):

 * owner:  aaugustin =>


Comment:

 I de-assign myself since I've proposed a patch and I have nothing more to
 do until someone reviews 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] #15579: Please add support to delete specialization , while preserving base class instance (multi-table inheritance)

2011-04-13 Thread Django

#15579: Please add support to delete specialization , while preserving base 
class
instance (multi-table inheritance)
-+-
   Reporter:  zimnyx |Owner:  nobody
   Type:  New|   Status:  reopened
  feature|Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by russellm):

 * status:  closed => reopened
 * resolution:  wontfix =>
 * stage:  Unreviewed => Accepted


Comment:

 My apologies -- it appears that your original report was correct. I closed
 it because I thought I had code in production that was using the trick I
 suggested; however, when I checked, it turns out I'm reparenting a child,
 not deleting 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.

[Changeset] r16026 - in django/trunk: django/core tests/regressiontests/pagination_regress

2011-04-13 Thread noreply

Author: SmileyChris
Date: 2011-04-13 04:28:42 -0700 (Wed, 13 Apr 2011)
New Revision: 16026

Modified:
   django/trunk/django/core/paginator.py
   django/trunk/tests/regressiontests/pagination_regress/tests.py
Log:
Fixes Paginator.validate_number not raising a PageNotAnInteger exception when 
passed a non-int-castable type.

Modified: django/trunk/django/core/paginator.py
===
--- django/trunk/django/core/paginator.py   2011-04-11 21:48:47 UTC (rev 
16025)
+++ django/trunk/django/core/paginator.py   2011-04-13 11:28:42 UTC (rev 
16026)
@@ -22,7 +22,7 @@
 "Validates the given 1-based page number."
 try:
 number = int(number)
-except ValueError:
+except (TypeError, ValueError):
 raise PageNotAnInteger('That page number is not an integer')
 if number < 1:
 raise EmptyPage('That page number is less than 1')

Modified: django/trunk/tests/regressiontests/pagination_regress/tests.py
===
--- django/trunk/tests/regressiontests/pagination_regress/tests.py  
2011-04-11 21:48:47 UTC (rev 16025)
+++ django/trunk/tests/regressiontests/pagination_regress/tests.py  
2011-04-13 11:28:42 UTC (rev 16026)
@@ -1,4 +1,4 @@
-from django.core.paginator import Paginator, EmptyPage
+from django.core.paginator import Paginator, EmptyPage, PageNotAnInteger
 from django.utils.unittest import TestCase
 
 class PaginatorTests(TestCase):
@@ -27,6 +27,15 @@
 "For '%s', expected %s but got %s.  Paginator parameters were: %s"
 % (name, expected, got, params))
 
+def test_invalid_page_number(self):
+"""
+Tests that invalid page numbers result in the correct exception being
+raised.
+"""
+paginator = Paginator([1, 2, 3], 2)
+self.assertRaises(PageNotAnInteger, paginator.validate_number, None)
+self.assertRaises(PageNotAnInteger, paginator.validate_number, 'x')
+
 def test_paginator(self):
 """
 Tests the paginator attributes using varying inputs.

-- 
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] #12180: ProgrammingError thrown with autocommit: True if first query on PostgreSQL >= 8.2 is an INSERT

2011-04-13 Thread Django

#12180: ProgrammingError thrown with autocommit: True if first query on 
PostgreSQL
>= 8.2 is an INSERT
-+-
   Reporter:  Xof|Owner:  Xof
   Type:  Bug|   Status:  assigned
  Milestone: |Component:  Database layer
Version:  1.1|  (models, ORM)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  1
-+-

Comment (by kmtracey):

 #15818 reported this again.

-- 
Ticket URL: 
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] #15818: PostgreSQL autocommit mode breaks initial insert

2011-04-13 Thread Django

#15818: PostgreSQL autocommit mode breaks initial insert
-+-
   Reporter:  Rick@… |Owner:  nobody
   Type:  Bug|   Status:  closed
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution:  duplicate  | Severity:  Release blocker
   Triage Stage: | Keywords:  postgresql,
  Unreviewed |  postgresql-9, autocommit
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by kmtracey):

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


Comment:

 Sounds like #12180.

-- 
Ticket URL: 
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] #15354: Cookie with CSRF token not always available for AJAX Post requests

2011-04-13 Thread Django

#15354: Cookie with CSRF token not always available for AJAX Post requests
+
   Reporter:  sayane|Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:  1.3   |Component:  contrib.csrf
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+
Changes (by lamby):

 * cc: lamby (added)
 * has_patch:  0 => 1


Comment:

 I can't think of a nice *general* fix that doesn't involve a setting - we
 really do not want to speculatively set a CSRF cookie on every response
 (ie. remove the CSRF_COOKIE_USED flag checking) as that adds "Vary:
 Cookie" everywhere, uses entropy, bloats headers, etc. However, a patch
 for a setting enabling this for certain projects would be pretty trivial
 (just check for it in CsrfMiddleware.process_response).

 My solution would be add a view decorator that ensures the CSRF cookie is
 set in the corresponding response. I'm attaching this now - it works well
 and is better than having to place a {% csrf_token %} inside a HTML
 comment or some other horrible hack.

-- 
Ticket URL: 
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] #15819: Admin searches should use distinct, if query involves joins

2011-04-13 Thread Django

#15819: Admin searches should use distinct, if query involves joins
-+-
   Reporter:  Adam   |Owner:  aip@…
  Kochanowski |   Status:  closed
   Type:  Bug|Component:  contrib.admin
  Milestone: | Severity:  Normal
Version:  1.3| Keywords:
 Resolution:  needsinfo  |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by kmtracey):

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


Comment:

 Please provide more specifics. Search is available on changelist pages,
 inlines are on edit pages, so I'm confused about what you are trying to
 report. Models, model admin configs, and instructions for reproducing what
 you are seeing would help someone diagnose. As it is there is not enough
 information here to move forward.

-- 
Ticket URL: 
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] #15811: Lazy doesn't take into account methods defined in parents

2011-04-13 Thread Django

#15811: Lazy doesn't take into account methods defined in parents
--+-
   Reporter:  abki|Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Uncategorized
Version:  SVN | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by abki):

 * 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.

Re: [Django] #15810: Easy rename of apps in admin

2011-04-13 Thread Django

#15810: Easy rename of apps in admin
-+-
   Reporter: |Owner:  nobody
  aatanasov+django@… |   Status:  closed
   Type:  New|Component:  contrib.admin
  feature| Severity:  Normal
  Milestone: | Keywords:  app_label, admin
Version:  SVN|Has patch:  1
 Resolution:  duplicate  |  Needs tests:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by anonymous):

 > The bigger issue here is app configuration; renaming the app in the
 admin is just one part of a bigger problem.
 > I should also add -- #3591 was the subject of a Google Summer of Code
 project last year, and there's lots of interest in getting that work
 integrated into trunk in the 1.4 timeframe.

 I've looked at #3591 before posting this. It's there since 4 years, patch
 changes a lot of code and tries to solve two problems at once:
 - app paths
 - give apps names

 i've tried to solve only the second, minimal changes which are backwards
 compatible.
 result is more like #10436 but with less changes
 {{{
 AppLabel('app_label',_('Translate 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] #15818: PostgreSQL autocommit mode breaks initial insert

2011-04-13 Thread Django

#15818: PostgreSQL autocommit mode breaks initial insert
-+-
   Reporter:  Rick@… |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Release blocker
   Triage Stage: | Keywords:  postgresql,
  Unreviewed |  postgresql-9, autocommit
Needs documentation:  0  |Has patch:  0
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by Rick van Hattem ):

 * keywords:   => postgresql, postgresql-9, autocommit


-- 
Ticket URL: 
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] #15818: PostgreSQL autocommit mode breaks initial insert

2011-04-13 Thread Django

#15818: PostgreSQL autocommit mode breaks initial insert
-+-
   Reporter:  Rick@… |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Database layer
Version:  SVN|  (models, ORM)
 Resolution: | Severity:  Release blocker
   Triage Stage: | Keywords:
  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by Rick van Hattem ):

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


Comment:

 This was tested in a brand new project with the latest svn (r16025).

-- 
Ticket URL: 
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] #15820: inline admin formset uses incorrect form

2011-04-13 Thread Django

#15820: inline admin formset uses incorrect form
---+--
 Reporter:  shanyu | Owner:  nobody
 Type:  Bug|Status:  new
Milestone: | Component:  contrib.admin
  Version:  1.2|  Severity:  Normal
 Keywords:  inlinemodeladmin, inlines  |  Triage Stage:  Unreviewed
Has patch:  0  |
---+--
 I have the (somewhat simplified) following code:

 {{{
 def create_foo_form(baz):
 class FooForm(forms.ModelForm):
def __init__(self, *args, **kwargs):
print "Initializing a FooForm object"
# Init stuff here
 return FooForm

 class FooInline(admin.TabularInline):
 model = Foo

 def get_formset(self, request, obj=None, **kwargs):
 if obj:
 kwargs['form'] = create_foo_form(obj)
 return super(FooInline, self).get_formset(request, obj, **kwargs)

 class BazAdmin(admin.ModelAdmin):
 inlines = [FooInline,]
 }}}

 The problem is that the inline formset always uses my custom FooForm,
 though the code above clearly chooses it only if obj is not None
 (Otherwise the default self.form should be used).

 The following code is get_fieldsets method of InlineModelAdmin.

 {{{
 def get_fieldsets(self, request, obj=None):
 if self.declared_fieldsets:
 return self.declared_fieldsets
 form = self.get_formset(request).form
 fields = form.base_fields.keys() +
 list(self.get_readonly_fields(request, obj))
 return [(None, {'fields': fields})]
 }}}

 The line "form = self.get_formset(request).form" calls get_formset method
 without providing the argument "obj". That results in using an incorrect
 form in this case. I guess the correct form would be "form =
 self.get_formset(request, obj).form".

-- 
Ticket URL: 
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] #15819: Admin searches should use distinct, if query involves joins

2011-04-13 Thread Django

#15819: Admin searches should use distinct, if query involves joins
--+--
 Reporter:  Adam Kochanowski   | Owner:  aip@…
 Type:  Bug   |Status:  new
Milestone:| Component:  contrib.admin
  Version:  1.3   |  Severity:  Normal
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  0 |
--+--
 If search on inline relation in django-admin I've got multiple same rows.
 It do search unusable... On django 1.2 it works 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.

[Django] #15818: PostgreSQL autocommit mode breaks initial insert

2011-04-13 Thread Django

#15818: PostgreSQL autocommit mode breaks initial insert
+-
 Reporter:  Rick@…  | Owner:  nobody
 Type:  Bug |Status:  new
Milestone:  | Component:  Database layer (models, ORM)
  Version:  SVN |  Severity:  Release blocker
 Keywords:  |  Triage Stage:  Unreviewed
Has patch:  0   |
+-
 Settings used:
 {{{#!python
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'django_test',   # Or path to database file if
 using sqlite3.
 'USER': '',  # Not used with sqlite3.
 'PASSWORD': '',  # Not used with sqlite3.
 'HOST': '',  # Set to empty string for
 localhost. Not used with sqlite3.
 'PORT': '',  # Set to empty string for
 default. Not used with sqlite3.
 'OPTIONS': {
 'autocommit': True,
 },
 }
 }
 }}}

 Code to reproduce:
 {{{#!python
 from django.conf import settings
 from django.contrib.auth.models import User
 user = User(username='something')
 user.save()
 }}}

 Stacktrace when executing:
 {{{#!python
 Traceback (most recent call last):
   File "test.py", line 5, in 
 user.save()
   File "django/db/models/base.py", line 461, in save
 self.save_base(using=using, force_insert=force_insert,
 force_update=force_update)
   File "django/db/models/base.py", line 554, in save_base
 result = manager._insert(values, return_id=update_pk, using=using)
   File "django/db/models/manager.py", line 195, in _insert
 return insert_query(self.model, values, **kwargs)
   File "django/db/models/query.py", line 1434, in insert_query
 return query.get_compiler(using=using).execute_sql(return_id)
   File "django/db/models/sql/compiler.py", line 795, in execute_sql
 return self.connection.ops.fetch_returned_insert_id(cursor)
   File "django/db/backends/__init__.py", line 460, in
 fetch_returned_insert_id
 return cursor.fetchone()[0]
 psycopg2.ProgrammingError: no results to fetch
 }}}

-- 
Ticket URL: 
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] #15817: ImageField having [width|height]_field set sytematically compute the image dimensions in ModelForm validation process

2011-04-13 Thread Django

#15817: ImageField having [width|height]_field set sytematically compute the 
image
dimensions in ModelForm validation process
-+-
 Reporter:  stan | Owner:  nobody
 Type:  Cleanup/optimization |Status:  new
Milestone:   | Component:  Forms
  Version:  1.3  |  Severity:  Normal
 Keywords:  ImageField, dimension,   |  Triage Stage:
  height_field, width_field, slow|  Unreviewed
Has patch:  0|
-+-
 This bug is directly related to the ticket #11084 and
 [http://groups.google.com/group/django-
 developers/browse_thread/thread/4375ac8425002e3a this discussion on Google
 Groups].

 The fact is when you submit a ModelForm of an existing instance having an
 ImageField with the image_height / image_width attributes set, the
 validation process cause the image to be systematically opened to compute
 the dimension whathever It has changed or not.

 This does not happens when these attributes are not set in the field so I
 guess we do not need the dimensions at this point.

 This is a huge overhead in some cases as you can imagine especially with
 inline_formset when you have several images related to a model ; the
 simple fact of updating one single field of the parent take ages to open
 every single image with the PIL.


 This take place during the form validation process (.is_valid()), in the
 _post_clean() method where model validation is performed.


 {{{
 self.instance.clean_fields(exclude=exclude) # forms.models.py (line 325 in
 post_clean())
 setattr(self, f.attname, f.clean(raw_value, self)) # db.models.base.py
 (line 848 in clean_fields())
 }}}


 Which lead us to the ''ImageFileDescriptor.__set__()'' and a call to
 ''update_dimension_fields'' line 314 :


 {{{
 class ImageFileDescriptor(FileDescriptor):
 """
 Just like the FileDescriptor, but for ImageFields. The only difference
 is
 assigning the width/height to the width_field/height_field, if
 appropriate.
 """
 def __set__(self, instance, value):
 previous_file = instance.__dict__.get(self.field.name)
 super(ImageFileDescriptor, self).__set__(instance, value)

 # To prevent recalculating image dimensions when we are
 instantiating
 # an object from the database (bug #11084), only update dimensions
 if
 # the field had a value before this assignment.  Since the default
 # value for FileField subclasses is an instance of
 field.attr_class,
 # previous_file will only be None when we are called from
 # Model.__init__().  The ImageField.update_dimension_fields method
 # hooked up to the post_init signal handles the Model.__init__()
 cases.
 # Assignment happening outside of Model.__init__() will trigger
 the
 # update right here.
 if previous_file is not None:
 self.field.update_dimension_fields(instance, force=True)
 }}}


 At this point, I can not see a trivial and elegant patch that does not
 break anything. A simple workaround (not tested) is to disable those
 attributes and override the model.save() to update {height|width}_field by
 myself, not so funny :-)

-- 
Ticket URL: 
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] #5863: list_display does not allow functions of referenced objects

2011-04-13 Thread Django

#5863: list_display does not allow functions of referenced objects
-+-
   Reporter:  Beat   |Owner:  nobody
  Bolli |   Status:  closed
   Type: |Component:  contrib.admin
  Uncategorized  | Severity:  Normal
  Milestone: | Keywords:  list_display
Version:  SVN|Has patch:  1
 Resolution:  wontfix|  Needs tests:  0
   Triage Stage:  Design |
  decision needed|
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-
Changes (by brillgen):

 * cc: brillgen (added)
 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 @kmtracey:
  We would have to use over a 100 extra boilerplate functions at last
 estimate since callables is being stated as the only supported means of
 getting direct fields from foreign keys...some of them are simply a text
 field that needs to be displayed as such..I have 2 questions for the
 community:
 1. Isn't there a performance impact of using a callable (select_related)
 benefit loss which could happen in case of simple FK fields required?
 If there is no impact, its irrelevant because the boiler plate code is not
 thaat much trouble
 However, if there is (and I believe there would be),
 2. Would the django admin accept a patch as long as it met the
 requirements of test cases, documentation etc etc.
 I ask because there would be nothing more frustrating than developing a
 fully featured patch against trunk just to hear that it'll never get
 accepted due to contrary design ideas :(

-- 
Ticket URL: 
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] #15811: Lazy doesn't take into account methods defined in parents

2011-04-13 Thread Django

#15811: Lazy doesn't take into account methods defined in parents
-+-
   Reporter:  abki   |Owner:  nobody
   Type:  Uncategorized  |   Status:  new
  Milestone: |Component:  Uncategorized
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by abki):

 * needs_better_patch:   => 0
 * version:  1.2 => SVN
 * 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] #7704: JS comments put after statements break make-messages.py output

2011-04-13 Thread Django

#7704: JS comments put after statements break make-messages.py output
-+-
   Reporter:  robbyd |Owner:  nedbatchelder
   Type:  Bug|   Status:  assigned
  Milestone: |Component:  Internationalization
Version:  1.0| Severity:  Normal
 Resolution: | Keywords:  djangojs, make-
   Triage Stage:  Accepted   |  messages
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  0
-+-

Comment (by Marc Demierre ):

 As the actual documentation does not even state that there are limitations
 with the message extraction from javascript files, I think that this patch
 should be used at least until the transition to Babel. The expected
 behaviour is to extract all messages wrapped in the gettext() function.

 The only real solution to the current problem for a developer is not to
 use the makemessages utility for javascript at all. I think that using the
 patch would be better than that.

 If the patch is not accepted, I propose to update the documentation to
 clearly state that javacript parsing is a hack and that it is not working
 properly.

-- 
Ticket URL: 
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] #15812: SortedDict.update() should accept tuples or generators

2011-04-13 Thread Django

#15812: SortedDict.update() should accept tuples or generators
---+
   Reporter:  slinkp   |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  Core (Other)
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  0
Patch needs improvement:  0|
---+

Comment (by lrekucki):

 Sorry for the noise, but:

 {{{ getattr(dict_, 'iteritems', None) is not None }}}

 strikes me as far less readable then:

 {{{ hasattr(dict_, 'iteritems') }}}

-- 
Ticket URL: 
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] #15092: Built-in template tags "now" don't accept simple quote

2011-04-13 Thread Django

#15092: Built-in template tags "now" don't accept simple quote
---+-
   Reporter:  ninja_otoko  |Owner:  nobody
   Type:  Bug  |   Status:  new
  Milestone:   |Component:  Template system
Version:  1.2  | Severity:  Normal
 Resolution:   | Keywords:  template tags,now
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+-
Changes (by julien):

 * 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.

Re: [Django] #15092: Built-in template tags "now" don't accept simple quote

2011-04-13 Thread Django

#15092: Built-in template tags "now" don't accept simple quote
-+-
   Reporter:  ninja_otoko|Owner:  nobody
   Type:  Uncategorized  |   Status:  new
  Milestone: |Component:  Template system
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:  template tags,now
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 Your patch for `{% now %}` looks good however I don't understand why
 you're adding a test for `{% ifequal %}`. If you've got a good reason to
 add that test, then please describe it in a new ticket, and also resubmit
 a new patch for this ticket solely addressing the `{% now %}` 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.

60 matches

Mail list logo