[Django] #11056: wrong object listed as a dependency in storage doc

[Django]

#11056: wrong object listed as a dependency in storage doc
---+
 Reporter:  wam|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 at http://docs.djangoproject.com/en/dev/ref/files/storage/#storage-save-
 name-content  the following statement is made:
 {{{
 The content argument must be an instance of django.db.files.File or of a
 subclass of File.
 }}}
 That URL corresponds to:
 django/docs/ref/files/storage.txt which includes the following text:
 {{{
 The ``content`` argument must be an instance of
 :class:`django.db.files.File` or of a subclass of
 :class:`~django.db.files.File`.
 }}}

 In fact, there is no django.db.files.File object defined. I suspect the
 actual object that the documentation refers to is
 django.core.files.File. I'll attach a patch against the doc that corrects
 this mistake.

-- 
Ticket URL: 
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] r10724 - django/branches/releases/1.0.X

[noreply]

Author: russellm
Date: 2009-05-09 00:31:19 -0500 (Sat, 09 May 2009)
New Revision: 10724

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X] Updated svnmerge properties for recent checkins


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275,10281,10315,10317-10318,10323,10326-10327,10330-10332,10345-10347,10352,10357,10364,10369-10370,10381-10385,10408-10410,10412,10428,10438-10439,10443,10446,10451,10454-10456,10465,10468,10481,10486-10488,10493-10494,10498,10506-10507,10510,10515-10516,10521-10523,10526-10527,10529,10538,10549,10558-10560,10562,10565-10566,10572,10575,10579,10590,10593-10594,10597-10598,10602,10621,10641-10642,10648,10677-10678
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275,10281,10315,10317-10318,10323,10326-10327,10330-10332,10345-10347,10352,10357,10364,10369-10370,10381-10385,10408-10410,10412,10428,10438-10439,10443,10446,10451,10454-10456,10465,10468,10481,10486-10488,10493-10494,10498,10506-10507,10510,10515-10516,10521-10523,10526-10527,10529,10538,10549,10558-10560,10562,10565-10566,10572,10575,10579,10590,10593-10594,10597-10598,10602,10621,10641-10642,10648,10677-10678,10681
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990-10001,10003-10004,10007,10009-10010,10013-10017,10019-10020,10022-10025,10031,10036-10041,10049-10052,10054-10061,10066-10069,10071-10076,10078-10079,10085-10087,10104,10106,10125-10127,10136,10138-10140,10143,10145-10147,10149-10160,10163-10167,10170,10173,10175-10176,10180,10185,10189,10192-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10314,10316,10319-10322,10324-10325,10328-10329,10333-10344,10348-10351,10353-10356,10358-10363,10365-10368,10371-10380,10386-10407,10411,10413-10427,10429-10437,10440-10442,10444-10445,10447-10450,10452-10453,10457-10464,10466-10467,10469-10480,10482-10485,10489-10492,10495-10497,10499-10504,10508-10509,10511-10514,10517-10520,10524-10525,10528,10530-10535,10536-10537,10539-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10601,10603-10620,10643,10646,10652,10654-10655,10659-10660,10666-10669,10675
   + 

Re: [Django] #9230: Iterating over checkboxes in CheckboxSelectMultiple should be possible

[Django]

#9230: Iterating over checkboxes in CheckboxSelectMultiple should be possible
--+-
  Reporter:  mtredinnick  | Owner:  mtredinnick
Status:  new  | Milestone: 
 Component:  Forms|   Version:  1.0
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by BradMcGonigle):

 I also just ran into a use-case for this so another +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] #9751: project_directory calculated incorrectly when "settings" is a directory (breaks 'startapp')

[Django]

#9751: project_directory calculated incorrectly when "settings" is a directory
(breaks 'startapp')
+---
  Reporter:  lamby  | Owner:  gsong 
  
Status:  assigned   | Milestone:  1.1   
  
 Component:  django-admin.py|   Version:  1.0   
  
Resolution: |  Keywords:  
startapp,settings,module
 Stage:  Ready for checkin  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Comment (by gsong):

 The reason for using `sys.modules` lookup instead of `import_module()` was
 to '''prevent''' the setting module from unnecessarily being imported
 again, since it would have to have been imported by this point.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #11055: ImageField uploads fail at r10717

[Django]

#11055: ImageField uploads fail at r10717
--+-
 Reporter:  timo  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  File uploads/storage  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 When uploading an image in the admin I get the error: {{{Upload a valid
 image. The file you uploaded was either not an image or a corrupted
 image.}}} r10717 seems to have introduced the bug as r10716 works fine.

-- 
Ticket URL: 
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] #10663: Serbian translations

[Django]

#10663: Serbian translations
---+
  Reporter:  Branko Vukelic   | Owner:  
nobody 
Status:  new   | Milestone:  
1.1
 Component:  Translations  |   Version:  
SVN
Resolution:|  Keywords:  
Serbian
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by janos):

  * needs_better_patch:  1 => 0

Comment:

 Here is a patch from Serbian translation team. It includes Serbian and
 Serbian Latin translations. We agreed that the code for Serbian Latin
 translation should be sr_Latn. There were some discussions on django-i18n
 list about that.

 Please consider this patch for 1.1 version because it is updated against
 recent SVN revision.

-- 
Ticket URL: 
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] #9093: Extend inclusion tag syntax to allow custom templates

[Django]

#9093: Extend inclusion tag syntax to allow custom templates
-+--
  Reporter:  exo...@gmail.com| Owner:  nobody   
Status:  new | Milestone:   
 Component:  Template system |   Version:  1.0  
Resolution:  |  Keywords:  inclusion
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Comment (by andrewbadr):

 Even if you're willing to write multiple inclusion tags for some finite
 number of templates that take the same context, you have to write a
 wrapper around the context function. (Django won't let you use the same
 function for multiple inclusion tags.) One possible workaround might be to
 do {% with inclusion_template as 'whatever'%}{% show_result %}{% endwith
 %} and show_result would render a template that `include`s the
 `inclusion_template` that it gets from the context.

-- 
Ticket URL: 
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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
---+
  Reporter:  ikelly| Owner: 

Status:  new   | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  oracle 
postgresql mysql schemas
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Changes (by Tarken):

 * cc: Tarken (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] #11054: Small typo in docs/howto/auth-remote-user.txt

[Django]

#11054: Small typo in docs/howto/auth-remote-user.txt
+---
  Reporter:  Jan Hülsbergen | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1-beta-1
Resolution: |  Keywords:  typo  
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * keywords:  => typo
  * 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] #11037: Support HTTPOnly cookie for HttpResponse.set_cookie

[Django]

#11037: Support HTTPOnly cookie for HttpResponse.set_cookie
-+--
  Reporter:  hvendelbo   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  HTTP handling   |   Version:  SVN   
Resolution:  duplicate   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by hvendelbo):

 I did search for httponly and set_cookie, didn't find anything

 Anyway, I added a couple of doctests for HttpResponse that might be useful

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

Re: [Django] #11054: Small typo in docs/howto/auth-remote-user.txt

[Django]

#11054: Small typo in docs/howto/auth-remote-user.txt
-+--
  Reporter:  Jan Hülsbergen  | Owner:  nobody
Status:  new | Milestone:
 Component:  Documentation   |   Version:  1.1-beta-1
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

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

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

[Django] #11054: Small typo in docs/howto/auth-remote-user.txt

[Django]

#11054: Small typo in docs/howto/auth-remote-user.txt
+---
 Reporter:  Jan Hülsbergen  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Documentation   | Version:  1.1-beta-1
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I found a small typo in said file. Path attached.

-- 
Ticket URL: 
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

[Django]

#11052: Q-Object disjunction join promotion .. bug
---+
  Reporter:  emulbreh  | Owner:  
mtredinnick   
Status:  assigned  | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  m2m, join, 
null, q
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

  * owner:  nobody => mtredinnick
  * needs_better_patch:  => 0
  * status:  new => assigned
  * 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] #2705: [patch] Add optional FOR UPDATE clause to QuerySets

[Django]

#2705: [patch] Add optional FOR UPDATE clause to QuerySets
---+
  Reporter:  Hawkeye   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by sfllaw):

 * cc: si...@akoha.com (added)

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

[Django] #11053: access to OneToOneField when null=True should return None instead of raising DoesNotExist

[Django]

#11053: access to OneToOneField when null=True should return None instead of
raising DoesNotExist
---+
 Reporter:  Harm Geerts   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Database layer (models, ORM)   | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 {{{
 class Place(models.Model):
 name = models.CharField(max_length=50)

 class UndergroundBar(models.Model):
 place = models.OneToOneField(Place, null=True)
 }}}

 Django behaves differently with access to the OneToOneField depending on
 which side of the relation is used.
 Currently UndergroundBar.place will return None while Place.undergroundbar
 raises DoesNotExist.

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

[Django]

