Re: [Django] #10886: "Reversing Admin URLs" section provides invalid examples

[Django]

#10886: "Reversing Admin URLs" section provides invalid examples
--+-
  Reporter:  Simon Meers   | Owner:  nobody
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 Alex):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * milestone:  => 1.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] #10886: "Reversing Admin URLs" section provides invalid examples

[Django]

#10886: "Reversing Admin URLs" section provides invalid examples
-+--
 Reporter:  Simon Meers   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Documentation| Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 {{{
 urlresolvers.reverse('admin_polls_choice_change', (c.id,))
 }}}

 should be:

 {{{
 urlresolvers.reverse('admin_polls_choice_change', args=[c.id,])
 }}}

 otherwise (c.id,) is interpreted as the urlconf argument, and an error
 such as:

 {{{
 AttributeError: 'int' object has no attribute 'regex'
 }}}

 is raised, since (c.id,) is not a urlconf. The second example with
 custom_admin_... should also be changed.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10618 - in django/branches/releases/1.0.X: . django/contrib/csrf

[noreply]

Author: lukeplant
Date: 2009-04-21 18:44:28 -0500 (Tue, 21 Apr 2009)
New Revision: 10618

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/contrib/csrf/middleware.py
Log:
[1.0.X] Fixed #10884 - more lenient regexp for matching forms in CSRF 
post-processing
  
Thanks to Ryszard Szopa for the report and fix

Backport of r10617



Property changes on: django/branches/releases/1.0.X
___
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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603
   + 
/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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603,10617

