date:20090716

Re: [Django] #6548: django behind apache ssl proxy

2009-07-16 Thread Django

#6548: django behind apache ssl proxy
-+--
  Reporter:  laureline.gue...@makina-corpus.org  | Owner:  
nobody
Status:  new | Milestone:   
 
 Component:  HTTP handling   |   Version:  SVN  
 
Resolution:  |  Keywords:   
 
 Stage:  Design decision needed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

 * cc: anb...@gmail.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] #11496: max_value validation is inconsistant

2009-07-16 Thread Django

#11496: max_value validation is inconsistant
+---
 Reporter:  bobbo...@gmail.com  |   Owner:  nobody
   Status:  new |   Milestone:  1.0.3 
Component:  Forms   | Version:  1.0   
 Keywords:  max_value   |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I am attempting to use validation in the following modelform:

 class BatchForm(ModelForm):
 amount =
 forms.DecimalField(max_digits=8,decimal_places=2,max_value=59.99)
 class Meta:
 model = Batch
 exclude = ('submit_date','user')

 Sometimes is_valid() returns true and sometimes it returns false with the
 amount 1212.

 The error returnedis:

 Ensure this value is less than or equal to 59.99.

 Is this a know issue?

 Version Django-1.0.2-final Python 2.5.1 Mac OSX 10.5.7

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

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

2009-07-16 Thread Django

#4992: Alter cache key based on GET parameters
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Cache system|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

 * cc: ta...@taijala.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
-~--~~~~--~~--~--~---

Re: [Django] #11495: Small improvements to django.views.static.serve directory indexes

2009-07-16 Thread Django

#11495: Small improvements to django.views.static.serve directory indexes
-+--
  Reporter:  SmileyChris | Owner:  SmileyChris
Status:  assigned| Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * owner:  nobody => SmileyChris
  * 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
-~--~~~~--~~--~--~---

[Django] #11495: Small improvements to django.views.static.serve directory indexes

2009-07-16 Thread Django

#11495: Small improvements to django.views.static.serve directory indexes
+---
 Reporter:  SmileyChris |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 This patch sorts indexes and shows directories before files.
 It also adds functionality for providing an index prefix so the template
 can show the full indexed path 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
-~--~~~~--~~--~--~---

[Django] #11494: syncdb fails silently to create tables for an app where the app has an import error

2009-07-16 Thread Django

#11494: syncdb fails silently to create tables for an app where the app has an
import error
-+--
 Reporter:  lawgon   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Core framework   | Version:  SVN   
 Keywords:  syncdb   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I am using latest trunk. This is the same behaviour as reported in
 #10706. To replicate create an app, this app should import something that
 is not available, but should not have any syntax error. That is, from the
 shell 'import app' should work and 'from app import *' should raise an
 exception. In these circumstances syncdb will fail silently to create any
 tables for the app.

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

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 20:01:50 -0500 (Thu, 16 Jul 2009)
New Revision: 11259

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/topics/http/urls.txt
Log:
[1.0.X] Fixed #11492 -- Corrected some typos, and added some extra markup for 
the URLs documentation. Thanks to Ramiro Morales for the patch.

Merge of r11258 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,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-10505,10508-10509,10511-10514,10517-10520,10524-10525,10528,10530-10537,10539-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10601,10603-10620,10624-10626,10631,10639-10641,10643,10646,10652-10655,10659-10660,10666-10669,10675,10682-10690,10693,10697-10704,10707,10713-10714,10723,10725,10727,10729,10732,10743-10750,10752-10760,10768,10770,10772,10774,10777,10782,10787,10789,10791,10795,10797,10799,10801,10805,10808,10810,10812,10814,10816,10819,10822,10828,10831,10833,10835,10837,10839,10841,10843,10845,10847,10849,10861,10863,10913-10914,10952,10970-10973,10979,10981,10983,10985,11007,11009,11019,11021-11022,11025-11026,11028,11041,11043-11054,11067-11068,11079,11093-11097,11103,9-11120,11125,11127,11155,11162-11164,11169-11170,11173,11175,11205,11215,11217-11220,11234-11237,11239,11248-11249
   +

[Changeset] r11258 - django/trunk/docs/topics/http

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 19:55:21 -0500 (Thu, 16 Jul 2009)
New Revision: 11258

Modified:
   django/trunk/docs/topics/http/urls.txt
Log:
Fixed #11492 -- Corrected some typos, and added some extra markup for the URLs 
documentation. Thanks to Ramiro Morales for the patch.

Modified: django/trunk/docs/topics/http/urls.txt
===
--- django/trunk/docs/topics/http/urls.txt  2009-07-17 00:15:02 UTC (rev 
11257)
+++ django/trunk/docs/topics/http/urls.txt  2009-07-17 00:55:21 UTC (rev 
11258)
@@ -4,6 +4,8 @@
 URL dispatcher
 ==
 
+.. module:: django.core.urlresolvers
+
 A clean, elegant URL scheme is an important detail in a high-quality Web
 application. Django lets you design URLs however you want, with no framework
 limitations.
@@ -182,11 +184,13 @@
 patterns
 
 
+.. function:: patterns(prefix, pattern_description, ...)
+
 A function that takes a prefix, and an arbitrary number of URL patterns, and
 returns a list of URL patterns in the format Django needs.
 
 The first argument to ``patterns()`` is a string ``prefix``. See
-"The view prefix" below.
+`The view prefix`_ below.
 
 The remaining arguments should be tuples in this format::
 
@@ -222,6 +226,8 @@
 
 .. versionadded:: 1.0
 
+.. function:: url(regex, view, kwargs=None, name=None, prefix='')
+
 You can use the ``url()`` function, instead of a tuple, as an argument to
 ``patterns()``. This is convenient if you want to specify a name without the
 optional extra arguments dictionary. For example::
@@ -244,6 +250,8 @@
 handler404
 --
 
+.. data:: handler404
+
 A string representing the full Python import path to the view that should be
 called if none of the URL patterns match.
 
@@ -253,6 +261,8 @@
 handler500
 --
 
+.. data:: handler500
+
 A string representing the full Python import path to the view that should be
 called in case of server errors. Server errors happen when you have runtime
 errors in view code.
@@ -263,12 +273,14 @@
 include
 ---
 
+.. function:: include()
+
 A function that takes a full Python import path to another URLconf module that
 should be "included" in this place.
 
 .. versionadded:: 1.1
 
-:meth:``include`` also accepts as an argument an iterable that returns URL
+:func:`include` also accepts as an argument an iterable that returns URL
 patterns.
 
 See `Including other URLconfs`_ below.