#11052: Q-Object disjunction join promotion .. bug
--+-
 Reporter:  emulbreh  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  m2m, join, null, q|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 (someone who understands why this fails should fix the summary)

 Here's a minimal test:
 {{{
 #!python
 from unittest import TestCase
 from django.db import models

 class A(models.Model):
 name = models.CharField(max_length=30)
 bs = models.ManyToManyField('B')

 class B(models.Model):
 name = models.CharField(max_length=30)
 c = models.ForeignKey('C')

 class C(models.Model):
 name = models.CharField(max_length=30)

 class ABCTest(TestCase):
 def test(self):
 c = C.objects.create(name='the c')
 b = B.objects.create(c=c, name='the b')
 a_with_b = A.objects.create(name='a with b')
 a_with_b.bs.add(b)
 a_without_b = A.objects.create(name='a without b')

 q0 = models.Q(name__contains='without')
 q1 = models.Q(bs__name__contains='foo')
 q2 = models.Q(bs__c__name__contains='foo')

 self.assertEqual([a_without_b], list(A.objects.filter(q0)))
 self.assertEqual([a_without_b], list(A.objects.filter(q0 | q1)))
 self.assertEqual([a_without_b], list(A.objects.filter(q0 | q2)))

 # this fails:
 self.assertEqual([a_without_b], list(A.objects.filter(q0 | q1 |
 q2)))

 }}}
 The offensive query (edited for readabiliy):
 {{{
 #!sql
 SELECT a.id, a.name
 FROM a
   LEFT OUTER JOIN a_bs ON (a.id = a_bs.a_id)
   LEFT OUTER JOIN b ON (a_bs.b_id = b.id)
   INNER JOIN c ON (b.c_id = c.id)
 WHERE (a.name LIKE %without% OR b.name LIKE %foo% OR c.name LIKE %foo%)
 }}}

 Obviously this `INNER JOIN` should be a `LEFT OUTER JOIN`.

-- 
Ticket URL: 
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] #11051: Oracle backend fails null_fk regression tests

[Django]

#11051: Oracle backend fails null_fk regression tests
--+-
 Reporter:  mboersma  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  Oracle oracle |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 These must be due to Oracle's nonstandard handling of NULL vs. empty
 string for VARCHAR columns.

 {{{
 C:\projects\django-trunk\tests>runtests.py --settings=testsettings.oracle
 null_fk
 ==
 FAIL: Doctest: regressiontests.null_fk.models.__test__.API_TESTS
 --
 Traceback (most recent call last):
   File "C:\projects\django-trunk\django\test\_doctest.py", line 2180, in
 runTest
 raise self.failureException(self.format_failure(new.getvalue()))
 AssertionError: Failed doctest test for
 regressiontests.null_fk.models.__test__.API_TESTS
   File "C:\projects\django-trunk\tests\regressiontests\null_fk\models.py",
 line unknown line number, in API_TESTS

 --
 File "C:\projects\django-trunk\tests\regressiontests\null_fk\models.py",
 line ?, in regressiontests.null_fk.models.__test__.API_TESTS
 Failed example:
 [(c.id, c.comment_text, c.post) for c in comments]
 Exception raised:
 Traceback (most recent call last):
   File "C:\projects\django-trunk\django\test\_doctest.py", line 1267,
 in __run
 compileflags, 1) in test.globs
   File "", line 1, in
 
 [(c.id, c.comment_text, c.post) for c in comments]
   File "C:\projects\django-trunk\django\db\models\base.py", line 325,
 in __repr__
 u = unicode(self)
 TypeError: coercing to Unicode: need string or buffer, NoneType found
 --
 File "C:\projects\django-trunk\tests\regressiontests\null_fk\models.py",
 line ?, in regressiontests.null_fk.models.__test__.API_TESTS
 Failed example:
 Comment.objects.select_related('post').filter(post__isnull=True)[0].post
 is None
 Expected:
 True
 Got:
 False
 }}}

 This happens in the pre-1.1 trunk as of revision [10723]. It hasn't caused
 real-world problems as far as I know, but I've entered it here as a bug so
 we don't lose track of 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] #11048: Oracle raises KeyError in IntrospectionTests.test_get_indexes

[Django]

#11048: Oracle raises KeyError in IntrospectionTests.test_get_indexes
---+
  Reporter:  mboersma  | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:  duplicate |  Keywords:  Oracle 
oracle
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by mboersma):

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

Comment:

 Ian Kelly points out this is actually another case of the capitalization
 problem in #11050.

-- 
Ticket URL: 
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] #11050: Oracle fails introspection tests due to capitalization

[Django]

#11050: Oracle fails introspection tests due to capitalization
--+-
 Reporter:  mboersma  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  Oracle oracle |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The Oracle backend fails two introspection tests currently, I think
 because it expects lower-case identifiers when Oracle returns ALL_CAPS
 names by default.

 {{{
 C:\projects\django-trunk\tests>runtests.py --settings=testsettings.oracle
 introspection
 ...
 ==
 FAIL: test_get_table_description_names
 (regressiontests.introspection.tests.IntrospectionTests)
 --
 Traceback (most recent call last):
   File "C:\projects\django-
 trunk\tests\regressiontests\introspection\tests.py", line 28, in _inner
 return func(*args, **kwargs)
   File "C:\projects\django-
 trunk\tests\regressiontests\introspection\tests.py", line 74, in
 test_get_table_description_names
 [f.column for f in Reporter._meta.fields])
 AssertionError: ['ID', 'FIRST_NAME', 'LAST_NAME', 'EMAIL'] != ['id',
 'first_name', 'last_name', 'email']
 }}}

 {{{
 ...
 ==
 FAIL: test_table_names
 (regressiontests.introspection.tests.IntrospectionTests)
 --
 Traceback (most recent call last):
   File "C:\projects\django-
 trunk\tests\regressiontests\introspection\tests.py", line 28, in _inner
 return func(*args, **kwargs)
   File "C:\projects\django-
 trunk\tests\regressiontests\introspection\tests.py", line 47, in
 test_table_names
 "'%s' isn't in table_list()." % Reporter._meta.db_table)
 AssertionError: 'introspection_reporter' isn't in table_list().
 }}}

 This happens in both the 1.0.x maintenance branch and the pre-1.1 trunk as
 of revision [10723]. It hasn't caused real-world problems as far as I
 know, but I've entered it here as a bug so we don't lose track of 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] #10855: tutorial doesn't give sufficient warning about superuser account or there should be a default login

[Django]

#10855: tutorial doesn't give sufficient warning about superuser account or 
there
should be a default login
+---
  Reporter:  cwolf127   | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords:  superuser admin
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by gsong):

  * summary:  tutorial doesn't give sufficient waring about superuser
  account or there should be a default login =>
  tutorial doesn't give sufficient warning about
  superuser account or there should be a default
  login

-- 
Ticket URL: 
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] #10994: Flat page content with unicode causes fatal error but data is still commited

[Django]

#10994: Flat page content with unicode causes fatal error but data is still
commited
---+
  Reporter:  ati...@gmail.com  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.0
   
Resolution:  invalid   |  Keywords:  uniode mysql 
flatpages
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by gsong):

  * summary:  Flay page content with unicode causes fatal error but data is
  still commited => Flat page content with
  unicode causes fatal error but data is still
  commited

-- 
Ticket URL: 
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] #11039: Document that aggregation doesn't work with generic relations.

[Django]

#11039: Document that aggregation doesn't work with generic relations.
+---
  Reporter:  Alex   | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

[Django] #11049: Oracle fails to return IntegerField in test_get_table_description_types

[Django]

#11049: Oracle fails to return IntegerField in test_get_table_description_types
--+-
 Reporter:  mboersma  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  Oracle oracle |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The Oracle backend raises an AssertionError when executing
 test_get_table_description_types in the test suite:

 {{{
 C:\projects\django-1.0.x\tests>runtests.py --settings=testsettings.oracle
 introspection
 ...

 ==
 FAIL: test_get_table_description_types
 (regressiontests.introspection.tests.IntrospectionTests)
 --
 Traceback (most recent call last):
   File
 "C:\projects\django-1.0.x\tests\regressiontests\introspection\tests.py",
 line 28, in _inner
 return func(*args, **kwargs)
   File
 "C:\projects\django-1.0.x\tests\regressiontests\introspection\tests.py",
 line 80, in test_get_table_description_types
 ['IntegerField', 'CharField', 'CharField', 'CharField'])
 AssertionError: ['DecimalField', 'CharField', 'CharField', 'CharField'] !=
 ['IntegerField', 'CharField', 'CharField', 'CharField']
 }}}

 Oracle doesn't have a distinct data type for integers as opposed to
 floating point numbers; they all come across as cx_Oracle.NUMERIC.  Either
 we should use a different approach during introspection, or this test case
 should be changed so this isn't considered an error when run against
 Oracle.

 This happens in both the 1.0.x maintenance branch and the pre-1.1 trunk as
 of revision [10723]. It hasn't caused real-world problems as far as I
 know, but I've entered it here as a bug so we don't lose track of 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] #11039: Document that aggregation doesn't work with generic relations.

[Django]

#11039: Document that aggregation doesn't work with generic relations.
+---
  Reporter:  Alex   | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by psmith):

  * has_patch:  0 => 1

Comment:

 Here's a stab at the docs.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #11048: Oracle raises KeyError in IntrospectionTests.test_get_indexes

[Django]

#11048: Oracle raises KeyError in IntrospectionTests.test_get_indexes
--+-
 Reporter:  mboersma  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  Oracle oracle |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The Oracle backend raises a KeyError when executing test_get_indexes:

 {{{
 C:\projects\django-trunk\tests>runtests.py --settings=testsettings.oracle
 introspection
 ==
 ERROR: test_get_indexes
 (regressiontests.introspection.tests.IntrospectionTests)
 --
 Traceback (most recent call last):
   File "C:\projects\django-
 trunk\tests\regressiontests\introspection\tests.py", line 28, in _inner
 return func(*args, **kwargs)
   File "C:\projects\django-
 trunk\tests\regressiontests\introspection\tests.py", line 105, in
 test_get_indexes
 self.assertEqual(indexes['reporter_id'], {'unique': False,
 'primary_key': False})
 KeyError: 'reporter_id'
 }}}

 This happens in both the 1.0.x maintenance branch and the pre-1.1 trunk as
 of revision [10723].  It hasn't caused real-world problems as far as I
 know, but I've entered it here as a bug so we don't lose track of 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] #10855: tutorial doesn't give sufficient waring about superuser account or there should be a default login