Modified: django/branches/releases/1.0.X/django/contrib/csrf/middleware.py
===
--- django/branches/releases/1.0.X/django/contrib/csrf/middleware.py
2009-04-21 23:31:01 UTC (rev 10617)
+++ django/branches/releases/1.0.X/django/contrib/csrf/middleware.py
2009-04-21 23:44:28 UTC (rev 10618)
@@ -16,7 +16,7 @@
 _ERROR_MSG = mark_safe('http://www.w3.org/1999/xhtml"; 
xml:lang="en">403 ForbiddenCross Site Request Forgery 
detected. Request aborted.')
 
 _POST_FORM_RE = \
-re.compile(r'(]*\bmethod=(\'|"|)POST(\'|"|)\b[^>]*>)', 
re.IGNORECASE)
+re.compile(r'(]*\bmethod\s*=\s*(\'|"|)POST(\'|"|)\b[^>]*>)', 
re.IGNORECASE)
 
 _HTML_TYPES = ('text/html', 'application/xhtml+xml')
 


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

[Changeset] r10617 - django/trunk/django/contrib/csrf

[noreply]

Author: lukeplant
Date: 2009-04-21 18:31:01 -0500 (Tue, 21 Apr 2009)
New Revision: 10617

Modified:
   django/trunk/django/contrib/csrf/middleware.py
Log:
Fixed #10884 - more lenient regexp for matching forms in CSRF post-processing

Thanks to Ryszard Szopa for the report and fix


Modified: django/trunk/django/contrib/csrf/middleware.py
===
--- django/trunk/django/contrib/csrf/middleware.py  2009-04-21 22:40:49 UTC 
(rev 10616)
+++ django/trunk/django/contrib/csrf/middleware.py  2009-04-21 23:31:01 UTC 
(rev 10617)
@@ -20,7 +20,7 @@
 _ERROR_MSG = mark_safe('http://www.w3.org/1999/xhtml"; 
xml:lang="en">403 ForbiddenCross Site Request Forgery 
detected. Request aborted.')
 
 _POST_FORM_RE = \
-re.compile(r'(]*\bmethod=(\'|"|)POST(\'|"|)\b[^>]*>)', 
re.IGNORECASE)
+re.compile(r'(]*\bmethod\s*=\s*(\'|"|)POST(\'|"|)\b[^>]*>)', 
re.IGNORECASE)
 
 _HTML_TYPES = ('text/html', 'application/xhtml+xml')
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10885: Update the Hebrew Translaions for 1.1

[Django]

#10885: Update the Hebrew Translaions for 1.1
---+
  Reporter:  Alex  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 Moses Gaynor and Yaron McNabb should be credited for this.

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

Re: [Django] #10885: Update the Hebrew Translaions for 1.1

[Django]

#10885: Update the Hebrew Translaions for 1.1
---+
  Reporter:  Alex  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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] #10885: Update the Hebrew Translaions for 1.1

[Django]

#10885: Update the Hebrew Translaions for 1.1
--+-
 Reporter:  Alex  |   Owner:  nobody
   Status:  new   |   Milestone:  1.1   
Component:  Translations  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The hebrew translation is out of date.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10616 - in django/branches/releases/1.0.X/django/contrib/gis: db/models/sql tests/relatedapp

[noreply]

Author: jbronn
Date: 2009-04-21 17:40:49 -0500 (Tue, 21 Apr 2009)
New Revision: 10616

Modified:
   django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
   django/branches/releases/1.0.X/django/contrib/gis/tests/relatedapp/tests.py
Log:
[1.0.X] Fixed #10839 -- `GeoQuery` now unpickles properly on Oracle.

Backport of r10615 from trunk.


Modified: 
django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
2009-04-21 22:35:04 UTC (rev 10615)
+++ django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
2009-04-21 22:40:49 UTC (rev 10616)
@@ -30,6 +30,13 @@
 self.transformed_srid = None
 self.extra_select_fields = {}
 
+if SpatialBackend.oracle:
+# Have to override this so that GeoQuery, instead of OracleQuery,
+# is returned when unpickling.
+def __reduce__(self):
+callable, args, data = super(GeoQuery, self).__reduce__()
+return (unpickle_geoquery, (), data)
+
 def clone(self, *args, **kwargs):
 obj = super(GeoQuery, self).clone(*args, **kwargs)
 # Customized selection dictionary and transformed srid flag have
@@ -324,6 +331,15 @@
 # a lookup to a _related_ geographic field.
 return self._check_geo_field(self.model, field_name)
 
+if SpatialBackend.oracle:
+def unpickle_geoquery():
+"""
+Utility function, called by Python's unpickling machinery, that handles
+unpickling of GeoQuery subclasses of OracleQuery.
+"""
+return GeoQuery.__new__(GeoQuery)
+unpickle_geoquery.__safe_for_unpickling__ = True
+
 ### Field Classes for `convert_values` 
 class BaseField(object):
 def get_internal_type(self):

Modified: 
django/branches/releases/1.0.X/django/contrib/gis/tests/relatedapp/tests.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/tests/relatedapp/tests.py 
2009-04-21 22:35:04 UTC (rev 10615)
+++ django/branches/releases/1.0.X/django/contrib/gis/tests/relatedapp/tests.py 
2009-04-21 22:40:49 UTC (rev 10616)
@@ -137,6 +137,15 @@
 self.assertEqual(val_dict['id'], c_id)
 self.assertEqual(val_dict['location__id'], l_id)
 
+def test11_geoquery_pickle(self):
+"Ensuring GeoQuery objects are unpickled correctly.  See #10839."
+import pickle
+from django.contrib.gis.db.models.sql import GeoQuery
+qs = City.objects.all()
+q_str = pickle.dumps(qs.query)
+q = pickle.loads(q_str)
+self.assertEqual(GeoQuery, q.__class__)
+
 # TODO: Related tests for KML, GML, and distance lookups.
 
 def suite():


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10615 - in django/trunk/django/contrib/gis: db/models/sql tests/relatedapp

[noreply]

Author: jbronn
Date: 2009-04-21 17:35:04 -0500 (Tue, 21 Apr 2009)
New Revision: 10615

Modified:
   django/trunk/django/contrib/gis/db/models/sql/query.py
   django/trunk/django/contrib/gis/tests/relatedapp/tests.py
Log:
Fixed #10839 -- `GeoQuery` now unpickles properly on Oracle.


Modified: django/trunk/django/contrib/gis/db/models/sql/query.py
===
--- django/trunk/django/contrib/gis/db/models/sql/query.py  2009-04-21 
21:25:47 UTC (rev 10614)
+++ django/trunk/django/contrib/gis/db/models/sql/query.py  2009-04-21 
22:35:04 UTC (rev 10615)
@@ -33,6 +33,13 @@
 self.transformed_srid = None
 self.extra_select_fields = {}
 
+if SpatialBackend.oracle:
+# Have to override this so that GeoQuery, instead of OracleQuery,
+# is returned when unpickling.
+def __reduce__(self):
+callable, args, data = super(GeoQuery, self).__reduce__()
+return (unpickle_geoquery, (), data)
+
 def clone(self, *args, **kwargs):
 obj = super(GeoQuery, self).clone(*args, **kwargs)
 # Customized selection dictionary and transformed srid flag have
@@ -332,3 +339,12 @@
 # Otherwise, check by the given field name -- which may be
 # a lookup to a _related_ geographic field.
 return GeoWhereNode._check_geo_field(self.model._meta, field_name)
+
+if SpatialBackend.oracle:
+def unpickle_geoquery():
+"""
+Utility function, called by Python's unpickling machinery, that handles
+unpickling of GeoQuery subclasses of OracleQuery.
+"""
+return GeoQuery.__new__(GeoQuery)
+unpickle_geoquery.__safe_for_unpickling__ = True

Modified: django/trunk/django/contrib/gis/tests/relatedapp/tests.py
===
--- django/trunk/django/contrib/gis/tests/relatedapp/tests.py   2009-04-21 
21:25:47 UTC (rev 10614)
+++ django/trunk/django/contrib/gis/tests/relatedapp/tests.py   2009-04-21 
22:35:04 UTC (rev 10615)
@@ -222,6 +222,15 @@
 self.failUnless('Aurora' in names)
 self.failUnless('Kecksburg' in names)
 
+def test11_geoquery_pickle(self):
+"Ensuring GeoQuery objects are unpickled correctly.  See #10839."
+import pickle
+from django.contrib.gis.db.models.sql import GeoQuery
+qs = City.objects.all()
+q_str = pickle.dumps(qs.query)
+q = pickle.loads(q_str)
+self.assertEqual(GeoQuery, q.__class__)
+
 # TODO: Related tests for KML, GML, and distance lookups.
 
 def suite():


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10884: CSRF Middleware regular expression doesn't take in account spaces.

[Django]

#10884: CSRF Middleware regular expression doesn't take in account spaces.
-+--
 Reporter:  Ryszard Szopa   |   Owner:  nobody
   Status:  new  |   Milestone:  1.1   
Component:  Contrib apps | Version:  SVN   
 Keywords:  csrf |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 The CSRF protection middleware regular expression that looks for forms
 with method POST assumes that there are no spaces between the attribute
 name and the '=' sign or between the '=' sign and the attribute value.
 This means that forms like this:
 {{{
 
 ...
 
 }}}

 (which browsers generally accept and interpret correctly) won't be caught
 by the regexp, the inputs with the magic tokens be inserted, and the user
 will get a 403 Forbidden error. Moreover, additional whitespace is rather
 dificult to spot (and isn't obviously relevant to the issue of CSRF),
 making the whole thing rather frustrating to debug.

 A very easy fix is to change the regular expression:

 {{{
 _POST_FORM_RE = \
 re.compile(r'(]*\bmethod\s*=\s*(\'|"|)POST(\'|"|)\b[^>]*>)',
 re.IGNORECASE)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10614 - in django/branches/releases/1.0.X/django/contrib/gis: db/models/sql tests tests/distapp tests/geoapp tests/relatedapp

[noreply]

Author: jbronn
Date: 2009-04-21 16:25:47 -0500 (Tue, 21 Apr 2009)
New Revision: 10614

Modified:
   django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
   django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py
   django/branches/releases/1.0.X/django/contrib/gis/tests/distapp/tests.py
   django/branches/releases/1.0.X/django/contrib/gis/tests/geoapp/tests.py
   django/branches/releases/1.0.X/django/contrib/gis/tests/relatedapp/tests.py
Log:
[1.0.X] Fixed various Oracle errata and test failures present in this branch 
(including not going to 11).

Backport of Oracle-related changes from trunk in r10197.


Modified: 
django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
2009-04-21 20:14:42 UTC (rev 10613)
+++ django/branches/releases/1.0.X/django/contrib/gis/db/models/sql/query.py
2009-04-21 21:25:47 UTC (rev 10614)
@@ -201,7 +201,7 @@
 """
 if SpatialBackend.oracle:
 # Running through Oracle's first.
-value = super(GeoQuery, self).convert_values(value, field)
+value = super(GeoQuery, self).convert_values(value, field or 
GeomField())
 if isinstance(field, DistanceField):
 # Using the field's distance attribute, can instantiate
 # `Distance` with the right context.
@@ -325,15 +325,22 @@
 return self._check_geo_field(self.model, field_name)
 
 ### Field Classes for `convert_values` 
-class AreaField(object):
+class BaseField(object):
+def get_internal_type(self):
+"Overloaded method so OracleQuery.convert_values doesn't balk."
+return None
+
+if SpatialBackend.oracle: BaseField.empty_strings_allowed = False
+
+class AreaField(BaseField):
 def __init__(self, area_att):
 self.area_att = area_att
 
-class DistanceField(object):
+class DistanceField(BaseField):
 def __init__(self, distance_att):
 self.distance_att = distance_att
 
 # Rather than use GeometryField (which requires a SQL query
 # upon instantiation), use this lighter weight class.
-class GeomField(object): 
+class GeomField(BaseField): 
 pass

Modified: django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py 
2009-04-21 20:14:42 UTC (rev 10613)
+++ django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py 
2009-04-21 21:25:47 UTC (rev 10614)
@@ -13,7 +13,7 @@
 from django.contrib.gis.utils import HAS_GEOIP
 
 # Tests that require use of a spatial database (e.g., creation of models)
-test_models = ['geoapp',]
+test_models = ['geoapp', 'layermap', 'relatedapp']
 
 # Tests that do not require setting up and tearing down a spatial database.
 test_suite_names = [
@@ -21,15 +21,8 @@
 'test_measure',
 ]
 if HAS_GDAL:
-if oracle:
-# TODO: There's a problem with `select_related` and GeoQuerySet on
-# Oracle -- e.g., GeoModel.objects.distance(geom, 
field_name='fk__point')
-# doesn't work so we don't test `relatedapp`.
-test_models += ['distapp', 'layermap']
-elif postgis:
-test_models += ['distapp', 'layermap', 'relatedapp']
-elif mysql:
-test_models += ['relatedapp', 'layermap']
+if oracle or postgis:
+test_models.append('distapp')
 
 test_suite_names += [
 'test_gdal_driver',

Modified: 
django/branches/releases/1.0.X/django/contrib/gis/tests/distapp/tests.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/tests/distapp/tests.py
2009-04-21 20:14:42 UTC (rev 10613)
+++ django/branches/releases/1.0.X/django/contrib/gis/tests/distapp/tests.py
2009-04-21 21:25:47 UTC (rev 10614)
@@ -115,8 +115,12 @@
 # with different projected coordinate systems.
 dist1 = SouthTexasCity.objects.distance(lagrange, field_name='point')
 dist2 = SouthTexasCity.objects.distance(lagrange)  # Using 
GEOSGeometry parameter
-dist3 = SouthTexasCityFt.objects.distance(lagrange.ewkt) # Using EWKT 
string parameter.
-dist4 = SouthTexasCityFt.objects.distance(lagrange)
+if oracle:
+dist_qs = [dist1, dist2]
+else:
+dist3 = SouthTexasCityFt.objects.distance(lagrange.ewkt) # Using 
EWKT string parameter.
+dist4 = SouthTexasCityFt.objects.distance(lagrange)
+dist_qs = [dist1, dist2, dist3, dist4]
 
 # Original query done on PostGIS, have to adjust AlmostEqual tolerance
 # for Oracle.
@@ -124,7 +128,7 @@
 else: tol = 5
 
 # Ensuring expected distances are returned for each distance queryset.
- 

[Changeset] r10613 - django/branches/releases/1.0.X/django/contrib/gis/tests

[noreply]

Author: jbronn
Date: 2009-04-21 15:14:42 -0500 (Tue, 21 Apr 2009)
New Revision: 10613

Modified:
   django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py
Log:
[1.0.X] Fixed #10791 -- The GeoDjango test runner now respects the `--noinput` 
command-line option, thanks to seanl for ticket & patch.

Backport of r10601 from trunk.


Modified: django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py
===
--- django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py 
2009-04-21 18:58:32 UTC (rev 10612)
+++ django/branches/releases/1.0.X/django/contrib/gis/tests/__init__.py 
2009-04-21 20:14:42 UTC (rev 10613)
@@ -193,7 +193,7 @@
 suite.addTest(test)
 
 # Creating the test spatial database.
-create_spatial_db(test=True, verbosity=verbosity)
+create_spatial_db(test=True, verbosity=verbosity, autoclobber=not 
interactive)
 
 # Executing the tests (including the model tests), and destorying the
 # test database after the tests have completed.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10839: Pickling queryset.query doesn't work for gis models on Oracle

[Django]

#10839: Pickling queryset.query doesn't work for gis models on Oracle
-+--
  Reporter:  jtiai   | Owner:  jbronn
Status:  new | Milestone:
 Component:  GIS |   Version:  SVN   
Resolution:  |  Keywords:  oracle gis
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by jbronn):

  * owner:  nobody => jbronn
  * needs_tests:  0 => 1

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

Re: [Django] #2443: Add IntervalField to database models

[Django]

#2443: Add IntervalField to database models
---+
  Reporter:  ben.tuc...@gmail.com  | Owner:  Gulopine   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
IntervalField interval duration DurationField
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by Adys):

 It feels wrong to "store" as seconds. Then again, just my opinion.[[BR]]
 [[BR]]
 I was thinking the same thing about a js helper, and a friend came up with
 the idea of just parsing the field for units. I'll see if I can get a few
 mins to work on it tonight, I really like the idea. Three big
 advantages:[[BR]]
 - No need for javascript (6 weeks would be "6w", 30 seconds would be
 "30s", 2 hours would be "2h", etc)[[BR]]
 - Easy to understand, very user friendly (parsing "3h 10d" is okay, I
 suppose we'd give validationerror on "1h 10m 2h" or similar tho)[[BR]]
 - No need for multiple input boxes, avoids confusion[[BR]]
 [[BR]]
 On a slightly-related note, I don't know what to do about microseconds.
 Standard display is µs, but that could cause problems for users with
 special keyboard layouts etc.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10883: Template does not exist for admin site on initial creation

[Django]

#10883: Template does not exist for admin site on initial creation
+---
  Reporter:  rodericj   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  0.96  
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Any questions about getting stuff to work on an old level of Django should
 be directed to the django-users list.  You may be hitting a problem in the
 old install where template and other data files were not installed
 properly.  This has been corrected in the current code, so one fix would
 be to upgrade to the latest release.  Alternatively if you post to django-
 users someone may be able to help you out with how to manually get the
 templates installed properly.

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

[Changeset] r10612 - in django/branches/releases/1.0.X: . django/forms tests/regressiontests/admin_views

[noreply]

Author: kmtracey
Date: 2009-04-21 13:58:32 -0500 (Tue, 21 Apr 2009)
New Revision: 10612

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/forms/models.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 #9651: fixed save_as with inline forms. Thanks, kmike and 
Mnewman. 

Backport of r10353 from trunk.



Property changes on: django/branches/releases/1.0.X
___
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,10354-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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603
   + 
/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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603

Modified: django/branches/releases/1.0.X/django/forms/models.py
===
--- django/branches/releases/1.0.X/django/forms/models.py   2009-04-21 
18:36:45 UTC (rev 10611)
+++ django/branches/releases/1.0.X/django/forms/models.py   2009-04-21 
18:58:32 UTC (rev 10612)
@@ -496,6 +496,9 @@
 # Remove the primary key from the form's data, we are only
 # creating new instances
 form.data[form.add_prefix(self._pk_field.name)] = None
+
+# Remove the foreign key from the form's data
+form.data[form.add_prefix(self.fk.name)] = None
 return form
 
 #...@classmethod

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-04-21 18:36:45 UTC (rev 10611)
+++ django/branches/releases/1.0.X/tests/regressionte

[Django] #10883: Template does not exist for admin site on initial creation

[Django]

#10883: Template does not exist for admin site on initial creation
---+
 Reporter:  rodericj   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  0.96  
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://www.djangoproject.com/documentation/0.96/tutorial02/

 In the older versions of django there is a setup for an admin site. You
 can add the site to the INSTALLED_APPS list but the template for the admin
 site (admin/index.html) is never defined.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #2443: Add IntervalField to database models

[Django]

#2443: Add IntervalField to database models
---+
  Reporter:  ben.tuc...@gmail.com  | Owner:  Gulopine   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
IntervalField interval duration DurationField
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by Adys):

 For the interface part, there's two decent choices.[[BR]]
 Either go for a parse of the values in a single field, for example (input)
 "3d 12h 4m 7s", "7d 10m", "15 ms"; output would be highest value
 possible first - 6ms would be "1m", 75000ms would be "1m 15s"
 (abbreviations are up for change, would go for the standard ones).[[BR]]
 [[BR]]
 Or, go for a single field with a  box, with some js shortcuts.
 [___] [ Unit ... ] (X)[[BR]][[BR]]

 In both cases, the possible units would be years, months, weeks, days,
 hours, minutes, seconds, milliseconds, microseconds (assuming microsecond
 precision). Thoughts?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #5253: serializer for csv format for loaddata and dumpdata

[Django]

#5253: serializer for csv format for loaddata and dumpdata
+---
  Reporter:  Adam Schmideg   | Owner:  erob  

Status:  new| Milestone:

 Component:  Serialization  |   Version:  SVN   

Resolution: |  Keywords:  csv, 
foreign keys, feature
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  1  |   Needs_tests:  1 

Needs_better_patch:  1  |  
+---
Comment (by erob):

 Replying to [comment:15 Alex]:
 > Django .96 is not eligible for new features, this patch should be
 written against the latest trunk.

 I agree, except that my client requires that it works with Django 0.96.3.

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

Re: [Django] #5253: serializer for csv format for loaddata and dumpdata

[Django]

#5253: serializer for csv format for loaddata and dumpdata
+---
  Reporter:  Adam Schmideg   | Owner:  erob  

Status:  new| Milestone:

 Component:  Serialization  |   Version:  SVN   

Resolution: |  Keywords:  csv, 
foreign keys, feature
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  1  |   Needs_tests:  1 

Needs_better_patch:  1  |  
+---
Comment (by Alex):

 The patch has been uploaded fine, the preview doesn't always show
 correctly.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #5253: serializer for csv format for loaddata and dumpdata

[Django]

#5253: serializer for csv format for loaddata and dumpdata
+---
  Reporter:  Adam Schmideg   | Owner:  erob  

Status:  new| Milestone:

 Component:  Serialization  |   Version:  SVN   

Resolution: |  Keywords:  csv, 
foreign keys, feature
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  1  |   Needs_tests:  1 

Needs_better_patch:  1  |  
+---
Comment (by erob):

 giving up trying to upload the patch... something seems broken with the
 file uploader thing.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10611 - in django/branches/releases/1.0.X: . docs/howto

[noreply]

Author: kmtracey
Date: 2009-04-21 13:36:45 -0500 (Tue, 21 Apr 2009)
New Revision: 10611

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/howto/custom-model-fields.txt
Log:
[1.0.X] Fixed #10693: updated params in the docs. 

r10324 from trunk.



Property changes on: django/branches/releases/1.0.X
___
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,10325,10328-10329,10333-10344,10348-10351,10354-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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603
   + 
/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,10354-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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603

Modified: django/branches/releases/1.0.X/docs/howto/custom-model-fields.txt
===
--- django/branches/releases/1.0.X/docs/howto/custom-model-fields.txt   
2009-04-21 18:34:27 UTC (rev 10610)
+++ django/branches/releases/1.0.X/docs/howto/custom-model-fields.txt   
2009-04-21 18:36:45 UTC (rev 10611)
@@ -198,7 +198,6 @@
 * :attr:`~django.db.models.Field.blank`
 * :attr:`~django.db.models.Field.null`
 * :attr:`~django.db.models.Field.db_index`
-* :attr:`~django.db.models.Field.core`
 * :attr:`~django.db.models.Field.rel`: Used for related fields (like
   :class:`ForeignKey`). For advanced use only.
 * :attr:`~django.db.models.Field.default`
@@ -206,7 +205,6 @@
 * :attr:`~django.db.models.Field.serialize`: If ``False``, the field will
   not be serialized when the model is passed to Django's :ref:`serializers
   `. Defaults to ``True``.
-* :attr:`~django.db.models.Field.prepopulate_from`
 * :attr:`~django.db.models.Field.unique_for_date`
 * :attr:`~django.db.models.Field.unique_for_month`
 * :attr:`~django.db.models.Field.unique_for_year`
@@ -216,6 +214,9 @@
 * :attr:`~django.db.mod

Re: [Django] #5253: serializer for csv format for loaddata and dumpdata

[Django]

#5253: serializer for csv format for loaddata and dumpdata
+---
  Reporter:  Adam Schmideg   | Owner:  erob  

Status:  new| Milestone:

 Component:  Serialization  |   Version:  SVN   

Resolution: |  Keywords:  csv, 
foreign keys, feature
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  1  |   Needs_tests:  1 

Needs_better_patch:  1  |  
+---
Comment (by Alex):

 Django .96 is not eligible for new features, this patch should be written
 against the latest trunk.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #2443: Add IntervalField to database models

[Django]

#2443: Add IntervalField to database models
---+
  Reporter:  ben.tuc...@gmail.com  | Owner:  Gulopine   
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  
IntervalField interval duration DurationField
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by Adys):

 I had a look through the patch today. Using a DecimalField and playing
 with commas seems unreasonably hacky. Is using a 64-bit int an option? It
 shouldn't be a problem under postgres, but I don't know about the other db
 backends.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10610 - django/branches/releases/1.0.X

[noreply]

Author: kmtracey
Date: 2009-04-21 13:34:27 -0500 (Tue, 21 Apr 2009)
New Revision: 10610

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X] Unblocked r10324 and 10353.  These changesets are applicable to the 
branch as well.



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-10324,10326-10327,10330-10332,10345-10347,10352-10353,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
   + 
/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


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #5253: serializer for csv format for loaddata and dumpdata

[Django]

#5253: serializer for csv format for loaddata and dumpdata
+---
  Reporter:  Adam Schmideg   | Owner:  erob  

Status:  new| Milestone:

 Component:  Serialization  |   Version:  SVN   

Resolution: |  Keywords:  csv, 
foreign keys, feature
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  1  |   Needs_tests:  1 

Needs_better_patch:  1  |  
+---
Comment (by erob):

 Made a updated patch that seems to work with Django 0.96.3. I also changed
 the is_string_field
 function so that it doesn't require importing model definitions by using
 slightly improved
 type introspection.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10716: Syntax error and bug in db/backends/oracle/creation.py

[Django]

#10716: Syntax error and bug in db/backends/oracle/creation.py
---+
  Reporter:  canarix   | Owner:  nobody
Status:  closed| Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  fixed |  Keywords:  oracle
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mboersma):

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

Comment:

 Karen's new patch looks sane enough to me, and does work.  I made similar
 changes to the 1.0.X code and checked this in to both.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10609 - django/branches/releases/1.0.X/django/db/backends/oracle

[noreply]

Author: mboersma
Date: 2009-04-21 13:09:52 -0500 (Tue, 21 Apr 2009)
New Revision: 10609

Modified:
   django/branches/releases/1.0.X/django/db/backends/oracle/creation.py
Log:
[1.0.X] Fixed #10716 so Oracle tests run again. Thanks very much, kmtracey.


Modified: django/branches/releases/1.0.X/django/db/backends/oracle/creation.py
===
--- django/branches/releases/1.0.X/django/db/backends/oracle/creation.py
2009-04-21 18:09:03 UTC (rev 10608)
+++ django/branches/releases/1.0.X/django/db/backends/oracle/creation.py
2009-04-21 18:09:52 UTC (rev 10609)
@@ -56,7 +56,6 @@
 'tblspace_temp': TEST_DATABASE_TBLSPACE_TMP,
 }
 
-self.remember['name'] = settings.DATABASE_NAME
 self.remember['user'] = settings.DATABASE_USER
 self.remember['passwd'] = settings.DATABASE_PASSWORD
 
@@ -109,8 +108,7 @@
 print "Tests cancelled."
 sys.exit(1)
 
-settings.DATABASE_NAME = TEST_DATABASE_NAME
-settings.DATABASE_USER = TEST_DATABASE_USER
+settings.TEST_DATABASE_USER = settings.DATABASE_USER = 
TEST_DATABASE_USER
 settings.DATABASE_PASSWORD = TEST_DATABASE_PASSWD
 
 return settings.DATABASE_NAME
@@ -126,7 +124,6 @@
 TEST_DATABASE_TBLSPACE = self._test_database_tblspace(settings)
 TEST_DATABASE_TBLSPACE_TMP = self._test_database_tblspace_tmp(settings)
 
-settings.DATABASE_NAME = self.remember['name']
 settings.DATABASE_USER = self.remember['user']
 settings.DATABASE_PASSWORD = self.remember['passwd']
 
@@ -138,7 +135,6 @@
 'tblspace_temp': TEST_DATABASE_TBLSPACE_TMP,
 }
 
-self.remember['name'] = settings.DATABASE_NAME
 self.remember['user'] = settings.DATABASE_USER
 self.remember['passwd'] = settings.DATABASE_PASSWORD
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10608 - django/trunk/django/db/backends/oracle

[noreply]

Author: mboersma
Date: 2009-04-21 13:09:03 -0500 (Tue, 21 Apr 2009)
New Revision: 10608

Modified:
   django/trunk/django/db/backends/oracle/creation.py
Log:
Fixed #10716 so Oracle tests run again.  Thanks very much, kmtracey.


Modified: django/trunk/django/db/backends/oracle/creation.py
===
--- django/trunk/django/db/backends/oracle/creation.py  2009-04-21 17:56:54 UTC 
(rev 10607)
+++ django/trunk/django/db/backends/oracle/creation.py  2009-04-21 18:09:03 UTC 
(rev 10608)
@@ -56,7 +56,6 @@
 'tblspace_temp': TEST_DATABASE_TBLSPACE_TMP,
 }
 
-self.remember['name'] = settings.DATABASE_NAME
 self.remember['user'] = settings.DATABASE_USER
 self.remember['passwd'] = settings.DATABASE_PASSWORD
 
@@ -109,8 +108,7 @@
 print "Tests cancelled."
 sys.exit(1)
 
-settings.DATABASE_NAME = 
self.connection.settings_dict["DATABASE_NAME"] = TEST_DATABASE_NAME
-settings.DATABASE_USER = 
self.connection.settings_dict["DATABASE_USER"] = TEST_DATABASE_USER
+settings.TEST_DATABASE_USER = settings.DATABASE_USER = 
self.connection.settings_dict["DATABASE_USER"] = TEST_DATABASE_USER
 settings.DATABASE_PASSWORD = 
self.connection.settings_dict["DATABASE_PASSWORD"] = TEST_DATABASE_PASSWD
 
 return settings.DATABASE_NAME
@@ -126,7 +124,6 @@
 TEST_DATABASE_TBLSPACE = self._test_database_tblspace(settings)
 TEST_DATABASE_TBLSPACE_TMP = self._test_database_tblspace_tmp(settings)
 
-settings.DATABASE_NAME = 
self.connection.settings_dict["DATABASE_NAME"] = self.remember['name']
 settings.DATABASE_USER = 
self.connection.settings_dict["DATABASE_USER"] = self.remember['user']
 settings.DATABASE_PASSWORD = 
self.connection.settings_dict["DATABASE_PASSWORD"] = self.remember['passwd']
 
@@ -138,7 +135,6 @@
 'tblspace_temp': TEST_DATABASE_TBLSPACE_TMP,
 }
 
-self.remember['name'] = settings.DATABASE_NAME
 self.remember['user'] = settings.DATABASE_USER
 self.remember['passwd'] = settings.DATABASE_PASSWORD
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10607 - in django/branches/releases/1.0.X: . tests/regressiontests/queries

[noreply]

Author: kmtracey
Date: 2009-04-21 12:56:54 -0500 (Tue, 21 Apr 2009)
New Revision: 10607

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/tests/regressiontests/queries/models.py
Log:
[1.0.X] Added a test from Jamie Gennis to ensure #9848 doesn't reappear.

The bug itself was fixed at some point in the past months (there have
been a few improvements to update() recently). Fixed #9848. 

(Merge of r10528 from trunk.  Per comment in #9848 the fix was in r9967,
which was backported in r9968, thus it seems right to backport the new
test as well.)



Property changes on: django/branches/releases/1.0.X
___
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,10325,10328-10329,10333-10344,10348-10351,10354-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,10530-10535,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603
   + 
/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,10325,10328-10329,10333-10344,10348-10351,10354-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,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603

Modified: django/branches/releases/1.0.X/tests/regressiontests/queries/models.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/queries/models.py  
2009-04-21 17:48:00 UTC (rev 10606)
+++ django/branches/releases/1.0.X/tests/regressiontests/queries/models.py  
2009-04-21 17:56:54 UTC (rev 10607)
@@ -1096,6 +1096,23 @@
 >>> list(Note.objects.filter(pk__in=g())) == [n_obj]
 True
 
+Make sure that updates which only filter on sub-tables don't inadvertently
+update the wrong records (bug #9848).
+
+# Make sure that the IDs from different tables don't happen to match.
+>>> Ranking.objects.filter(author__name='a1')
+[]
+>>> Ranking.objects.filter(author__name='a1').update(rank='4')
+1
+>>> r = Ranking.objects.filter(author__name='a1')[0]
+>>> r.id != r.author.id
+True
+>>> r.rank
+4
+>>> r.rank = 3
+>>> r.save()
+>>> Ranking.objects.all()

[Changeset] r10606 - in django/branches/releases/1.0.X: . django/contrib/admin/media/css

[noreply]

Author: kmtracey
Date: 2009-04-21 12:48:00 -0500 (Tue, 21 Apr 2009)
New Revision: 10606

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/contrib/admin/media/css/rtl.css
Log:
[1.0.X] Fixed #10601 -- Fixed edit inline display in admin for right-to-left 
locales. r10524 from trunk.

Also updated svnmerge metadata to reflect other changesets that have already 
been applied to the branch.



Property changes on: django/branches/releases/1.0.X
___
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,10325,10328-10329,10333-10344,10348-10351,10354-10356,10358-10363,10365-10368,10371-10380,10386-10406,10411,10413-10414,10418-10427,10429-10437,10440,10444-10445,10447-10450,10452-10453,10457-10464,10466-10467,10469-10480,10482-10485,10489-10492,10495-10497,10499-10500,10508,10511,10513,10517,10519,10550,10552,10554,10556,10561,10563-10564,10567,10573-10574
   + 
/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,10325,10328-10329,10333-10344,10348-10351,10354-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,10530-10535,10537,10539-10542,10544-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10600,10603

Modified: django/branches/releases/1.0.X/django/contrib/admin/media/css/rtl.css
===
--- django/branches/releases/1.0.X/django/contrib/admin/media/css/rtl.css   
2009-04-21 16:41:33 UTC (rev 10605)
+++ django/branches/releases/1.0.X/django/contrib/admin/media/css/rtl.css   
2009-04-21 17:48:00 UTC (rev 10606)
@@ -54,3 +54,15 @@
 
 /* x unsorted */
 .inline-related h2 { text-align:right }
+
+.inline-related h3 span.delete {
+padding-right: 20px;
+padding-left: inherit;
+left: 10px;
+right: inherit;
+}
+
+.inline-related h3 span.delete label {
+margin-left: inherit;
+margin-right: 2px;
+}


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10109: Move raw sql from models.fields.related to models.sql.query

[Django]

#10109: Move raw sql from models.fields.related to models.sql.query
---+
  Reporter:  david | Owner:  david
Status:  new   | Milestone:   
 Component:  Database layer (models, ORM)  |   Version:  1.0  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  1 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 Noting here that this(or some variant thereof) is going to be a blocker on
 having many to many fields work correctly with Multiple Database
 support(GSOC).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r10605 - django/branches/releases/1.0.X

[noreply]

Author: kmtracey
Date: 2009-04-21 11:41:33 -0500 (Tue, 21 Apr 2009)
New Revision: 10605

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X] Blocked a bunch of changesets related to new function from merge to 
branch.



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-10324,10326-10327,10330-10332,10345-10347,10352-10353,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,10521-10523,10560,10562,10565-10566,10575
   + 
/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-10324,10326-10327,10330-10332,10345-10347,10352-10353,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


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10882: FormWizard process_step receives yet to be validated form for previous steps

[Django]

#10882: FormWizard process_step receives yet to be validated form for previous
steps
---+
 Reporter:  graham.carl...@maplecroft.com  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  django.contrib.formtools   | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The docs for FormWizard process_step state that "The Form is guaranteed to
 have clean, valid data." and so you might assume that the form it supplies
 is ready to use when passed to this method. However its only the current
 step that gets a form that has the cleaned_data property immediately
 accessible, whereas previous steps require the form.is_valid method to be
 called.

 So it seems that the code should call is_valid on forms from previous
 steps before passing the form to process_step. Presumably as the docs
 state the form would always be valid and if not then somehow the hash has
 been defeated.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10881: db.backends.postgresql.operations.sequence_reset_sql and M2M fields with non-integer PKs

[Django]

#10881: db.backends.postgresql.operations.sequence_reset_sql and M2M fields with
non-integer PKs
---+
 Reporter:  gordyt |   Owner:  
nobody
   Status:  new|   Milestone:   
 
Component:  Database layer (models, ORM)   | Version:  
1.0   
 Keywords:  postgresql,operations,sequence_reset_sql,loaddata  |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 Near the end of the command `python manage.py loaddata ...` the
 `sequence_reset_sql` is called.  This part of the method is run for models
 that contain many-to-many fields:
 {{{
 for f in model._meta.many_to_many:
 output.append("%s setval('%s', coalesce(max(%s), 1), max(%s) %s
 null) %s %s;" % \
 (style.SQL_KEYWORD('SELECT'),
 style.SQL_FIELD(qn('%s_id_seq' % f.m2m_db_table())),
 style.SQL_FIELD(qn('id')),
 style.SQL_FIELD(qn('id')),
 style.SQL_KEYWORD('IS NOT'),
 style.SQL_KEYWORD('FROM'),
 style.SQL_TABLE(qn(f.m2m_db_table()
 }}}

 Under normal circumstances this is fine.  But if you are using your own
 model to manage the M2M relationship (specified via the `through=xxx`
 parameter in the `ManyToManyField`) and that model uses a non-integer
 primary key, then this part of the method generates invalid SQL code.

 I have attached two files to this ticket.  The `models.py` file has
 additional comments at the top that shows the output of running the
 `loaddata` command.  It is self-contained except that is uses the
 UUIDField from the django-extensions project.  This version of a UUIDField
 is a simple `CharField` extension.

 The file `strtest_dump.json` is a very small file created by the
 `dumpdata` command.  It has data for 3 authors and 1 book and the entries
 to join them together.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #3872: Bug in SetRemoteAddrFromForwardedFor middleware

[Django]

#3872: Bug in SetRemoteAddrFromForwardedFor middleware
+---
  Reporter:  Simon Willison | Owner:  gregorth  
Status:  reopened   | Milestone:
 Component:  Core framework |   Version:  SVN   
Resolution: |  Keywords:  middleware
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by JohnMoylan):

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

Comment:

 Hi, I'm using Apache and Django with Squid as a reverse proxy. Squid
 appends it's IP to the "END" of the X_FORWARDED_FOR header. The real ip
 shoudl be the second last in the list.

 EG

 'HTTP_X_FORWARDED_FOR': '10.162.50.55, 213.233.159.69, 89.207.56.145',

 89.207.56.145 is Squid

 In this sort of setup the SetRemoteAddrFromForwardedFor should use that
 second last IP as the real IP

 real_ip = real_ip.split(",")[-2].strip()

 and not the current

 real_ip = real_ip.split(",")[0].strip()

 Having real_ip as the first IP in the list assumes that the client has not
 gone through multiple proxies.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10878: Comments moderation.py docstring error

[Django]

#10878: Comments moderation.py docstring error
--+-
  Reporter:  lucalenardi  | Owner:  ubernostrum
Status:  assigned | Milestone:  1.1
 Component:  django.contrib.comments  |   Version:  1.1-beta-1 
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by Fantomas42):

 Hi,

 I enjoy that you are preparing a big patch.

 Is this patch will includes,
 - translations of the mail_subject, when sending email ?
 - the pre_save_moderation method with the '''request''' in parameters,
 with '''comment_will_be_posted''' signal for exemple ?

 It's just some suggestions that I've made with the usage of the
 moderation.py

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

Re: [Django] #10873: urlize

[Django]

#10873: urlize
--+-
  Reporter:  onno | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.1-beta-1
Resolution:  invalid  |  Keywords:  urlize
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by lukeplant):

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

Comment:

 urlize works exactly as advertised, and URLField does too.

 Strictly speaking, www.example.com is not a URL, it is a domain, so it
 seems reasonable that URLField should either not accept it as a URL or
 convert it so that it is a URL.  urlize is for marking up users' text in
 things like comments, whereas URLField is meant for storing URLs in the
 database, so it makes sense that it should be more fussy and only store
 actual URLs.

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

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

[Django]

#7539: Add ON DELETE and ON UPDATE support to Django
---+
  Reporter:  glassfordm| Owner:  nobody 
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords:  feature
 Stage:  Design decision needed| Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by benjaoming):

 Someone requested a discussion...

 I just had an encounter with this, and what I lacked was *knowing* what's
 going on with regards to cascading deletion, because it's quite dangerous
 (you loose data!!) and steals lots of time. Preventing it is simple,
 though. Overriding the delete() method of a model and calling clear() on
 the related model's foreign keys is simple, and it's a manual
 implementation, that all programmers should be able to understand.

 But I can think of another alternative: If null=True for the foreign key
 in question, why not automatically use SET NULL when the related instance
 is deleted? For me, this is even more "intuitive" than CASCADE. After all,
 null=True is something that the programmer specifies and has to deal with
 anywhere in the implementation, which is also why he doesn't need
 cascading deletion of such a relation.

 Also, if on_delete is possible to set in a key field, it would have to
 comply with the null option.. and together with the "intuition argument"
 that creates a 1:1 correspondence between the two options.

 And then the "logic argument": Django handles its logic in Python code,
 not in the Database, which is kept as a simple storage engine. The
 RESTRICT option is a validation issue, and will probably be handled this
 way in most cases, so having the database enforcing it, would be
 redundant. To enable it on model-level could pave the way for some nice
 new automatic validation in ModelForms, so I think it sounds like a nice
 feature.

 If all this is implemented, I would suggest to remove the null option from
 key fields and have it set according to on_delete.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #3051: django.test.client.Client() does not set HttpResponse context and template properly

[Django]

#3051: django.test.client.Client() does not set HttpResponse context and 
template
properly
+---
  Reporter:  anonymous  | Owner:  adrian
Status:  reopened   | Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by adamtwiss):

  * status:  closed => reopened
  * needs_docs:  0 => 1
  * resolution:  invalid =>

Comment:

 I've just come across this same problem, and spent an hour or so
 scratching my head. .As russellm says it is easy to fix by calling
 django.test.utils.setup_test_environment() first.
 However, this is not really mentioned in the documentation at all. The
 function is mentioned at:
   http://docs.findjango.com/topics/testing.html
 But it isn't in anyway clear that you have to call it for certain things
 to work, and none of the example code calls it.

 Surely -at the very least, the documentation/examples need to make this
 clear.

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

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

[Django]

#7539: Add ON DELETE and ON UPDATE support to Django
---+
  Reporter:  glassfordm| Owner:  nobody 
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords:  feature
 Stage:  Design decision needed| Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by dokterbob):

 Note: the patch I've just uploaded does not propagate the new cascading
 behaviour to the admin. I am not sure whether the 'old version' of this
 patch did but it is something someone needs 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
-~--~~~~--~~--~--~---

Re: [Django] #2983: ImageField not deleing previously attached file when updated

[Django]

#2983: ImageField not deleing previously attached file when updated
---+
  Reporter:  Shimon| Owner:  tbecker   
Status:  closed| Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:  fs-rf-docs
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by anonymous):

 '''It can't be done with FileStorage''' because FileStorage knows nothing
 about context of file creation. It can't decide wether owerwrite the old
 file (if it belongs to the same FileField as the new one), or append "_"
 to it's name (if old file belongs to other record's FileField).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #2983: ImageField not deleing previously attached file when updated

[Django]

#2983: ImageField not deleing previously attached file when updated
---+
  Reporter:  Shimon| Owner:  tbecker   
Status:  closed| Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:  fs-rf-docs
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Comment (by anonymous):

 But why docs are not saying that if you update FileField/ImageField, old
 file remain on filesystem?

 If you don't want to fix it, write an example, how to avoid it, please.
 The exact goal is "let old file be deleted after replacement with new
 one".

 That's obvious behaviour. Your text fields, char fields, etc are replaced
 on model field update. Why FileField behave differently?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10880: Link to 1.0 docs has two trailing slashes

[Django]

#10880: Link to 1.0 docs has two trailing slashes
-+--
 Reporter:  guettli  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Django Web site  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The link on http://docs.djangoproject.com/en/dev/ to "Django 1.0" docs has
 two trailing slashes:
  http://docs.djangoproject.com/en/1.0//

 The link gets resolved (the link is not broken).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #8857: Forms documentation doesn't describe how to handle uploads

[Django]

#8857: Forms documentation doesn't describe how to handle uploads
+---
  Reporter:  kylefox| Owner:  jacob 
 
Status:  assigned   | Milestone:  1.1   
 
 Component:  Documentation  |   Version:  SVN   
 
Resolution: |  Keywords:  docs, forms, files, 
uploads
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Comment (by prairiedogg):

 Added a patch to modelforms docs that changes the link in the "working
 with forms" document in accordance with what kylefox described as the
 "bare minimum" to resolve 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
-~--~~~~--~~--~--~---