@@ -421,7 +433,7 @@
 Admin application. The Django Admin is deployed as instances of a
 :class:`AdminSite`; each :class:`AdminSite` instance has an attribute
 ``urls`` that returns the url patterns available to that instance. It is this
-attribute that you ``included()`` into your projects ``urlpatterns`` when you
+attribute that you ``include()`` into your projects ``urlpatterns`` when you
 deploy the admin instance.
 
 .. _`Django Web site`: http://www.djangoproject.com/
@@ -466,15 +478,15 @@
 
 * An **instance namespace**. This identifies a specific instance of an
   application. Instance namespaces should be unique across your entire
-  project. However, and instance namespace can be the same as the
+  project. However, an instance namespace can be the same as the
   application namespace. This is used to specify a default instance of an
   application. For example, the default Django Admin instance has an
   instance namespace of ``admin``.
 
 URL Namespaces can be specified in two ways.
 
-Firstly, you can provide the applicaiton and instance namespace as arguments
-to the ``include()`` when you construct your URL patterns. For example,::
+Firstly, you can provide the application and instance namespace as arguments
+to ``include()`` when you construct your URL patterns. For example,::
 
 (r'^help/', include('apps.help.urls', namespace='foo', app_name='bar')),
 
@@ -494,7 +506,7 @@
 an admin site, plus the name of the admin instance, and the application
 namespace ``admin``.
 
-Once you have defined namespace URLs, you can reverse them. For details on
+Once you have defined namespaced URLs, you can reverse them. For details on
 reversing namespaced urls, see the documentation on :ref:`reversing namespaced
 URLs `.
 
@@ -679,18 +691,18 @@
 
 .. versionadded:: 1.1
 
-Namespaced URLs are specified using the `:` operator. For example, the main 
index
-page of the admin application is referenced using ``admin:index``. This 
indicates
-a namespace of ``admin``, and a named URL of ``index``.
+Namespaced URLs are specified using the ``:`` operator. For example, the main
+index page of the admin application is referenced using ``admin:index``. This
+indicates a namespace of ``admin``, and a named URL of ``index``.
 
 Namespaces can also be nested. The named URL ``foo:bar:whiz`` would look for
 a pattern named ``whiz`` in the namespace ``bar`` that is itself defined within
 the top-level namespace ``foo``.
 
-When given a namespaced URL (e.g.,, `myapp:index`) to resolve, Django splits
+When given

[Changeset] r11257 - in django/branches/soc2009/multidb/django: core/management/commands db db/backends db/models db/models/fields db/models/sql

2009-07-16 Thread noreply


Author: Alex
Date: 2009-07-16 19:15:02 -0500 (Thu, 16 Jul 2009)
New Revision: 11257

Modified:
   
django/branches/soc2009/multidb/django/core/management/commands/createcachetable.py
   django/branches/soc2009/multidb/django/db/backends/creation.py
   django/branches/soc2009/multidb/django/db/models/fields/related.py
   django/branches/soc2009/multidb/django/db/models/query.py
   django/branches/soc2009/multidb/django/db/models/sql/where.py
   django/branches/soc2009/multidb/django/db/utils.py
Log:
[soc2009/multidb] Fixed a bug with EmptyQuerySet.

Modified: 
django/branches/soc2009/multidb/django/core/management/commands/createcachetable.py
===
--- 
django/branches/soc2009/multidb/django/core/management/commands/createcachetable.py
 2009-07-17 00:08:24 UTC (rev 11256)
+++ 
django/branches/soc2009/multidb/django/core/management/commands/createcachetable.py
 2009-07-17 00:15:02 UTC (rev 11257)
@@ -2,6 +2,7 @@
 
 from django.core.management.base import LabelCommand
 from django.db import connections, transaction, models, DEFAULT_DB_ALIAS
+from django.db.utils import call_with_connection
 
 class Command(LabelCommand):
 help = "Creates the table needed to use the SQL cache backend."
@@ -30,7 +31,7 @@
 index_output = []
 qn = connection.ops.quote_name
 for f in fields:
-field_output = [qn(f.name), f.db_type(connection)]
+field_output = [qn(f.name), call_with_connection(f.db_type, 
connection=connection)]
 field_output.append("%sNULL" % (not f.null and "NOT " or ""))
 if f.primary_key:
 field_output.append("PRIMARY KEY")

Modified: django/branches/soc2009/multidb/django/db/backends/creation.py
===
--- django/branches/soc2009/multidb/django/db/backends/creation.py  
2009-07-17 00:08:24 UTC (rev 11256)
+++ django/branches/soc2009/multidb/django/db/backends/creation.py  
2009-07-17 00:15:02 UTC (rev 11257)
@@ -8,6 +8,7 @@
 
 from django.conf import settings
 from django.core.management import call_command
+from django.db.utils import call_with_connection
 
 # The prefix to put on the default database name when creating
 # the test database.
@@ -47,7 +48,7 @@
 pending_references = {}
 qn = self.connection.ops.quote_name
 for f in opts.local_fields:
-col_type = f.db_type(self.connection)
+col_type = call_with_connection(f.db_type, 
connection=self.connection)
 tablespace = f.db_tablespace or opts.db_tablespace
 if col_type is None:
 # Skip ManyToManyFields, because they're not represented as

Modified: django/branches/soc2009/multidb/django/db/models/fields/related.py
===
--- django/branches/soc2009/multidb/django/db/models/fields/related.py  
2009-07-17 00:08:24 UTC (rev 11256)
+++ django/branches/soc2009/multidb/django/db/models/fields/related.py  
2009-07-17 00:15:02 UTC (rev 11257)
@@ -5,6 +5,7 @@
 from django.db.models.related import RelatedObject
 from django.db.models.query import QuerySet
 from django.db.models.query_utils import QueryWrapper
+from django.db.utils import call_with_connection
 from django.utils.encoding import smart_unicode
 from django.utils.translation import ugettext_lazy, string_concat, ungettext, 
ugettext as _
 from django.utils.functional import curry