[Django]

#10855: tutorial doesn't give sufficient waring about superuser account or there
should be a default login
+---
  Reporter:  cwolf127   | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords:  superuser admin
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * needs_docs:  1 => 0
  * has_patch:  0 => 1
  * version:  1.0 => SVN
  * 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] #11042: admin inlines of inherited models break on edit submit after changeset 10666

[Django]

#11042: admin inlines of inherited models break on edit submit after changeset
10666
---+
  Reporter:  jsmullyan | Owner: 
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by mir):

  * owner:  mir =>
  * has_patch:  0 => 1
  * needs_tests:  1 => 0

Comment:

 This is really a bug introduced in [10666] that broke using subclassed
 models in admin inlines. #11042

 The changeset introduced a function has_auto_field that checked for auto
 pk fields instead
 of checking whether it has been automatically created.

 I'm not so familiar with this area, can someone please review 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] r10723 - in django/trunk: django/core/files django/http tests/regressiontests/file_uploads

[noreply]

Author: jacob
Date: 2009-05-08 12:22:34 -0500 (Fri, 08 May 2009)
New Revision: 10723

Modified:
   django/trunk/django/core/files/base.py
   django/trunk/django/http/multipartparser.py
   django/trunk/tests/regressiontests/file_uploads/tests.py
Log:
Fixed #10687: fixed request parsing when upload_handlers is empty. Thanks, 
Armin Ronacher.

Modified: django/trunk/django/core/files/base.py
===
--- django/trunk/django/core/files/base.py  2009-05-08 16:49:49 UTC (rev 
10722)
+++ django/trunk/django/core/files/base.py  2009-05-08 17:22:34 UTC (rev 
10723)
@@ -1,5 +1,4 @@
 import os
-
 try:
 from cStringIO import StringIO
 except ImportError:

Modified: django/trunk/django/http/multipartparser.py
===
--- django/trunk/django/http/multipartparser.py 2009-05-08 16:49:49 UTC (rev 
10722)
+++ django/trunk/django/http/multipartparser.py 2009-05-08 17:22:34 UTC (rev 
10723)
@@ -84,7 +84,8 @@
 
 # For compatibility with low-level network APIs (with 32-bit integers),
 # the chunk size should be < 2^31, but still divisible by 4.
-self._chunk_size = min(2**31-4, *[x.chunk_size for x in 
upload_handlers if x.chunk_size])
+possible_sizes = [x.chunk_size for x in upload_handlers if 
x.chunk_size]
+self._chunk_size = min([2**31-4] + possible_sizes)
 
 self._meta = META
 self._encoding = encoding or settings.DEFAULT_CHARSET

Modified: django/trunk/tests/regressiontests/file_uploads/tests.py
===
--- django/trunk/tests/regressiontests/file_uploads/tests.py2009-05-08 
16:49:49 UTC (rev 10722)
+++ django/trunk/tests/regressiontests/file_uploads/tests.py2009-05-08 
17:22:34 UTC (rev 10723)
@@ -3,12 +3,14 @@
 import errno
 import shutil
 import unittest
+from StringIO import StringIO
 
 from django.core.files import temp as tempfile
 from django.core.files.uploadedfile import SimpleUploadedFile
 from django.test import TestCase, client
 from django.utils import simplejson
 from django.utils.hashcompat import sha_constructor
+from django.http.multipartparser import MultiPartParser
 
 from models import FileModel, temp_storage, UPLOAD_TO
 import uploadhandler
@@ -290,3 +292,13 @@
   "%s exists and is not a directory." % UPLOAD_TO)
 except:
 self.fail("IOError not raised")
+
+class MultiParserTests(unittest.TestCase):
+
+def test_empty_upload_handlers(self):
+# We're not actually parsing here; just checking if the parser properly
+# instantiates with empty upload handlers.
+parser = MultiPartParser({
+'CONTENT_TYPE': 'multipart/form-data; boundary=_foo',
+'CONTENT_LENGTH':   '1'
+}, StringIO('x'), [], 'utf-8')


--~--~-~--~~~---~--~~
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] #10846: deployment typo + updated link

[Django]

#10846: deployment typo + updated link
+---
  Reporter:  timo   | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords:  typo deployment
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * 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] #6850: contrib.auth.forms is inconsistent on form field labels and max_length

[Django]

#6850: contrib.auth.forms is inconsistent on form field labels and max_length
-+--
  Reporter:  Bela Hausmann   | Owner:  
nobody
Status:  closed  | Milestone:   
 
 Component:  Contrib apps|   Version:  
newforms-admin
Resolution:  invalid |  Keywords:   
 
 Stage:  Accepted| Has_patch:  
1 
Needs_docs:  0   |   Needs_tests:  
0 
Needs_better_patch:  0   |  
-+--
Changes (by thejaswi_puthraya):

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

Comment:

 Most of this seems to have already been fixed in the current trunk. I am
 closing this
 ticket.

-- 
Ticket URL: 
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] #10925: Django tutorial part 2: was_published_today example

[Django]

#10925: Django tutorial part 2: was_published_today example
+---
  Reporter:  rm | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  tutorial
 Stage:  Ready for checkin  | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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] #9751: project_directory calculated incorrectly when "settings" is a directory (breaks 'startapp')

[Django]

#9751: project_directory calculated incorrectly when "settings" is a directory
(breaks 'startapp')
+---
  Reporter:  lamby  | Owner:  gsong 
  
Status:  assigned   | Milestone:  1.1   
  
 Component:  django-admin.py|   Version:  1.0   
  
Resolution: |  Keywords:  
startapp,settings,module
 Stage:  Ready for checkin  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_tests:  1 => 0
  * 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] #10422: documentation of ticket #4140: manage.py with oracle database fails with ORA-06552 when a field name is a keyword

[Django]

#10422: documentation of ticket #4140: manage.py with oracle database fails with
ORA-06552 when a field name is a keyword
+---
  Reporter:  boyombo| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mboersma):

 * cc: mboersma (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] #10888: Inserting model with GeometryField as None crashes on Oracle

[Django]

#10888: Inserting model with GeometryField as None crashes on Oracle
---+
  Reporter:  jtiai | Owner:  jbronn 
Status:  closed| Milestone:  1.1
 Component:  GIS   |   Version:  SVN
Resolution:  fixed |  Keywords:  oracle gis null
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by mboersma):

 * cc: mboersma (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] #11033: cx_Oracle.UNICODE missing if cx_Oracle version 5.0.1 is compiled without Unicode support

[Django]

#11033: cx_Oracle.UNICODE missing if cx_Oracle version 5.0.1 is compiled without
Unicode support
---+
  Reporter:  JirkaV| Owner:  ikelly 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  oracle 
unicode cx_Oracle
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by mboersma):

 * cc: mboersma (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] #11017: Oracle LIKEC query doesn't use index

[Django]

#11017: Oracle LIKEC query doesn't use index
---+
  Reporter:  jtiai | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  oracle
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mboersma):

 * cc: mboersma (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] #10664: non-serializing fixtures

[Django]

#10664: non-serializing fixtures
-+--
  Reporter:  lsaffre | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Serialization   |   Version:  1.0 
Resolution:  |  Keywords:  fixtures
 Stage:  Design decision needed  | Has_patch:  0   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  django-admin.py => Serialization

-- 
Ticket URL: 
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] #11031: Docs change - django user needs more roles in Oracle database

[Django]

#11031: Docs change - django user needs more roles in Oracle database
+---
  Reporter:  JirkaV | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  oracle documentation
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  1  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by mboersma):

 * cc: mboersma, ikelly (added)
  * needs_docs:  0 => 1
  * stage:  Unreviewed => Accepted

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

Re: [Django] #6290: profanity filter

[Django]

#6290: profanity filter
-+--
  Reporter:  programmerq | Owner:  nobody   

Status:  reopened| Milestone:   

 Component:  Contrib apps|   Version:  SVN  

Resolution:  |  Keywords:  template filter 
profanity
 Stage:  Design decision needed  | Has_patch:  0

Needs_docs:  0   |   Needs_tests:  0

Needs_better_patch:  0   |  
-+--
Comment (by thejaswi_puthraya):

 I doubt if we should go ahead especially with the reluctance of the BDFLs
 (see #8794).

 Maintaining profanities like Alex mentioned would be very difficult. Just
 take into account the large number, then i18n variants and finally the
 number of tickets people might open to add new ones.

-- 
Ticket URL: 
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] r10722 - django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress

[noreply]

Author: mboersma
Date: 2009-05-08 11:49:49 -0500 (Fri, 08 May 2009)
New Revision: 10722

Modified:
   
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/models.py
   
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/tests.py
Log:
[1.0.X] Fixed test suite on Oracle that was broken by using keyword "date" as a 
field name. Refs #4140 and #10422.


Modified: 
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/models.py
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/models.py
  2009-05-08 16:20:28 UTC (rev 10721)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/models.py
  2009-05-08 16:49:49 UTC (rev 10722)
@@ -17,7 +17,7 @@
 
 class Publication(models.Model):
 title = models.CharField(max_length=30)
-date = models.DateField()
+date_published = models.DateField()
 
 def __unicode__(self):
 return self.title

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/tests.py
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/tests.py
   2009-05-08 16:20:28 UTC (rev 10721)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/model_forms_regress/tests.py
   2009-05-08 16:49:49 UTC (rev 10722)
@@ -71,13 +71,13 @@
 # Set up a callable initial value
 def formfield_for_dbfield(db_field, **kwargs):
 if db_field.name == 'publications':
-kwargs['initial'] = lambda: 
Publication.objects.all().order_by('date')[:2]
+kwargs['initial'] = lambda: 
Publication.objects.all().order_by('date_published')[:2]
 return db_field.formfield(**kwargs)
 
 # Set up some Publications to use as data
-Publication(title="First Book", date=date(2007,1,1)).save()
-Publication(title="Second Book", date=date(2008,1,1)).save()
-Publication(title="Third Book", date=date(2009,1,1)).save()
+Publication(title="First Book", date_published=date(2007,1,1)).save()
+Publication(title="Second Book", date_published=date(2008,1,1)).save()
+Publication(title="Third Book", date_published=date(2009,1,1)).save()
 
 # Create a ModelForm, instantiate it, and check that the output is as 
expected
 ModelForm = modelform_factory(Article, 
formfield_callback=formfield_for_dbfield)
@@ -88,5 +88,3 @@
 Second Book
 Third Book
   Hold down "Control", or "Command" on a Mac, to select more than 
one.""")
-
-


--~--~-~--~~~---~--~~
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] #2283: [patch] comment form templates don't validate as XHTML strict

[Django]

#2283: [patch] comment form templates don't validate as XHTML strict
--+-
  Reporter:  fonso| Owner:  adrian
Status:  reopened | Milestone:
 Component:  django.contrib.comments  |   Version:
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by thejaswi_puthraya):

 The admin and forms use XHTML and some tags in the comments (like IMG and
 Meta) were usign XHTML,
 so I thought why not convert everything to XHTML for uniformity.

-- 
Ticket URL: 
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] #11025: [patch] Ability to specify LOGIN_URL as full qualified absolute URL, ex: https://passport.example.com/passport?mode=login

[Django]

#11025: [patch] Ability to specify LOGIN_URL as full qualified absolute URL, ex:
https://passport.example.com/passport?mode=login
-+--
  Reporter:  arikon  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by arikon):

  * summary:  Ability to specify LOGIN_URL as full qualified absolute URL,
  ex:
  https://passport.example.com/passport?mode=login
  => [patch] Ability to specify LOGIN_URL as full
  qualified absolute URL, ex:
  https://passport.example.com/passport?mode=login

-- 
Ticket URL: 
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] #11046: Documentation on ifchanged should use new cycle syntax

[Django]

#11046: Documentation on ifchanged should use new cycle syntax
+---
  Reporter:  mitsuhiko  | Owner:  mitsuhiko
Status:  new| Milestone:  1.1  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

[Django] #11047: Clarification of contenttypes docs

[Django]

#11047: Clarification of contenttypes docs
+---
 Reporter:  psmith  |   Owner:  
nobody
   Status:  new |   Milestone:  
  
Component:  Documentation   | Version:  1.0 
  
 Keywords:  contenttypes genericrelation genericforeignkey  |   Stage:  
Unreviewed
Has_patch:  1   |  
+---
 I found the paragraph about using a GenericForeignKey in a GenericRelation
 to be somewhat confusing at first read, and the example line of code
 explicitly sets the content_type_field, even though the example of Comment
 uses a default value for content_type_field.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #2283: [patch] comment form templates don't validate as XHTML strict

[Django]

#2283: [patch] comment form templates don't validate as XHTML strict
--+-
  Reporter:  fonso| Owner:  adrian
Status:  reopened | Milestone:
 Component:  django.contrib.comments  |   Version:
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by thejaswi_puthraya):

  * component:  Contrib apps => django.contrib.comments

Comment:

 Wow, can't believe this bug existed in both versions and took so long to
 fix.

-- 
Ticket URL: 
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] #11046: Documentation on ifchanged should use new cycle syntax

[Django]

#11046: Documentation on ifchanged should use new cycle syntax
---+
 Reporter:  mitsuhiko  |   Owner:  mitsuhiko 
   Status:  new|   Milestone:  1.1   
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 The documentation on the ifchanged tag should use `{% cycle "foo" "bar"
 %}` instead of `{% cycle foo,bar %}` which is deprecated.

-- 
Ticket URL: 
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] r10721 - django/trunk/django/conf/locale/hr/LC_MESSAGES

[noreply]

Author: aljosa
Date: 2009-05-08 11:20:28 -0500 (Fri, 08 May 2009)
New Revision: 10721

Modified:
   django/trunk/django/conf/locale/hr/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/hr/LC_MESSAGES/django.po
Log:


Modified: django/trunk/django/conf/locale/hr/LC_MESSAGES/django.mo
===
--- django/trunk/django/conf/locale/hr/LC_MESSAGES/django.mo2009-05-08 
16:12:51 UTC (rev 10720)
+++ django/trunk/django/conf/locale/hr/LC_MESSAGES/django.mo2009-05-08 
16:20:28 UTC (rev 10721)
@@ -1,209 +1,201 @@
-Þ  •
--~--~-~--~~~---~--~~
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] #11043: InlineForeignKeyField should respect to_field

[Django]

#11043: InlineForeignKeyField should respect to_field
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Forms |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * component:  Database layer (models, ORM) => Forms
  * stage:  Unreviewed => Accepted

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

Re: [Django] #11043: InlineForeignKeyField should respect to_field

[Django]

#11043: InlineForeignKeyField should respect to_field
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by thejaswi_puthraya):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Database layer (models, ORM)
  * 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] #11027: Storage backends should know about the max_length attribute of the FileFields

[Django]

#11027: Storage backends should know about the max_length attribute of the
FileFields
---+
  Reporter:  apollo13  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by thejaswi_puthraya):

  * needs_better_patch:  => 0
  * component:  Uncategorized => File uploads/storage
  * 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] #11013: Named imports in urls

[Django]

#11013: Named imports in urls
-+--
  Reporter:  gruszczy| Owner:  nobody
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  1.1-beta-1
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => Core framework

-- 
Ticket URL: 
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] #9977: CSRFMiddleware needs template tag

[Django]

#9977: CSRFMiddleware needs template tag
-+--
  Reporter:  bthomas | Owner:  lukeplant
Status:  assigned| Milestone:   
 Component:  HTTP handling   |   Version:  SVN  
Resolution:  |  Keywords:  csrf 
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  1   |   Needs_tests:  0
Needs_better_patch:  1   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => HTTP handling

-- 
Ticket URL: 
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] r10720 - in django/branches/releases/1.0.X: django/contrib/admin tests/regressiontests/admin_views

[noreply]

Author: russellm
Date: 2009-05-08 11:12:51 -0500 (Fri, 08 May 2009)
New Revision: 10720

Modified:
   django/branches/releases/1.0.X/django/contrib/admin/options.py
   django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py
Log:
[1.0.X] Fixed #10899 -- Ensured that log messages for deletions in the admin 
contain useful descriptions. Thanks to Jeremy Dunck for the patch.

Merge of r10686 from trunk.

Modified: django/branches/releases/1.0.X/django/contrib/admin/options.py
===
--- django/branches/releases/1.0.X/django/contrib/admin/options.py  
2009-05-08 16:08:55 UTC (rev 10719)
+++ django/branches/releases/1.0.X/django/contrib/admin/options.py  
2009-05-08 16:12:51 UTC (rev 10720)
@@ -46,7 +46,7 @@
 
 If kwargs are given, they're passed to the form Field's constructor.
 """
-
+
 # If the field specifies choices, we don't need to look for special
 # admin widgets - we just need to use a select widget of some kind.
 if db_field.choices:
@@ -79,17 +79,17 @@
 if isinstance(db_field, models.TimeField):
 kwargs['widget'] = widgets.AdminTimeWidget
 return db_field.formfield(**kwargs)
-
+
 # For TextFields, add a custom CSS class.
 if isinstance(db_field, models.TextField):
 kwargs['widget'] = widgets.AdminTextareaWidget
 return db_field.formfield(**kwargs)
-
+
 # For URLFields, add a custom CSS class.
 if isinstance(db_field, models.URLField):
 kwargs['widget'] = widgets.AdminURLFieldWidget
 return db_field.formfield(**kwargs)
-
+
 # For IntegerFields, add a custom CSS class.
 if isinstance(db_field, models.IntegerField):
 kwargs['widget'] = widgets.AdminIntegerFieldWidget
@@ -104,7 +104,7 @@
 if isinstance(db_field, models.CharField):
 kwargs['widget'] = widgets.AdminTextInputWidget
 return db_field.formfield(**kwargs)
-
+
 # For FileFields and ImageFields add a link to the current file.
 if isinstance(db_field, models.ImageField) or isinstance(db_field, 
models.FileField):
 kwargs['widget'] = widgets.AdminFileWidget
@@ -281,56 +281,56 @@
 def get_formsets(self, request, obj=None):
 for inline in self.inline_instances:
 yield inline.get_formset(request, obj)
-
+
 def log_addition(self, request, object):
 """
-Log that an object has been successfully added. 
-
+Log that an object has been successfully added.
+
 The default implementation creates an admin LogEntry object.
 """
 from django.contrib.admin.models import LogEntry, ADDITION
 LogEntry.objects.log_action(
-user_id = request.user.pk, 
+user_id = request.user.pk,
 content_type_id = ContentType.objects.get_for_model(object).pk,
 object_id   = object.pk,
-object_repr = force_unicode(object), 
+object_repr = force_unicode(object),
 action_flag = ADDITION
 )