@@ -772,7 +773,7 @@
 isinstance(rel_field, (PositiveIntegerField,
PositiveSmallIntegerField:
 return IntegerField().db_type(connection)
-return rel_field.db_type(connection)
+return call_with_connection(rel_field.db_type, connection=connection)
 
 class OneToOneField(ForeignKey):
 """

Modified: django/branches/soc2009/multidb/django/db/models/query.py
===
--- django/branches/soc2009/multidb/django/db/models/query.py   2009-07-17 
00:08:24 UTC (rev 11256)
+++ django/branches/soc2009/multidb/django/db/models/query.py   2009-07-17 
00:15:02 UTC (rev 11257)
@@ -33,7 +33,12 @@
 """
 def __init__(self, model=None, query=None):
 self.model = model
-using = model._meta.using or DEFAULT_DB_ALIAS
+# EmptyQuerySet instantiates QuerySet with model as None
+if model:
+using = model._meta.using
+else:
+using = None
+using = using or DEFAULT_DB_ALIAS
 connection = connections[using]
 self.query = query or sql.Query(self.model, connection)
 self._result_cache = None

Modified: django/branches/soc2009/multidb/django/db/models/sql/where.py
===
--- django/branches/soc2009/multidb/django/db/models/sql/where.py   
2009-07-17 00:08:24 UTC (rev 11256)
+++

Re: [Django] #7376: auth docs don't say they depend on contenttypes

2009-07-16 Thread Django

#7376: auth docs don't say they depend on contenttypes
+---
  Reporter:  kcarnold   | Owner:  nobody
Status:  new| Milestone:
 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 timo):

  * 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] #11359: "Built-in signals" API reference doc fails to mention "Signals" documentation.

2009-07-16 Thread Django

#11359: "Built-in signals" API reference doc fails to mention "Signals"
documentation.
+---
  Reporter:  tyson  | Owner:  nobody   
Status:  new| Milestone:   
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:  signals documentation
 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
-~--~~~~--~~--~--~---

[Changeset] r11255 - in django/branches/releases/1.0.X: . docs/howto/deployment

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 18:54:04 -0500 (Thu, 16 Jul 2009)
New Revision: 11255

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/howto/deployment/modwsgi.txt
Log:
[1.0.X] Fixed #11229 -- Updated the mod_wsgi deployment documentation to avoid 
references to mod_python and techniques that are not recommended or required 
for mod_wsgi. Thanks to Graham Dumpleton for the suggestion and guidance.

Merge of r11249 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,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-10505,10508-10509,10511-10514,10517-10520,10524-10525,10528,10530-10537,10539-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10601,10603-10620,10624-10626,10631,10639-10641,10643,10646,10652-10655,10659-10660,10666-10669,10675,10682-10690,10693,10697-10704,10707,10713-10714,10723,10725,10727,10729,10732,10743-10750,10752-10760,10768,10770,10772,10774,10777,10782,10787,10789,10791,10795,10797,10799,10801,10805,10808,10810,10812,10814,10816,10819,10822,10828,10831,10833,10835,10837,10839,10841,10843,10845,10847,10849,10861,10863,10913-10914,10952,10970-10973,10979,10981,10983,10985,11007,11009,11019,11021-11022,11025-11026,11028,11041,11043-11054,11067-11068,11079,11093-11097,11103,9-11120,11125,11127,11155,11162-11164,11169-11170,11173,11175,11205,11215,11217-11220,11234-11237,11239,11248
   +

[Changeset] r11254 - in django/branches/releases/1.0.X: . docs/topics

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 18:49:27 -0500 (Thu, 16 Jul 2009)
New Revision: 11254

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/topics/testing.txt
Log:
[1.0.X] Fixed #10908 -- Clarified the procedure for creating test users in the 
testing docs. Thanks to gruszczy and timo.

Merge of r11248 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,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-10505,10508-10509,10511-10514,10517-10520,10524-10525,10528,10530-10537,10539-10548,10550-10557,10561,10563-10564,10567-10571,10573-10574,10576-10578,10580-10589,10591-10592,10595-10596,10599-10601,10603-10620,10624-10626,10631,10639-10641,10643,10646,10652-10655,10659-10660,10666-10669,10675,10682-10690,10693,10697-10704,10707,10713-10714,10723,10725,10727,10729,10732,10743-10750,10752-10760,10768,10770,10772,10774,10777,10782,10787,10789,10791,10795,10797,10799,10801,10805,10808,10810,10812,10814,10816,10819,10822,10828,10831,10833,10835,10837,10839,10841,10843,10845,10847,10849,10861,10863,10913-10914,10952,10970-10973,10979,10981,10983,10985,11007,11009,11019,11021-11022,11025-11026,11028,11041,11043-11054,11067-11068,11079,11093-11097,11103,9-11120,11125,11127,11155,11162-11164,11169-11170,11173,11175,11205,11215,11217-11220,11234-11237,11239
   +

[Changeset] r11253 - django/trunk/docs/topics/http

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 18:45:36 -0500 (Thu, 16 Jul 2009)
New Revision: 11253

Modified:
   django/trunk/docs/topics/http/urls.txt
Log:
Fixed #11491 -- Corrected minor typo in new namespace URL docs. Thanks to Carl 
Meyer for the report.

Modified: django/trunk/docs/topics/http/urls.txt
===
--- django/trunk/docs/topics/http/urls.txt  2009-07-16 23:13:49 UTC (rev 
11252)
+++ django/trunk/docs/topics/http/urls.txt  2009-07-16 23:45:36 UTC (rev 
11253)
@@ -451,8 +451,8 @@
 Defining URL Namespaces
 ---
 
-When you need to deploying multiple instances of a single application, it can
-be helpful to be able to differentiate between instances. This is especially
+When you need to deploy multiple instances of a single application, it can be
+helpful to be able to differentiate between instances. This is especially
 important when using _`named URL patterns `, since
 multiple instances of a single application will share named URLs. Namespaces
 provide a way to tell these named URLs apart.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #9236: django.contrib.admin documentation -- missing dependency info?

2009-07-16 Thread Django

#9236: django.contrib.admin documentation -- missing dependency info?
+---
  Reporter:  cjlesh | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * version:  1.0 => SVN
  * 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] #11493: Document the timeline of Django deprecations

2009-07-16 Thread Django

#11493: Document the timeline of Django deprecations
+---
  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 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] #11493: Document the timeline of Django deprecations

2009-07-16 Thread Django

#11493: Document the timeline of Django deprecations
---+
 Reporter:  Alex   |   Owner:  nobody
   Status:  new|   Milestone:  1.1   
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  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] #7437: SelectDateWidget is not documented

2009-07-16 Thread Django

#7437: SelectDateWidget is not documented
+---
  Reporter:  Beetle_B   | Owner:  nobody
Status:  reopened   | Milestone:
 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 timo):

  * 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] #6047: db-api docs: invalid REGEX SQL equiv for SQLite

2009-07-16 Thread Django

#6047: db-api docs: invalid REGEX SQL equiv for SQLite
---+
  Reporter:  Richard D. Worth   | Owner:  
holdenweb
Status:  assigned  | Milestone: 
  
 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 timo):

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

2009-07-16 Thread 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   |  
-+--
Comment (by lukeplant):

 You're right, _make_token no longer servers a purpose.  I just didn't get
 round to changing 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] #6674: Missing widget documentation

2009-07-16 Thread Django