-
+
 def log_change(self, request, object, message):
 """
-Log that an object has been successfully changed. 
-
+Log that an object has been successfully changed.
+
 The default implementation creates an admin LogEntry object.
 """
 from django.contrib.admin.models import LogEntry, CHANGE
 LogEntry.objects.log_action(
-user_id = request.user.pk, 
-content_type_id = ContentType.objects.get_for_model(object).pk, 
-object_id   = object.pk, 
-object_repr = force_unicode(object), 
-action_flag = CHANGE, 
+user_id = request.user.pk,
+content_type_id = ContentType.objects.get_for_model(object).pk,
+object_id   = object.pk,
+object_repr = force_unicode(object),
+action_flag = CHANGE,
 change_message  = message
 )
-
+
 def log_deletion(self, request, object, object_repr):
 """
 Log that an object has been successfully deleted. Note that since the
 object is deleted, it might no longer be safe to call *any* methods
 on the object, hence this method getting object_repr.
-
+
 The default implementation creates an admin LogEntry object.
 """
 from django.contrib.admin.models import LogEntry, DELETION
 LogEntry.objects.log_action(
-user_id = request.user.id, 
-content_type_id = 
ContentType.objects.get_for_model(self.model).pk, 
-object_id   = object.pk, 
+user_id = request.user.id,
+content_type_id = 

Re: [Django] #9333: Add Django-localeurl to the translation/i18n documentation

[Django]

#9333: Add Django-localeurl to the translation/i18n documentation
---+
  Reporter:  vizualbod | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => Internationalization

-- 
Ticket URL: 
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] #9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware turns on Vary: Cookie

[Django]

#9249: Google Analytics' Cookies break CacheMiddleware when SessionMiddleware
turns on Vary: Cookie
+---
  Reporter:  pixelcort  | Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => HTTP handling

-- 
Ticket URL: 
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] #8952: Refactor a Django "site" to be just another view function

[Django]

#8952: Refactor a Django "site" to be just another view function
-+--
  Reporter:  simon   | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Contrib apps|   Version:  1.0  
Resolution:  |  Keywords:  djangocon
 Stage:  Design decision needed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => Contrib apps

-- 
Ticket URL: 
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] #9751: project_directory calculated incorrectly when "settings" is a directory (breaks 'startapp')

[Django]

#9751: project_directory calculated incorrectly when "settings" is a directory
(breaks 'startapp')
--+-
  Reporter:  lamby| Owner:  gsong   
Status:  assigned | Milestone:  1.1 
 Component:  django-admin.py  |   Version:  1.0 
Resolution:   |  Keywords:  startapp,settings,module
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  1   
Needs_better_patch:  0|  
--+-
Comment (by ericholscher):

 All tests pass, and the regression test (first at the top of that patch)
 fails on current trunk and passes with the patch.

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

Re: [Django] #8946: Denormalisation built in to the ORM

[Django]

#8946: Denormalisation built in to the ORM
---+
  Reporter:  simon | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.0  
Resolution:|  Keywords:  djangocon
 Stage:  Someday/Maybe | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => Database layer (models, ORM)

-- 
Ticket URL: 
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] #8936: Integrate databrowse functionality in to the admin

[Django]

#8936: Integrate databrowse functionality in to the admin
+---
  Reporter:  simon  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Contrib apps   |   Version:  1.0
Resolution: |  Keywords:  django pony
 Stage:  Someday/Maybe  | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by thejaswi_puthraya):

  * keywords:  => django pony
  * component:  Uncategorized => Contrib apps

-- 
Ticket URL: 
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] #8928: Make a WSGI compatibility layer for Django middleware

[Django]

#8928: Make a WSGI compatibility layer for Django middleware
+---
  Reporter:  simon  | Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => HTTP handling

-- 
Ticket URL: 
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] #8034: Gzip Middleware And Images

[Django]

#8034: Gzip Middleware And Images
-+--
  Reporter:  magneto | Owner:  nobody 
Status:  new | Milestone: 
 Component:  HTTP handling   |   Version:  SVN
Resolution:  |  Keywords:  gzip middleware
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => HTTP handling

-- 
Ticket URL: 
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] r10719 - in django/branches/releases/1.0.X: django/contrib/admin/views tests/regressiontests/admin_views tests/regressiontests/admin_views/fixtures

[noreply]

Author: russellm
Date: 2009-05-08 11:08:55 -0500 (Fri, 08 May 2009)
New Revision: 10719

Added:
   
django/branches/releases/1.0.X/tests/regressiontests/admin_views/fixtures/multiple-child-classes.json
Modified:
   django/branches/releases/1.0.X/django/contrib/admin/views/main.py
   django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py
   django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py
Log:
[1.0.X] Fixed #10516 -- Corrected admin search when the search_fields 
definition contains multiple fields on the same base model. Thanks to Zain Memon

Merge of r10684 from trunk.

Modified: django/branches/releases/1.0.X/django/contrib/admin/views/main.py
===
--- django/branches/releases/1.0.X/django/contrib/admin/views/main.py   
2009-05-08 16:04:59 UTC (rev 10718)
+++ django/branches/releases/1.0.X/django/contrib/admin/views/main.py   
2009-05-08 16:08:55 UTC (rev 10719)
@@ -190,7 +190,7 @@
 # Naked except! Because we don't have any other way of validating 
"params".
 # They might be invalid if the keyword arguments are incorrect, or if 
the
 # values are not in the correct type, so we might get FieldError, 
ValueError,
-# ValicationError, or ? from a custom field that raises yet something 
else 
+# ValicationError, or ? from a custom field that raises yet something 
else
 # when handed impossible data.
 except:
 raise IncorrectLookupParameters
@@ -227,11 +227,8 @@
 
 if self.search_fields and self.query:
 for bit in self.query.split():
-or_queries = [models.Q(**{construct_search(field_name): bit}) 
for field_name in self.search_fields]
-other_qs = QuerySet(self.model)
-other_qs.dup_select_related(qs)
-other_qs = other_qs.filter(reduce(operator.or_, or_queries))
-qs = qs & other_qs
+or_queries = [models.Q(**{construct_search(str(field_name)): 
bit}) for field_name in self.search_fields]
+qs = qs.filter(reduce(operator.or_, or_queries))
 for field_name in self.search_fields:
 if '__' in field_name:
 qs = qs.distinct()

Added: 
django/branches/releases/1.0.X/tests/regressiontests/admin_views/fixtures/multiple-child-classes.json
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/admin_views/fixtures/multiple-child-classes.json
   (rev 0)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/admin_views/fixtures/multiple-child-classes.json
   2009-05-08 16:08:55 UTC (rev 10719)
@@ -0,0 +1,107 @@
+[
+{
+"pk": 1,
+ "model": "admin_views.title",
+ "fields":
+{
+}
+},
+
+{
+"pk": 2,
+ "model": "admin_views.title",
+ "fields":
+{
+}
+},
+
+{
+"pk": 3,
+ "model": "admin_views.title",
+ "fields":
+{
+}
+},
+
+{
+"pk": 4,
+ "model": "admin_views.title",
+ "fields":
+{
+}
+},
+
+{
+"pk": 1,
+ "model": "admin_views.titletranslation",
+ "fields":
+{
+"text": "Bar",
+ "title": 1
+}
+},
+
+{
+"pk": 2,
+ "model": "admin_views.titletranslation",
+ "fields":
+{
+"text": "Foo",
+ "title": 2
+}
+},
+
+{
+"pk": 3,
+ "model": "admin_views.titletranslation",
+ "fields":
+{
+"text": "Few",
+ "title": 3
+}
+},
+
+{
+"pk": 4,
+ "model": "admin_views.titletranslation",
+ "fields":
+{
+"text": "Bas",
+ "title": 4
+}
+},
+
+{
+"pk": 1,
+ "model": "admin_views.recommender",
+ "fields":
+{
+}
+},
+
+{
+"pk": 4,
+ "model": "admin_views.recommender",
+ "fields":
+{
+}
+},
+
+{
+"pk": 2,
+ "model": "admin_views.recommendation",
+ "fields":
+{
+"recommender": 1
+}
+},
+
+{
+"pk": 3,
+ "model": "admin_views.recommendation",
+ "fields":
+{
+"recommender": 4
+}
+}
+]
\ No newline at end of file

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py  
2009-05-08 16:04:59 UTC (rev 10718)
+++ django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py  
2009-05-08 16:08:55 UTC (rev 10719)
@@ -238,6 +238,24 @@
 class 

Re: [Django] #6379: Don't hide errors when resolving URL views

[Django]

#6379: Don't hide errors when resolving URL views
-+--
  Reporter:  Bastian Kleineidam   | Owner:  
nobody
Status:  new | Milestone:   
 
 Component:  Core framework  |   Version:  
SVN   
Resolution:  |  Keywords:   
 
 Stage:  Accepted| Has_patch:  
1 
Needs_docs:  0   |   Needs_tests:  
0 
Needs_better_patch:  1   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => Core framework

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

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

[Django]

#5925: Unable to use urlresolvers (url,reverse ) feature in redirect argument of
decorator user_passes_test
-+--
  Reporter:  anonymous   | Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  Core framework  |   Version:  SVN  
  
Resolution:  |  Keywords:  
urlresolver,reverse,decorator,url,permalink
 Stage:  Accepted| Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => Core framework

-- 
Ticket URL: 
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] #5797: decorator_from_middleware can cause middleware hooks to run out of correct order.

[Django]

#5797: decorator_from_middleware can cause middleware hooks to run out of 
correct
order.
+---
  Reporter:  jdunck | Owner:  nobody
  
Status:  new| Milestone:
  
 Component:  HTTP handling  |   Version:  SVN   
  
Resolution: |  Keywords:  cache middleware 
decorator gzip conditional http
 Stage:  Accepted   | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => HTTP handling

-- 
Ticket URL: 
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] #5686: separate functions in CommonMiddleware.process_response

[Django]

#5686: separate functions in CommonMiddleware.process_response
+---
  Reporter:  keturn | Owner:  anonymous
Status:  assigned   | Milestone:   
 Component:  HTTP handling  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  1
Needs_better_patch:  0  |  
+---
Changes (by thejaswi_puthraya):

  * component:  Uncategorized => HTTP handling

-- 
Ticket URL: 
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] #11045: Updated Dutch translation

[Django]

#11045: Updated Dutch translation
--+-
 Reporter:  joeri |   Owner:  nobody
   Status:  new   |   Milestone:  1.1   
Component:  Translations  | Version:  SVN   
 Keywords:  dutch nl translation  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Localization patch for the Dutch language against revision 10717.

-- 
Ticket URL: 
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] r10718 - in django/branches/releases/1.0.X: django/forms docs/topics/forms tests/modeltests/model_formsets

[noreply]

Author: russellm
Date: 2009-05-08 11:04:59 -0500 (Fri, 08 May 2009)
New Revision: 10718

Modified:
   django/branches/releases/1.0.X/django/forms/models.py
   django/branches/releases/1.0.X/docs/topics/forms/modelforms.txt
   django/branches/releases/1.0.X/tests/modeltests/model_formsets/models.py
Log:
[1.0.X] Fixed #9493 -- Corrected error handling of formsets that violate unique 
constraints across the component forms. Thanks to Alex Gaynor for the patch.

Merge of r10682 from trunk.

Modified: django/branches/releases/1.0.X/django/forms/models.py
===
--- django/branches/releases/1.0.X/django/forms/models.py   2009-05-08 
15:08:09 UTC (rev 10717)
+++ django/branches/releases/1.0.X/django/forms/models.py   2009-05-08 
16:04:59 UTC (rev 10718)
@@ -6,10 +6,10 @@
 from django.utils.encoding import smart_unicode, force_unicode
 from django.utils.datastructures import SortedDict
 from django.utils.text import get_text_list, capfirst
-from django.utils.translation import ugettext_lazy as _
+from django.utils.translation import ugettext_lazy as _, ugettext
 
 from util import ValidationError, ErrorList
-from forms import BaseForm, get_declared_fields
+from forms import BaseForm, get_declared_fields, NON_FIELD_ERRORS
 from fields import Field, ChoiceField, IntegerField, EMPTY_VALUES
 from widgets import Select, SelectMultiple, HiddenInput, MultipleHiddenInput
 from widgets import media_property
@@ -225,6 +225,26 @@
 return self.cleaned_data
 
 def validate_unique(self):
+unique_checks, date_checks = self._get_unique_checks()
+form_errors = []
+bad_fields = set()
+
+field_errors, global_errors = 
self._perform_unique_checks(unique_checks)
+bad_fields.union(field_errors)
+form_errors.extend(global_errors)
+
+field_errors, global_errors = self._perform_date_checks(date_checks)
+bad_fields.union(field_errors)
+form_errors.extend(global_errors)
+
+for field_name in bad_fields:
+del self.cleaned_data[field_name]
+if form_errors:
+# Raise the unique together errors since they are considered
+# form-wide.
+raise ValidationError(form_errors)
+
+def _get_unique_checks(self):
 from django.db.models.fields import FieldDoesNotExist, Field as 
ModelField
 
 # Gather a list of checks to perform. We only perform unique checks
@@ -265,25 +285,9 @@
 date_checks.append(('year', name, f.unique_for_year))
 if f.unique_for_month and 
self.cleaned_data.get(f.unique_for_month) is not None:
 date_checks.append(('month', name, f.unique_for_month))
+return unique_checks, date_checks
 
-form_errors = []
-bad_fields = set()
 
-field_errors, global_errors = 
self._perform_unique_checks(unique_checks)
-bad_fields.union(field_errors)
-form_errors.extend(global_errors)
-
-field_errors, global_errors = self._perform_date_checks(date_checks)
-bad_fields.union(field_errors)
-form_errors.extend(global_errors)
-
-for field_name in bad_fields:
-del self.cleaned_data[field_name]
-if form_errors:
-# Raise the unique together errors since they are considered
-# form-wide.
-raise ValidationError(form_errors)
-
 def _perform_unique_checks(self, unique_checks):
 bad_fields = set()
 form_errors = []
@@ -497,6 +501,96 @@
 self.save_m2m = save_m2m
 return self.save_existing_objects(commit) + 
self.save_new_objects(commit)
 
+def clean(self):
+self.validate_unique()
+
+def validate_unique(self):
+# Iterate over the forms so that we can find one with potentially valid
+# data from which to extract the error checks
+for form in self.forms:
+if hasattr(form, 'cleaned_data'):
+break
+else:
+return
+unique_checks, date_checks = form._get_unique_checks()
+errors = []
+# Do each of the unique checks (unique and unique_together)
+for unique_check in unique_checks:
+seen_data = set()
+for form in self.forms:
+# if the form doesn't have cleaned_data then we ignore it,
+# it's already invalid
+if not hasattr(form, "cleaned_data"):
+continue
+# get each of the fields for which we have data on this form
+if [f for f in unique_check if f in form.cleaned_data and 
form.cleaned_data[f] is not None]:
+# get the data itself
+row_data = tuple([form.cleaned_data[field] for field in 
unique_check])
+# if we've aready seen it then we have a uniqueness failure
+if row_data in seen_data:
+# 

Re: [Django] #10625: Ewkt regexp incorrectly escaped

[Django]

#10625: Ewkt regexp incorrectly escaped
-+--
  Reporter:  timlinux| Owner:  springmeyer
Status:  closed  | Milestone:  1.1
 Component:  GIS |   Version:  SVN
Resolution:  worksforme  |  Keywords:  regexp ewkt
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Comment:

 Paul tried half a dozen browsers and we have no new information from the
 reported, marking as worksforme.

-- 
Ticket URL: 
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] #10625: Ewkt regexp incorrectly escaped

[Django]

#10625: Ewkt regexp incorrectly escaped
-+--
  Reporter:  timlinux| Owner:  springmeyer
Status:  new | Milestone:  1.1
 Component:  GIS |   Version:  SVN
Resolution:  |  Keywords:  regexp ewkt
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by psmith):

 I wasn't able to reproduce this. I tried:

  * Linux:
* FF 3.0.9
* Opera 9.6
  * Win XP:
* FF 3.0.10
* Opera 9.64
* IE 6.0.x

 Suggest this be punted to 1.2 since we don't have a user-agent yet of the
 reported 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] #10841: Better 500 template for AJAX calls

[Django]

#10841: Better 500 template for AJAX calls
--+-
  Reporter:  Riz   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Core framework   |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by Riz):

 Making it JSON is a nice idea ( maybe with combination of checking
 "accept" headers ) but afaik when you have 500 error it usually means that
 something really wrong happend and it's outside the frontend\javascript
 app logic (syntax error for example, or integrity error), not to note that
 you need debug 500 page only during development time and adding special
 logic just for debug time looks like an overkill. So my main point was to
 make it easy to read by developer, as ( usually ) special logic at
 javascript side for 500 error page will not exist.

-- 
Ticket URL: 
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] #10841: Better 500 template for AJAX calls

[Django]

#10841: Better 500 template for AJAX calls
--+-
  Reporter:  Riz   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Core framework   |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by alexkoshelev):

 * cc: alexkoshelev (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] #10032: ORM switches incorrectly to OUTER JOIN in certain cases with isnull=True

[Django]

#10032: ORM switches incorrectly to OUTER JOIN in certain cases with isnull=True
---+
  Reporter:  gabor | Owner:  nobody
Status:  closed| Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 As Malcolm said, this behavior is by intent. If you've got an issue with
 that intent please take it up on django-dev, but please don't reopen
 tickets closed by a committer.

-- 
Ticket URL: 
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] #9404: Proxy file-like methods and attributes in UploadedFile objects

[Django]

#9404: Proxy file-like methods and attributes in UploadedFile objects
---+
  Reporter:  magneto   | Owner:  mitsuhiko
Status:  closed| Milestone:  1.1  
 Component:  File uploads/storage  |   Version:  SVN  
Resolution:  fixed |  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Fixed in [10717].

-- 
Ticket URL: 
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] #10249: Cannot create a consistent method resolution order (MRO) for bases FieldFile, File

[Django]

#10249: Cannot create a consistent method resolution order (MRO) for bases
FieldFile, File
---+
  Reporter:  kmtracey  | Owner:  mitsuhiko
Status:  closed| Milestone:  1.1  
 Component:  File uploads/storage  |   Version:  1.0  
Resolution:  fixed |  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Fixed in [10717].

-- 
Ticket URL: 
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] #10300: Custom File Storage Backend broken by recent SVN commit.

[Django]

#10300: Custom File Storage Backend broken by recent SVN commit.
---+
  Reporter:  erikcw| Owner:  mitsuhiko  
   
Status:  closed| Milestone:  1.1
   
 Component:  File uploads/storage  |   Version:  SVN
   
Resolution:  fixed |  Keywords:  file upload 
storage s3
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Fixed in [10717].

-- 
Ticket URL: 
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] #7712: UploadedFile missing readline method

[Django]

#7712: UploadedFile missing readline method
---+
  Reporter:  artagnon  | Owner:  nobody 
Status:  closed| Milestone: 
 Component:  File uploads/storage  |   Version:  SVN
Resolution:  fixed |  Keywords:  upload uploadedfile
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Fixed in [10717].

-- 
Ticket URL: 
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] r10717 - in django/trunk: django/core/files django/db/models/fields tests/modeltests/files tests/regressiontests/file_storage

[noreply]