#6674: Missing widget documentation
+---
  Reporter:  Karen Tracey   | Owner:  
holdenweb
Status:  new| Milestone:
   
 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 timo):

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

[Changeset] r11251 - in django/trunk/django/contrib/gis: db/models/sql tests/relatedapp

2009-07-16 Thread noreply


Author: jbronn
Date: 2009-07-16 17:38:22 -0500 (Thu, 16 Jul 2009)
New Revision: 11251

Modified:
   django/trunk/django/contrib/gis/db/models/sql/query.py
   django/trunk/django/contrib/gis/tests/relatedapp/tests.py
Log:
Fixed #11489 -- `GeoQuery.resolve_columns` now recognizes annotations; disabled 
problematic test cases on Oracle and added notes on why.


Modified: django/trunk/django/contrib/gis/db/models/sql/query.py
===
--- django/trunk/django/contrib/gis/db/models/sql/query.py  2009-07-16 
16:16:13 UTC (rev 11250)
+++ django/trunk/django/contrib/gis/db/models/sql/query.py  2009-07-16 
22:38:22 UTC (rev 11251)
@@ -13,7 +13,9 @@
 ALL_TERMS = sql.constants.QUERY_TERMS.copy()
 ALL_TERMS.update(SpatialBackend.gis_terms)
 
+# Pulling out other needed constants/routines to avoid attribute lookups.
 TABLE_NAME = sql.constants.TABLE_NAME
+get_proxied_model = sql.query.get_proxied_model
 
 class GeoQuery(sql.Query):
 """
@@ -153,7 +155,9 @@
 opts = self.model._meta
 aliases = set()
 only_load = self.deferred_to_columns()
-proxied_model = opts.proxy and opts.proxy_for_model or 0
+# Skip all proxy to the root proxied model
+proxied_model = get_proxied_model(opts)
+
 if start_alias:
 seen = {None: start_alias}
 for field, model in opts.get_fields_with_model():
@@ -205,6 +209,10 @@
 """
 values = []
 aliases = self.extra_select.keys()
+if self.aggregates:
+# If we have an aggregate annotation, must extend the aliases
+# so their corresponding row values are included.
+aliases.extend([None for i in xrange(len(self.aggregates))])
 
 # Have to set a starting row number offset that is used for
 # determining the correct starting row index -- needed for

Modified: django/trunk/django/contrib/gis/tests/relatedapp/tests.py
===
--- django/trunk/django/contrib/gis/tests/relatedapp/tests.py   2009-07-16 
16:16:13 UTC (rev 11250)
+++ django/trunk/django/contrib/gis/tests/relatedapp/tests.py   2009-07-16 
22:38:22 UTC (rev 11251)
@@ -231,8 +231,12 @@
 q = pickle.loads(q_str)
 self.assertEqual(GeoQuery, q.__class__)
 
-def test12_count(self):
-"Testing `Count` aggregate use with the `GeoManager`. See #11087."
+# TODO: fix on Oracle -- get the following error because the SQL is ordered
+# by a geometry object, which Oracle apparently doesn't like:
+#  ORA-22901: cannot compare nested table or VARRAY or LOB attributes of 
an object type
+@no_oracle
+def test12a_count(self):
+"Testing `Count` aggregate use with the `GeoManager` on geo-fields."
 # Creating a new City, 'Fort Worth', that uses the same location
 # as Dallas.
 dallas = City.objects.get(name='Dallas')
@@ -242,6 +246,8 @@
 loc = 
Location.objects.annotate(num_cities=Count('city')).get(id=dallas.location.id)
 self.assertEqual(2, loc.num_cities)
 
+def test12b_count(self):
+"Testing `Count` aggregate use with the `GeoManager` on non 
geo-fields. See #11087."
 # Creating some data for the Book/Author non-geo models that
 # use GeoManager.  See #11087.
 tp = Author.objects.create(name='Trevor Paglen')
@@ -250,13 +256,19 @@
 Book.objects.create(title='Blank Spots on the Map', author=tp)
 wp = Author.objects.create(name='William Patry')
 Book.objects.create(title='Patry on Copyright', author=wp)
-
+
 # Should only be one author (Trevor Paglen) returned by this query, and
-# the annotation should have 3 for the number of books.
+# the annotation should have 3 for the number of books.  Also testing
+# with a `GeoValuesQuerySet` (see #11489).
 qs = 
Author.objects.annotate(num_books=Count('books')).filter(num_books__gt=1)
+vqs = 
Author.objects.values('name').annotate(num_books=Count('books')).filter(num_books__gt=1)
 self.assertEqual(1, len(qs))
 self.assertEqual(3, qs[0].num_books)
+self.assertEqual(1, len(vqs))
+self.assertEqual(3, vqs[0]['num_books'])
 
+# TODO: The phantom model does appear on Oracle.
+@no_oracle
 def test13_select_related_null_fk(self):
 "Testing `select_related` on a nullable ForeignKey via `GeoManager`. 
See #11381."
 no_author = Book.objects.create(title='Without Author')


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

2009-07-16 Thread 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   |  
-+--
Comment (by Glenn):

 Refresh my memory: what's the point of _make_token() again?  Why isn't the
 CSRF cookie equal to the CSRF token?

 I need this to fill in the CSRF form field from another part of a site I'm
 developing; it's written in PHP, so it doesn't have access to the Python
 helpers.  I could copy over the secret key and hash it myself, but I can't
 remember any purpose to this hashing.

 I specifically remember discussing the advantages: so your own JS can add
 the CSRF token for generated forms, which is just another form of what I'm
 doing.  I can't remember why we didn't do it--my guess is we just forgot.
 I've made this change locally and it's working well.

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

Re: [Django] #11487: Oracle encoding bug when saving more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle encoding bug when saving more than 4000 characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 I belive it should say "as _a_ CLOB" (just a grammar nitpick ;))

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

2009-07-16 Thread Django

#11492: Some typos fixes for the docs added in r11250
---+
 Reporter:  ramiro |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  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] #11488: ValueError: too many values to unpack when POSTGIS_VERSION in settings

2009-07-16 Thread Django

#11488: ValueError: too many values to unpack when POSTGIS_VERSION in settings
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  GIS |   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jbronn):

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

Comment:

 Docs have been updated to reflect the proper usage.

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

2009-07-16 Thread Django

#10060: Multiple table annotation failure
--+-
  Reporter:  svsha...@intellecap.net  | Owner: 