Author: jacob
Date: 2009-05-08 10:08:09 -0500 (Fri, 08 May 2009)
New Revision: 10717

Added:
   django/trunk/django/core/files/utils.py
Modified:
   django/trunk/django/core/files/base.py
   django/trunk/django/core/files/temp.py
   django/trunk/django/core/files/uploadedfile.py
   django/trunk/django/db/models/fields/files.py
   django/trunk/tests/modeltests/files/models.py
   django/trunk/tests/regressiontests/file_storage/models.py
Log:
Fixed #7712, #9404, #10249, #10300: a light refactor and cleanup of file 
storage and the `File` object. Thanks to Armin Ronacher and Alex Gaynor.

Modified: django/trunk/django/core/files/base.py
===
--- django/trunk/django/core/files/base.py  2009-05-08 13:39:37 UTC (rev 
10716)
+++ django/trunk/django/core/files/base.py  2009-05-08 15:08:09 UTC (rev 
10717)
@@ -1,20 +1,23 @@
 import os
 
-from django.utils.encoding import smart_str, smart_unicode
-
 try:
 from cStringIO import StringIO
 except ImportError:
 from StringIO import StringIO
 
-class File(object):
+from django.utils.encoding import smart_str, smart_unicode
+from django.core.files.utils import FileProxyMixin
+
+class File(FileProxyMixin):
 DEFAULT_CHUNK_SIZE = 64 * 2**10
 
-def __init__(self, file):
+def __init__(self, file, name=None):
 self.file = file
-self._name = file.name
-self._mode = file.mode
-self._closed = False
+if name is None:
+name = getattr(file, 'name', None)
+self.name = name
+self.mode = getattr(file, 'mode', None)
+self.closed = False
 
 def __str__(self):
 return smart_str(self.name or '')
@@ -26,25 +29,11 @@
 return "<%s: %s>" % (self.__class__.__name__, self or "None")
 
 def __nonzero__(self):
-return not not self.name
+return bool(self.name)
 
 def __len__(self):
 return self.size
 
-def _get_name(self):
-if not hasattr(self, '_name'):
-raise ValueError("This operation requires the file to have a 
name.")
-return self._name
-name = property(_get_name)
-
-def _get_mode(self):
-return self._mode
-mode = property(_get_mode)
-
-def _get_closed(self):
-return self._closed
-closed = property(_get_closed)
-
 def _get_size(self):
 if not hasattr(self, '_size'):
 if hasattr(self.file, 'size'):
@@ -66,7 +55,7 @@
 ``UploadedFile.DEFAULT_CHUNK_SIZE``).
 """
 if not chunk_size:
-chunk_size = self.__class__.DEFAULT_CHUNK_SIZE
+chunk_size = self.DEFAULT_CHUNK_SIZE
 
 if hasattr(self, 'seek'):
 self.seek(0)
@@ -89,12 +78,6 @@
 chunk_size = self.DEFAULT_CHUNK_SIZE
 return self.size > chunk_size
 
-def xreadlines(self):
-return iter(self)
-
-def readlines(self):
-return list(self.xreadlines())
-
 def __iter__(self):
 # Iterate over this file-like object by newlines
 buffer_ = None
@@ -121,43 +104,22 @@
 self.seek(0)
 elif os.path.exists(self.file.name):
 self.file = open(self.file.name, mode or self.file.mode)
+self.closed = False
 else:
 raise ValueError("The file cannot be reopened.")
 
-def seek(self, position):
-self.file.seek(position)
-
-def tell(self):
-return self.file.tell()
-
-def read(self, num_bytes=None):
-if num_bytes is None:
-return self.file.read()
-return self.file.read(num_bytes)
-
-def write(self, content):
-if not self.mode.startswith('w'):
-raise IOError("File was not opened with write access.")
-self.file.write(content)
-
-def flush(self):
-if not self.mode.startswith('w'):
-raise IOError("File was not opened with write access.")
-self.file.flush()
-
 def close(self):
 self.file.close()
-self._closed = True
+self.closed = True
 
 class ContentFile(File):
 """
 A File-like object that takes just raw content, rather than an actual file.
 """
 def __init__(self, content):
-self.file = StringIO(content or '')
-self.size = len(content or '')
-self.file.seek(0)
-self._closed = False
+content = content or ''
+super(ContentFile, self).__init__(StringIO(content))
+self.size = len(content)
 
 def __str__(self):
 return 'Raw content'
@@ -166,6 +128,6 @@
 return True
 
 def open(self, mode=None):
-if self._closed:
-self._closed = False
+if self.closed:
+self.closed = False
 self.seek(0)

Modified: django/trunk/django/core/files/temp.py
===
--- django/trunk/django/core/files/temp.py  2009-05-08 13:39:37 UTC (rev 
10716)
+++ 

Re: [Django] #10841: Better 500 template for AJAX calls

[Django]

#10841: Better 500 template for AJAX calls
--+-
  Reporter:  Riz   | Owner:  nobody
Status:  new  | Milestone:
 Component:  Core framework   |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by jacob):

 Why not make the AJAX 500 template be valid JSON? Then it'd be easy for
 clients to programatically figure out what went wrong.

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

Re: [Django] #11019: Admin inlines queryset

[Django]

#11019: Admin inlines queryset
---+
  Reporter:  pcicman   | Owner: 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  admin inlines 
queryset BaseInlineFormSet
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 It is ''essentially'' a duplicate, not directly. The point of #10761 is
 that all admin querysets (including for inlines) should get an extensible,
 consistent and thought out overhaul.

-- 
Ticket URL: 
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] #10032: ORM switches incorrectly to OUTER JOIN in certain cases with isnull=True

[Django]

#10032: ORM switches incorrectly to OUTER JOIN in certain cases with isnull=True
---+
  Reporter:  gabor | Owner:  nobody
Status:  reopened  | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by gabor):

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

Comment:

 i'm fine with any way, as long as it is consistent.
 but:

 when i do this:

 {{{
 >>> list(Group.objects.filter(person__stamp__isnull=True))
 []
 }}}

 i get an OUTER JOIN

 but when i do this:

 {{{
 >>> list(Group.objects.filter(person__stamp='2008-12-12'))
 []
 }}}

 i get an INNER JOIN.

 i think it's incorrect that django switches to a different join_type
 just because i used an {{{ isnull=True }}}. please note,
 that the "stamp" field is not a foreignkey, it's just a normal field.
 it has no active role in this JOIN.

-- 
Ticket URL: 
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] #11019: Admin inlines queryset

[Django]

#11019: Admin inlines queryset
---+
  Reporter:  pcicman   | Owner: 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  admin inlines 
queryset BaseInlineFormSet
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by mrts):

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

Comment:

 (Didn't intend to assign this to myself).

-- 
Ticket URL: 
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] #10243: to_field option problems in admin site

[Django]

#10243: to_field option problems in admin site
---+
  Reporter:  tsawyer   | Owner:  mtredinnick
Status:  assigned  | Milestone:  1.1
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords:  to_field   
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by apollo13):

 * cc: apollo13 (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] #11042: admin inlines of inherited models break on edit submit after changeset 10666

[Django]

#11042: admin inlines of inherited models break on edit submit after changeset
10666
---+
  Reporter:  jsmullyan | Owner:  mir
Status:  new   | Milestone:  1.1
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by mir):

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

Comment:

 verified that the bug is real

-- 
Ticket URL: 
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] #11044: FormWizard extra_context attribute is class-wide

[Django]

#11044: FormWizard extra_context attribute is class-wide
--+-
 Reporter:  taylanpince   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.formtools  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 FormWizard's extra_context attribute is declared within the class, rather
 than the __init__ method, which means that it persists across the class,
 causing data within the extra_context to appear in all requests. Patch
 attached to move the declaration inside __init__.

-- 
Ticket URL: 
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] #10940: Omission in tutorial, part 4: generic views

[Django]

#10940: Omission in tutorial, part 4: generic views
+---
  Reporter:  zpearce| Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  SVN   
   
Resolution:  invalid|  Keywords:  tutorial, generic view, 
object_id
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by timo):

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

Comment:

 This is not necessary since {{{vote}}} is not a generic view.  Notice that
 the URLconf keeps the poll_id variable:

 {{{(r'^(?P\d+)/vote/$', 'mysite.polls.views.vote')}}}

-- 
Ticket URL: 
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] #9850: Outdated documentation - (date format strings)

[Django]

#9850: Outdated documentation - (date format strings)
-+--
  Reporter:  cezz| Owner:  timo 
 
Status:  closed  | Milestone:   
 
 Component:  Documentation   |   Version:  SVN  
 
Resolution:  fixed   |  Keywords:  now format 
strings
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by timo):

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

Comment:

 fixed: (In [10716]) Fixed #10825: fixed the 'U' format code to dateformat
 (and the date/now filter/tag).

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

Re: [Django] #10794: admin JS error 'document.getElementById("") is null' on adding new user

[Django]

#10794: admin JS error 'document.getElementById("") is null' on adding new user
---+
  Reporter:  carljm| Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by carljm):

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

Comment:

 This is a duplicate of #10651.

-- 
Ticket URL: 
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] #10829: QuerySet.delete() attempts to delete unmanaged models.

[Django]

#10829: QuerySet.delete() attempts to delete unmanaged models.
---+
  Reporter:  justinlilly   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:|  Keywords:  unmanaged 
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by philroche):

 This is a show stopper for us so I have a small patch

 line 1002 django\db\models\query.py
 {{{
 perform_delete = True

 if cls._meta.managed == False:
 check_view = "select count(TABLE_NAME) from INFORMATION_SCHEMA.VIEWS
 WHERE TABLE_NAME = '%s';" % cls._meta.db_table
 cursor = connection.cursor()
 cursor.execute(check_view, [])
 if not cursor.rowcount == 0:
 perform_delete = False

 if perform_delete:
.. the rest of the deletion of code
 }}}

 It's ugly as hell I know but a start.

-- 
Ticket URL: 
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] #10795: Add Link to modelformset_factory

[Django]

#10795: Add Link to modelformset_factory
+---
  Reporter:  csshef | Owner:  Uninen 
Status:  new| Milestone:  1.1
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords:  forms, formsets
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by Uninen):

  * keywords:  => forms, formsets
  * 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
-~--~~~~--~~--~--~---

[Django] #11043: InlineForeignKeyField should respect to_field

[Django]

#11043: InlineForeignKeyField should respect to_field
---+
 Reporter:  apollo13   |   Owner:  nobody
   Status:  new|   Milestone:  1.1   
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Hi, while looking at #10243 I found out that InlineForeignKeyField isn't
 respecting to_field of the ForeignKey. Attached is a patch, which doesn't
 work until #10243 is fixed, but the bug in the forms is fixed now…

-- 
Ticket URL: 
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] r10716 - in django/trunk: django/utils docs/ref/templates tests/regressiontests/dateformat tests/regressiontests/utils

[noreply]

Author: jacob
Date: 2009-05-08 08:39:37 -0500 (Fri, 08 May 2009)
New Revision: 10716

Added:
   django/trunk/tests/regressiontests/utils/dateformat.py
Modified:
   django/trunk/django/utils/dateformat.py
   django/trunk/docs/ref/templates/builtins.txt
   django/trunk/tests/regressiontests/dateformat/tests.py
   django/trunk/tests/regressiontests/utils/tests.py
Log:
Fixed #10825: fixed the 'U' format code to dateformat (and the date/now 
filter/tag). Thanks to gsong and mir.

Modified: django/trunk/django/utils/dateformat.py
===
--- django/trunk/django/utils/dateformat.py 2009-05-08 12:58:57 UTC (rev 
10715)
+++ django/trunk/django/utils/dateformat.py 2009-05-08 13:39:37 UTC (rev 
10716)
@@ -11,12 +11,13 @@
 >>>
 """
 
+import re
+import time
+import calendar
 from django.utils.dates import MONTHS, MONTHS_3, MONTHS_AP, WEEKDAYS, 
WEEKDAYS_ABBR
 from django.utils.tzinfo import LocalTimezone
 from django.utils.translation import ugettext as _
 from django.utils.encoding import force_unicode
-from calendar import isleap, monthrange
-import re, time
 
 re_formatchars = re.compile(r'(? 4:
-if jan1_weekday == 5 or (jan1_weekday == 6 and 
isleap(self.data.year-1)):
+if jan1_weekday == 5 or (jan1_weekday == 6 and 
calendar.isleap(self.data.year-1)):
 week_number = 53
 else:
 week_number = 52
 else:
-if isleap(self.data.year):
+if calendar.isleap(self.data.year):
 i = 366
 else:
 i = 365

Modified: django/trunk/docs/ref/templates/builtins.txt
===
--- django/trunk/docs/ref/templates/builtins.txt2009-05-08 12:58:57 UTC 
(rev 10715)
+++ django/trunk/docs/ref/templates/builtins.txt2009-05-08 13:39:37 UTC 
(rev 10716)
@@ -506,7 +506,8 @@
   month, 2 characters.
 t Number of days in the given month.``28`` to 
``31``
 T Time zone of this machine.``'EST'``, 
``'MDT'``
-U Not implemented.
+U Seconds since the Unix Epoch
+  (January 1 1970 00:00:00 UTC).
 w Day of the week, digits without   ``'0'`` 
(Sunday) to ``'6'`` (Saturday)
   leading zeros.
 W ISO-8601 week number of year, with``1``, ``53``

Modified: django/trunk/tests/regressiontests/dateformat/tests.py
===
--- django/trunk/tests/regressiontests/dateformat/tests.py  2009-05-08 
12:58:57 UTC (rev 10715)
+++ django/trunk/tests/regressiontests/dateformat/tests.py  2009-05-08 
13:39:37 UTC (rev 10716)
@@ -37,7 +37,7 @@
 u'31'
 >>> no_tz or format(my_birthday, 'T') == 'CET'
 True
->>> no_tz or format(my_birthday, 'U') == '300531600'
+>>> no_tz or format(my_birthday, 'U') == '300315600'
 True
 >>> format(my_birthday, 'w')
 u'0'

Added: django/trunk/tests/regressiontests/utils/dateformat.py
===
--- django/trunk/tests/regressiontests/utils/dateformat.py  
(rev 0)
+++ django/trunk/tests/regressiontests/utils/dateformat.py  2009-05-08 
13:39:37 UTC (rev 10716)
@@ -0,0 +1,48 @@
+"""
+>>> from datetime import datetime, date
+>>> from django.utils.dateformat import format
+>>> from django.utils.tzinfo import FixedOffset, LocalTimezone
+
+# date
+>>> d = date(2009, 5, 16)
+>>> date.fromtimestamp(int(format(d, 'U'))) == d
+True
+
+# Naive datetime
+>>> dt = datetime(2009, 5, 16, 5, 30, 30)
+>>> datetime.fromtimestamp(int(format(dt, 'U'))) == dt
+True
+
+# datetime with local tzinfo
+>>> ltz = LocalTimezone(datetime.now())
+>>> dt = datetime(2009, 5, 16, 5, 30, 30, tzinfo=ltz)
+>>> datetime.fromtimestamp(int(format(dt, 'U')), ltz) == dt
+True
+>>> datetime.fromtimestamp(int(format(dt, 'U'))) == dt.replace(tzinfo=None)
+True
+
+# datetime with arbitrary tzinfo
+>>> tz = FixedOffset(-510)
+>>> ltz = LocalTimezone(datetime.now())
+>>> dt = datetime(2009, 5, 16, 5, 30, 30, tzinfo=tz)
+>>> datetime.fromtimestamp(int(format(dt, 'U')), tz) == dt
+True
+>>> datetime.fromtimestamp(int(format(dt, 'U')), ltz) == dt
+True
+>>> datetime.fromtimestamp(int(format(dt, 'U'))) == 
dt.astimezone(ltz).replace(tzinfo=None)
+True
+>>> datetime.fromtimestamp(int(format(dt, 'U')), tz).utctimetuple() == 
dt.utctimetuple()
+True
+>>> datetime.fromtimestamp(int(format(dt, 'U')), ltz).utctimetuple() == 
dt.utctimetuple()
+True
+
+# Epoch
+>>> utc = FixedOffset(0)
+>>> udt = datetime(1970, 1, 1, tzinfo=utc)
+>>> format(udt, 'U')
+u'0'
+"""
+
+if __name__ == "__main__":
+import doctest
+doctest.testmod()

Modified: django/trunk/tests/regressiontests/utils/tests.py
===

Re: [Django] #11042: admin inlines of inherited models break on edit submit after changeset 10666

[Django]

#11042: admin inlines of inherited models break on edit submit after changeset
10666
+---
  Reporter:  jsmullyan  | Owner:  mir
Status:  new| Milestone: 
 Component:  Uncategorized  |   Version:  1.0
Resolution: |  Keywords: 
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by mir):

  * owner:  nobody => mir
  * 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] #10795: Add Link to modelformset_factory

[Django]

#10795: Add Link to modelformset_factory
+---
  Reporter:  csshef | Owner:  Uninen
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Uninen):

  * owner:  nobody => Uninen

-- 
Ticket URL: 
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] #11041: Document all QuerySet methods in QuerySet API

[Django]

#11041: Document all QuerySet methods in QuerySet API
---+
 Reporter:  idangazit  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Right now it is missing any mention of the update() and delete() methods,
 and possibly more.

 There is some documentation in
 [http://docs.djangoproject.com/en/dev/topics/db/queries/ Making Queries]
 but no reference documentation for some methods in the
 [http://docs.djangoproject.com/en/dev/ref/models/querysets/ QuerySet API
 reference].

-- 
Ticket URL: 
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] #11040: Updated Finnish translation

[Django]

#11040: Updated Finnish translation
--+-
 Reporter:  Uninen|   Owner:  nobody
   Status:  new   |   Milestone:  1.1   
Component:  Translations  | Version:  SVN   
 Keywords:  finnish, fi, translation  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Here's an updated translation for Finnish. Also corrected some minor
 spelling issues in the process.

-- 
Ticket URL: 
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] #10672: Proxy Model does not send save signal

[Django]

#10672: Proxy Model does not send save signal
---+
  Reporter:  zbyte64   | Owner:  Nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by UloPe):

  * owner:  UloPe => Nobody

Comment:

 I have to leave the sprint pretty soon, so I'm reassigning to nobdy since
 I didn't come up with any sensible way to imporove this patch

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

Re: [Django] #10272: document signatures and optional parameters for the contrib.auth views

[Django]

#10272: document signatures and optional parameters for the contrib.auth views
+---
  Reporter:  gwilson| Owner:  idangazit
Status:  assigned   | Milestone:  1.1  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by idangazit):

  * 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] #10273: document missing auth forms

[Django]

#10273: document missing auth forms
+---
  Reporter:  gwilson| Owner:  jacob
Status:  assigned   | Milestone:  1.1  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by idangazit):

  * 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] #10950: Unused import in django/forms/fields.py

[Django]

#10950: Unused import in django/forms/fields.py
-+--
  Reporter:  dc  | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by dc):

  * has_patch:  0 => 1
  * needs_tests:  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
-~--~~~~--~~--~--~---