Status:  new  | Milestone: 
 Component:  ORM aggregation  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by bendavis78):

 I also agree that this should be documented, but perhaps an exception
 should be raise when attempting to do multiple annotations on different
 tables/joins?  I can't think of a situation where that would ever
 guarantee accurate results.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle encoding bug when saving more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle encoding bug when saving more than 4000 characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 Replying to [comment:6 Alex]:
 > Please upload the diffs from the root of the source tree, not just for
 the single file.  Also there's no need to keep uploading the source file,
 just the diff is enough.
 Sorry Alex, I'm still adjusting to the process of submission of patches

 I believe that now the file is ok:
 [http://code.djangoproject.com/attachment/ticket/11487/base.3.diff
 base.3.diff]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle encoding bug when saving more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle encoding bug when saving more than 4000 characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 Please upload the diffs from the root of the source tree, not just for the
 single file.  Also there's no need to keep uploading the source file, just
 the diff is enough.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle encoding bug when saving more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle encoding bug when saving more than 4000 characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 Using CLOB also works perfectly! I've added the file with the diff
 ([http://code.djangoproject.com/attachment/ticket/11487/base.2.diff
 base.2.diff]) and source code
 ([http://code.djangoproject.com/attachment/ticket/11487/base.2.py
 base.2.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] #11487: Oracle encoding bug when saving more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle encoding bug when saving more than 4000 characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

  * summary:  Oracle does not register in the batabase items with more than
  4000 characters => Oracle encoding bug when
  saving more than 4000 characters
  * version:  1.0 => SVN
  * stage:  Unreviewed => Accepted

Comment:

 Glad you were able to get this working.  Would you mind testing out for me
 the same change but using Database.CLOB rather than Database.LONG_STRING?
 The reason is I'm concerned that LONG_STRING might cause problems in other
 configurations.  Also, the patch in #10566 already changes it from NCLOB
 to CLOB, so I'd prefer a solution that both tickets can agree on.

 Also, since I can't reproduce this myself, would you please write up a
 test case for this?  It doesn't need to be complicated.  Just inserting a
 large string, reading it back, and checking that it's the same would be
 fine.  The main thing is we need to be sure the string used will actually
 trigger the bug.

 Thanks!

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

Re: [Django] #11489: annotate fails when values is used via a GeoManager

2009-07-16 Thread Django

#11489: annotate fails when values is used via a GeoManager
-+--
  Reporter:  jamesturk   | Owner:  jamesturk
Status:  assigned| Milestone:  1.2  
 Component:  GIS |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  1
Needs_better_patch:  0   |  
-+--
Changes (by jamesturk):

  * has_patch:  0 => 1
  * 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] #11489: annotate fails when values is used via a GeoManager

2009-07-16 Thread Django

#11489: annotate fails when values is used via a GeoManager
-+--
  Reporter:  jamesturk   | Owner:  jamesturk
Status:  assigned| Milestone:  1.2  
 Component:  GIS |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by jamesturk):

  * owner:  nobody => jamesturk
  * status:  new => assigned

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11320: Over aggressive join promotion with exclude()

2009-07-16 Thread Django

#11320: Over aggressive join promotion with exclude()
---+
  Reporter:  Alex  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * 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] #2306: Many-to-many queries very slow on MySQL 3.23.58

2009-07-16 Thread Django

#2306: Many-to-many queries very slow on MySQL 3.23.58
---+
  Reporter:  anonymous | Owner:  nobody 
Status:  closed| Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:  fixed |  Keywords:  qs-rf-fixed
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by magmax):

 Replying to [comment:14 pjorstad]:
 > [http://dietrinepills.info/acheter-du-levitra.html levitra prix]
 This was really helpful! Thanks for sharing this.
 [http://www.bodybuildingweb.net/supplements/ discount bodybuilding
 supplements]
 Really interesting. I have read a lot about this on other articles written
 by other people, but I must admit that you is the best.
 [http://4hemorrhoids.info/vente-de-precose.html cailis] and
 [http://cailis.biz/ precose 25 mg]

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

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

2009-07-16 Thread Django

#9025: Nested Inline Support in Admin
-+--
  Reporter:  pixelcort   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  1   |  
-+--
Changes (by kilpatds):

 * cc: kilpa...@oppositelock.org (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] #11491: minor typo in docs for r11250

2009-07-16 Thread Django

#11491: minor typo in docs for r11250
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:
 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):

  * 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] #11491: minor typo in docs for r11250

2009-07-16 Thread Django

#11491: minor typo in docs for r11250
---+
 Reporter:  carljm |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 See attached patch - just a typo.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle does not register in the batabase items with more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle does not register in the batabase items with more than 4000
characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

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

Re: [Django] #11489: annotate fails when values is used via a GeoManager

2009-07-16 Thread Django

#11489: annotate fails when values is used via a GeoManager
-+--
  Reporter:  jamesturk   | Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  GIS |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * milestone:  1.1 => 1.2

Comment:

 Not a blocker for 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
-~--~~~~--~~--~--~---

Re: [Django] #11488: ValueError: too many values to unpack when POSTGIS_VERSION in settings

2009-07-16 Thread Django

#11488: ValueError: too many values to unpack when POSTGIS_VERSION in settings
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  new | Milestone:
 Component:  GIS |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

Comment:

 Not a blocker for 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
-~--~~~~--~~--~--~---

Re: [Django] #8774: ImageField errors in admin inline editing

2009-07-16 Thread Django

#8774: ImageField errors in admin inline editing
---+
  Reporter:  ramin | Owner:  nobody 

Status:  closed| Milestone:  1.0

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:  invalid   |  Keywords:  imagefield admin 
inline
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 The admin should not (and in fact, cannot) handle non-unicode objects
 returned by a model's `__unicode__` method.  A `__unicode__` method should
 return a unicode object.  If it does not, Python will attempt to coerce
 the returned value to unicode.  If Python cannot do this conversion, it
 generates the exception, which is pretty clear:

 {{{
 coercing to Unicode: need string or buffer, ImageFieldFile found
 }}}

 Here, instead of returning unicode, a `__unicode__` method returned an
 !ImageFieldFile, and Python cannot coerce that to unicode.  The only
 possible fix is to make the `__unicode__` method return unicode or
 something coercable to unicode.

 There is nothing Django-specific about the requirements for `__unicode__`.
 This is a Python-defined function:

 
http://docs.python.org/reference/datamodel.html?highlight=__unicode__#object.__unicode__

 Django's doc discusses element of `__unicode__` implementation specific to
 Django, I don't believe it ought to reiterate the basic Python
 requirements for the function.  It certainly should not attempt to list
 all the things that a `__unicode__` function should not return, as that
 list would be infinitely large.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle does not register in the batabase items with more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle does not register in the batabase items with more than 4000
characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * milestone:  1.1 =>

Comment:

 Please upload a proper patch; finding the change by eye can be tricky. If
 you need help, check out the
 [http://docs.djangoproject.com/en/dev/internals/contributing/#patch-style
 contributor's guide] or ask someone in IRC. Thanks!

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

Re: [Django] #11229: The mod_wsgi documentation about hosting of static files wrongly refers to mod_python documentation.

2009-07-16 Thread Django

#11229: The mod_wsgi documentation about hosting of static files wrongly refers 
to
mod_python documentation.
+---
  Reporter:  grahamd| Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  fixed  |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 (In [11249]) Fixed #11229 -- Updated the mod_wsgi deployment documentation
 to avoid references to mod_python and techniques that are not recommended
 or required for mod_wsgi. Thanks to Graham Dumpleton for the suggestion
 and guidance.

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

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 11:08:18 -0500 (Thu, 16 Jul 2009)
New Revision: 11249

Modified:
   django/trunk/docs/howto/deployment/modwsgi.txt
Log:
Fixed #11229 -- Updated the mod_wsgi deployment documentation to avoid 
references to mod_python and techniques that are not recommended or required 
for mod_wsgi. Thanks to Graham Dumpleton for the suggestion and guidance.

Modified: django/trunk/docs/howto/deployment/modwsgi.txt
===
--- django/trunk/docs/howto/deployment/modwsgi.txt  2009-07-16 16:06:53 UTC 
(rev 11248)
+++ django/trunk/docs/howto/deployment/modwsgi.txt  2009-07-16 16:08:18 UTC 
(rev 11249)
@@ -1,69 +1,118 @@
-.. _howto-deployment-modwsgi:
-
-==
-How to use Django with Apache and mod_wsgi
-==
-
-Deploying Django with Apache_ and `mod_wsgi`_ is the recommended way to get
-Django into production.
-
-.. _Apache: http://httpd.apache.org/
-.. _mod_wsgi: http://code.google.com/p/modwsgi/
-
-mod_wsgi is an Apache module which can be used to host any Python application
-which supports the `Python WSGI interface`_, including Django. Django will work
-with any version of Apache which supports mod_wsgi.
-
-.. _python wsgi interface: http://www.python.org/dev/peps/pep-0333/
-
-The `official mod_wsgi documentation`_ is fantastic; it's your source for all
-the details about how to use mod_wsgi. You'll probably want to start with the
-`installation and configuration documentation`_.
-
-.. _official mod_wsgi documentation: http://code.google.com/p/modwsgi/
-.. _installation and configuration documentation: 
http://code.google.com/p/modwsgi/wiki/InstallationInstructions
-
-Basic Configuration
-===
-
-Once you've got mod_wsgi installed and activated, edit your ``httpd.conf`` file
-and add::
-
-WSGIScriptAlias / /path/to/mysite/apache/django.wsgi
-
-The first bit above is the url you want to be serving your application at 
(``/``
-indicates the root url), and the second is the location of a "WSGI file" -- see
-below -- on your system, usually inside of your project. This tells Apache
-to serve any request below the given URL using the WSGI application defined by 
that file.
-
-Next we'll need to actually create this WSGI application, so create the file
-mentioned in the second part of ``WSGIScriptAlias`` and add::
-
-import os
-import sys
-
-os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings'
-
-import django.core.handlers.wsgi
-application = django.core.handlers.wsgi.WSGIHandler()
-
-If your project is not on your ``PYTHONPATH`` by default you can add::
-
-sys.path.append('/usr/local/django')
-
-just above the final ``import`` line to place your project on the path. 
Remember to
-replace 'mysite.settings' with your correct settings file, and 
'/usr/local/django'
-with your own project's location.
-
-See the :ref:`Apache/mod_python documentation` for 
-directions on serving static media, and the `mod_wsgi documentation`_ for an 
-explanation of other directives and configuration options you can use.
-
-Details
-===
-
-For more details, see the `mod_wsgi documentation`_, which explains the above 
in
-more detail, and walks through all the various options you've got when 
deploying
-under mod_wsgi.
-
-.. _mod_wsgi documentation: 
http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango
+.. _howto-deployment-modwsgi:
+
+==
+How to use Django with Apache and mod_wsgi
+==
+
+Deploying Django with Apache_ and `mod_wsgi`_ is the recommended way to get
+Django into production.
+
+.. _Apache: http://httpd.apache.org/
+.. _mod_wsgi: http://code.google.com/p/modwsgi/
+
+mod_wsgi is an Apache module which can be used to host any Python application
+which supports the `Python WSGI interface`_, including Django. Django will work
+with any version of Apache which supports mod_wsgi.
+
+.. _python wsgi interface: http://www.python.org/dev/peps/pep-0333/
+
+The `official mod_wsgi documentation`_ is fantastic; it's your source for all
+the details about how to use mod_wsgi. You'll probably want to start with the
+`installation and configuration documentation`_.
+
+.. _official mod_wsgi documentation: http://code.google.com/p/modwsgi/
+.. _installation and configuration documentation: 
http://code.google.com/p/modwsgi/wiki/InstallationInstructions
+
+Basic Configuration
+===
+
+Once you've got mod_wsgi installed and activated, edit your ``httpd.conf`` file
+and add::
+
+WSGIScriptAlias / /path/to/mysite/apache/django.wsgi
+
+The first bit above is the url you want to be serving your application at 
(``/``
+indicates the root url), and the second is the location of a "WSGI file" -- see
+below -- on your system, usually inside of your project. This tells Apache
+to serve any request below the given URL using the WSGI

[Changeset] r11248 - django/trunk/docs/topics

2009-07-16 Thread noreply


Author: russellm
Date: 2009-07-16 11:06:53 -0500 (Thu, 16 Jul 2009)
New Revision: 11248

Modified:
   django/trunk/docs/topics/testing.txt
Log:
Fixed #10908 -- Clarified the procedure for creating test users in the testing 
docs. Thanks to gruszczy and timo.

Modified: django/trunk/docs/topics/testing.txt
===
--- django/trunk/docs/topics/testing.txt2009-07-16 03:02:08 UTC (rev 
11247)
+++ django/trunk/docs/topics/testing.txt2009-07-16 16:06:53 UTC (rev 
11248)
@@ -686,7 +686,13 @@
 user accounts that are valid on your production site will not work
 under test conditions. You'll need to create users as part of the test
 suite -- either manually (using the Django model API) or with a test
-fixture.
+fixture. Remember that if you want your test user to have a password,
+you can't set the user's password by setting the password attribute
+directly -- you must use the
+:meth:`~django.contrib.auth.models.User.set_password()` function to
+store a correctly hashed password. Alternatively, you can use the
+:meth:`~django.contrib.auth.models.UserManager.create_user` helper
+method to create a new user with a correctly hashed password.
 
 .. method:: Client.logout()
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11490: Editing a model that contains m2m inline hangs the server

2009-07-16 Thread Django

#11490: Editing a model that contains m2m inline hangs the server
--+-
 Reporter:  v.kryac...@gmail.com  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:  inlines   |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The code first:[[BR]]
 {{{
 #models.py
 class Obj(models.Model):
 name = models.CharField(max_length=100)

 class ObjConf(models.Model):
 obj = models.ForeignKey(Obj, unique=True)

 someStuff = models.ManyToManyField('someStuff')

 class someStuff(models.Model):
 name = models.CharField(max_length=100)

 #admin.py
 class ObjConfInline(admin.TabularInline):
 model = ObjConf

 class ObjAdmin(admin.ModelAdmin):
 inlines = [ObjConfInline,]

 admin.site.register(Obj, ObjAdmin)
 }}}

 When I create a new instance of Obj, everything is OK. But when trying to
 /admin/project/app_name/Obj/1 the server starts thinking forever and never
 responds(only Ctrl+C works)

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

2009-07-16 Thread Django

#8774: ImageField errors in admin inline editing
---+
  Reporter:  ramin | Owner:  nobody 

Status:  reopened  | Milestone:  1.0

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  imagefield admin 
inline
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 Here is the problem.  In the Page model, the __unicode__ function returns
 an image object:

 def __unicode__(self):
 return self.image

 Either the admin templates should handle non-unicode objects or there
 should be a note at
 
http://docs.djangoproject.com/en/dev/ref/models/instances/#django.db.models.Model.__unicode__
 about not using FileField objects that may be referenced as part of a
 ForeignKey?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11489: annotate fails when values is used via a GeoManager

2009-07-16 Thread Django

#11489: annotate fails when values is used via a GeoManager
-+--
  Reporter:  jamesturk   | Owner:  nobody
Status:  new | Milestone:  1.1   
 Component:  GIS |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jamesturk):

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

[Django] #11489: annotate fails when values is used via a GeoManager

2009-07-16 Thread Django

#11489: annotate fails when values is used via a GeoManager
---+
 Reporter:  jamesturk  |   Owner:  nobody
   Status:  new|   Milestone:  1.1   
Component:  GIS| Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Attempting to do a query like
 Profile.objects.values('role').annotate(num=Count('id')) does not add a
 'num' attribute despite generating seemingly correct SQL.

 This was tested against r11247 with PostGIS

 {{{
 from django.conf import settings
 from django.db.models import Manager
 from django.contrib.auth.models import User
 from django.contrib.gis.db import models
 from django.contrib.gis.geos import Point

 class Profile(models.Model):
 user = models.OneToOneField(User, related_name='profile')
 role = models.CharField(max_length=5, choices=ROLES, default='other')
 # ... extra fields removed ...

 objects = models.GeoManager()
 non_geo_manager = Manager()

 >>> Profile.objects.values('role').annotate(num=Count('id'))._as_sql()
 ('SELECT U0."role", COUNT(U0."id") AS num FROM "people_profile" U0 GROUP
 BY U0."role"', ())
 >>> Profile.objects.values('role').annotate(num=Count('id'))
 [{'role': u'other'}, {'role': u'dev'}]
 # notice that 'num' was not added

 >>>
 Profile.non_geo_manager.values('role').annotate(num=Count('id'))._as_sql()
 ('SELECT U0."role", COUNT(U0."id") AS "num" FROM "people_profile" U0 GROUP
 BY U0."role"', ())
 >>> Profile.non_geo_manager.values('role').annotate(num=Count('id'))
 [{'num': 19, 'role': u'other'}, {'num': 1, 'role': u'dev'}]
 # num is added as expected

 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11488: ValueError: too many values to unpack when POSTGIS_VERSION in settings

2009-07-16 Thread Django

#11488: ValueError: too many values to unpack when POSTGIS_VERSION in settings
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:  1.1   
Component:  GIS| Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 On syncdb with contrib.gis installed and POSTGIS_VERSION in settings, i
 get a `ValueError: too many values to unpack`

 {{{
 File "C:\Python25\lib\site-
 packages\django\contrib\gis\db\backend\postgis\query.py", line 28, in
 
  POSTGIS_VERSION, MAJOR_VERSION, MINOR_VERSION1, MINOR_VERSION2 =
 version_tuple
 }}}

 in settings:
 {{{
 POSTGIS_VERSION='1.3.6'
 }}}

 When i remove that setting, syncdb works.

 It appears in
 
http://code.djangoproject.com/browser/django/trunk/django/contrib/gis/db/backend/postgis/query.py
 that when POSTGIS_VERSION is not in the settings, postgis_version_tuple()
 returns a tuple in this format: ('1.3.6',1,3,6) whereas the GIS docs
 (http://geodjango.org/docs/testing.html#postgis-version) say to set
 POSTGIS_VERSION in the format i used.  When POSTGIS_VERSION is returned,
 the tuple only has one element, not the four required.

 i noted that the code says "This setting is intentionally undocumented" so
 i don't know what course of action is appropriate.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle does not register in the batabase items with more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle does not register in the batabase items with more than 4000
characters
---+
  Reporter:  mdpetry   | Owner:  nobody 

Status:  new   | Milestone:  1.1

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

Resolution:|  Keywords:  oracle 
database
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 I simply changed the line 364 by placing the following contents:
 {{{self.input_size = Database.LONG_STRING}}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #11487: Oracle does not register in the batabase items with more than 4000 characters

2009-07-16 Thread Django

#11487: Oracle does not register in the batabase items with more than 4000
characters
--+-
 Reporter:  mdpetry   |   Owner:  nobody
   Status:  new   |   Milestone:  1.1   
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  oracle database   |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 I am working on a project where I have to store a large amount of
 content, (html) in a record from a table, I am using Oracle as the
 database

 What is very strange ... is put a text reasonably small, (around 3000
 characters) and it works correctly, save without problems, but
 doubling this size, this content is saved completely changed.

 This patch works well on: Django 1.1 (svn), debian, and Oracle 10g
 with cx_oracle 4.4.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] #8774: ImageField errors in admin inline editing

2009-07-16 Thread Django

#8774: ImageField errors in admin inline editing
---+
  Reporter:  ramin | Owner:  nobody 

Status:  reopened  | Milestone:  1.0

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  imagefield admin 
inline
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 When removing page.Page.image field from the models, this works fine.  It
 looks that the Django admin doesn't like a ForeignKey going to a model
 with an ImageField?

 Two caveats here are that there were no ImageField entries populated in
 the Page model and I'm using django-storages (specifically s3boto.py) as a
 file storage backend.

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

2009-07-16 Thread Django

#8774: ImageField errors in admin inline editing
---+
  Reporter:  ramin | Owner:  nobody 

Status:  reopened  | Milestone:  1.0

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  imagefield admin 
inline
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

  * status:  closed => reopened
  * resolution:  worksforme =>
  * component:  Template system => django.contrib.admin

Comment:

 I'm seeing this issue in Django 1.0.2 when trying to add a first record to
 the Score model through the standard admin interface.  field.field in the
 template is trying to render the ImageField because of a foreign key
 relationship I think.  Here are the relevant models:


 {{{
 from django.db import models
 from page.models import Page
 from phrase.models import Phrase



 class ScoreType(models.Model):
 """
 Types of score weights
 """
 #affiliate
 name = models.CharField(max_length=50,unique=True)
 description = models.CharField(max_length=255)
 weight = models.FloatField()

 def __unicode__(self):
 return self.name


 class Score(models.Model):
 """
 Score page
 """
 score = models.FloatField()
 #flag tinyint(1) unsigned DEFAULT NULL
 #status varchar(30)  DEFAULT 'pending'
 #review varchar(30)  DEFAULT 'not reviewed'
 date = models.DateTimeField(auto_now_add=True)
 type = models.ForeignKey(ScoreType)
 page = models.ForeignKey(Page)

 class Meta:
 unique_together = ('page','type')

 def __unicode__(self):
 return self.score

 class ScoreDetail(models.Model):
 """
 Detail page processed by Transparency
 """
 #line_number int(11) DEFAULT NULL
 #line_source text
 date = models.DateTimeField(auto_now_add=True)
 phrase = models.ForeignKey(Phrase)
 score = models.ForeignKey(Score)

 def __unicode__(self):
 return u'%s on %s' % (self.phrase, self.date)

 from django.db import models
 from company.models import Company
 from campaign.models import Campaign
 from log.models import Batch,Message

 # For handling html content as a file
 from django.core.files.storage import default_storage as s3_storage
 from django.core.files.base import ContentFile
 from django.core.cache import cache


 # Create your models here.
 class Page(models.Model):
 """
 Page process by Transparency
 """
 sub_id_1 = models.CharField(max_length=255,blank=True)
 sub_id_2 = models.CharField(max_length=255,blank=True)
 sub_id_3 = models.CharField(max_length=255,blank=True)
 sub_id_4 = models.CharField(max_length=255,blank=True)
 image =
 models.ImageField(upload_to='performline_page_image',blank=True)
 image_url = models.URLField(verify_exists=False)
 content =
 models.FileField(upload_to='performline_page_source',blank=True)
 content_local = models.TextField(blank=True)
 date = models.DateTimeField(auto_now_add=True)
 affiliate = models.ForeignKey(Company)
 campaign = models.ForeignKey(Campaign)

 def __unicode__(self):
 return self.image

 class PageDisplay(Page):
 """
 Detail of page of type display
 """
 url = models.URLField(verify_exists=False,blank=True)
 referrer = models.URLField(verify_exists=False,blank=True)
 browser = models.CharField(max_length=255,blank=True)

 def __unicode__(self):
 return self.url

 class PageEmail(Page):
 """
 Detail of page of type email processed by Transparency
 """
 token = models.PositiveIntegerField()
 header = models.TextField()
 source = models.CharField(max_length=10)
 hash = models.CharField(max_length=255)
 batch = models.ForeignKey(Batch)
 message = models.ForeignKey(Message)

 def __unicode__(self):
 return self.source

 from django.db import models
 from campaign.models import Campaign


 # Create your models here.
 LOGIC_CHOICES = (
  ('banned','banned'),
  ('expected','expected'),
  )

 class Phrase(models.Model):
 """
 Returns phrase for Transparency
 """
 phrase = models.CharField(max_length=255)
 logic = models.CharField(max_length=30,choices=LOGIC_CHOICES)
 display = models.BooleanField()
 search = models.BooleanField()
 email = models.BooleanField()
 landing = models.BooleanField()
 campaign = models.ForeignKey(Campaign)
 # category = models.ForeignKey(Category)

 class Meta:

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

2009-07-16 Thread Django

#10885: Update the Hebrew Translaions for 1.1
---+
  Reporter:  Alex  | Owner:  alex
Status:  reopened  | 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 anonymous):

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

Comment:

 avoid spaces before punctuation (like in lines 925 and 230), it doesn't
 look all that good :)

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

2009-07-16 Thread Django

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

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

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

2009-07-16 Thread Django

#7968: ImageField/FileField behaviour on ModelForms
-+--
  Reporter:  sime| Owner:  nobody
Status:  new | Milestone:
 Component:  Documentation   |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by Michael Stevens ):

 This would have really helped me recently.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #9071: Can't disable "add" popup links in the admin

2009-07-16 Thread Django

#9071: Can't disable "add" popup links in the admin
---+
  Reporter:  jacob | Owner:  kratorius
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.0  
Resolution:|  Keywords:  pyconuk  
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by floledermann):

 Btw. you can remove the plus sign by using css - this will not really
 disable the feature but hide it if you shoot for a more consistent user
 experience:

 {{{
 #add_id_<> {
 display: none;
 }
 }}}

 Best is to look up the id of the element in the admin pages' html source.

 If you dont't have an admin css already, you can put this snippet in a
 file - say css/admin.css - and add a Media class to your Admin class:

 {{{
 class Media:
 css = {
 'all': [settings.MEDIA_URL + 'css/admin.css']
 }
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10977: In some cases, the intersection of two QuerySets is empty when it shouldn't be

2009-07-16 Thread Django

#10977: In some cases, the intersection of two QuerySets is empty when it 
shouldn't
be
---+
  Reporter:  zain  | Owner: 
Status:  new   | Milestone: 
 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 |  
---+
Comment (by russellm):

 Ok - a request was made to push this into v1.1. To me. the fix looks ok
 (although I would probably avoid using a variable name like "connection"
 since it's a word that is already in use), and if the full Django test
 suite still passes after applying the fix, then that's about all the
 confirmation you need that the fix is correct (or at least, no more
 incorrect).

 The biggest thing preventing me from committing this is that that the test
 case is trying to be far too clever. The original report gives a very
 clear example of some queries, but no setup.  The test case is -
 ironically - longer than the original report, and is doing all sorts of
 convoluted tricks with manually instantiated QuerySets, calls to reduce(),
 and dynamically rolled out Q() objects. What's wrong with reproducing the
 original problem case? It should be easy to understand what a test is
 trying to achieve - in this case, the test is more complex than the
 problem it's trying to solve.

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

60 matches

Mail list logo