Re: [Django] #10060: Multiple table annotation failure

[Django]

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

  * milestone:  => 1.1

Comment:

 This is a fairly big problem, but it's not going to be an easy one to fix
 - the solution may just have to be documentation to say "don't do that".

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #5096: Doc: Model ref mentions sql-based initial data, should use fixtures

[Django]

#5096: Doc: Model ref mentions sql-based initial data, should use fixtures
-+--
  Reporter:  oggie rob   | Owner:  
jacob 
Status:  assigned| Milestone:  1.1  
 
 Component:  Documentation   |   Version:  SVN  
 
Resolution:  |  Keywords:  
sprint-pycon08
 Stage:  Accepted| Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

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

[noreply]

Author: ubernostrum
Date: 2009-02-28 00:05:44 -0600 (Sat, 28 Feb 2009)
New Revision: 9923

Modified:
   django/branches/releases/1.0.X/docs/ref/databases.txt
   django/branches/releases/1.0.X/docs/topics/install.txt
Log:
[1.0.X] Fixed #10377: Added clearer warning to database notes for cx_Oracle 5.0.

Modified: django/branches/releases/1.0.X/docs/ref/databases.txt
===
--- django/branches/releases/1.0.X/docs/ref/databases.txt   2009-02-28 
06:03:18 UTC (rev 9922)
+++ django/branches/releases/1.0.X/docs/ref/databases.txt   2009-02-28 
06:05:44 UTC (rev 9923)
@@ -333,11 +333,16 @@
 Oracle notes
 
 
-Django supports `Oracle Database Server`_ versions 9i and higher. Oracle
-version 10g or later is required to use Django's ``regex`` and ``iregex`` query
-operators. You will also need a 4.X release of the `cx_Oracle`_ driver,
-version 4.3.1 or newer.
+Django supports `Oracle Database Server`_ versions 9i and
+higher. Oracle version 10g or later is required to use Django's
+``regex`` and ``iregex`` query operators. You will also need at least
+version 4.3.1 of the `cx_Oracle`_ Python driver.
 
+Note that due to a Unicode-corruption bug in ``cx_Oracle`` 5.0, that
+version of the driver should **not** be used with Django;
+``cx_Oracle`` 5.0.1 resolved this issue, so if you'd like to use a
+more recent ``cx_Oracle``, use version 5.0.1.
+
 .. _`Oracle Database Server`: http://www.oracle.com/
 .. _`cx_Oracle`: http://cx-oracle.sourceforge.net/
 

Modified: django/branches/releases/1.0.X/docs/topics/install.txt
===
--- django/branches/releases/1.0.X/docs/topics/install.txt  2009-02-28 
06:03:18 UTC (rev 9922)
+++ django/branches/releases/1.0.X/docs/topics/install.txt  2009-02-28 
06:05:44 UTC (rev 9923)
@@ -82,9 +82,10 @@
   wrapper in the standard library, so you don't need to install anything extra
   in that case.
 
-* If you're using Oracle, you'll need a 4.X release of cx_Oracle_, version
-  4.3.1 or higher. You will also want to read the database-specific notes for
-  the :ref:`Oracle backend `.
+* If you're using Oracle, you'll need a copy of cx_Oracle_, but please
+  read the database-specific notes for the
+  :ref:`Oracle backend ` for important information
+  regarding supported versions of both Oracle and ``cx_Oracle``.
 
 If you plan to use Django's ``manage.py syncdb`` command to
 automatically create database tables for your models, you'll need to


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

[noreply]

Author: ubernostrum
Date: 2009-02-28 00:03:18 -0600 (Sat, 28 Feb 2009)
New Revision: 9922

Modified:
   django/trunk/docs/ref/databases.txt
   django/trunk/docs/topics/install.txt
Log:
Fixed #10377: Added clearer warning to database notes for cx_Oracle 5.0.

Modified: django/trunk/docs/ref/databases.txt
===
--- django/trunk/docs/ref/databases.txt 2009-02-28 05:35:22 UTC (rev 9921)
+++ django/trunk/docs/ref/databases.txt 2009-02-28 06:03:18 UTC (rev 9922)
@@ -366,11 +366,16 @@
 Oracle notes
 
 
-Django supports `Oracle Database Server`_ versions 9i and higher. Oracle
-version 10g or later is required to use Django's ``regex`` and ``iregex`` query
-operators. You will also need a 4.X release of the `cx_Oracle`_ driver,
-version 4.3.1 or newer.
+Django supports `Oracle Database Server`_ versions 9i and
+higher. Oracle version 10g or later is required to use Django's
+``regex`` and ``iregex`` query operators. You will also need at least
+version 4.3.1 of the `cx_Oracle`_ Python driver.
 
+Note that due to a Unicode-corruption bug in ``cx_Oracle`` 5.0, that
+version of the driver should **not** be used with Django;
+``cx_Oracle`` 5.0.1 resolved this issue, so if you'd like to use a
+more recent ``cx_Oracle``, use version 5.0.1.
+
 .. _`Oracle Database Server`: http://www.oracle.com/
 .. _`cx_Oracle`: http://cx-oracle.sourceforge.net/
 

Modified: django/trunk/docs/topics/install.txt
===
--- django/trunk/docs/topics/install.txt2009-02-28 05:35:22 UTC (rev 
9921)
+++ django/trunk/docs/topics/install.txt2009-02-28 06:03:18 UTC (rev 
9922)
@@ -82,9 +82,10 @@
   wrapper in the standard library, so you don't need to install anything extra
   in that case.
 
-* If you're using Oracle, you'll need a 4.X release of cx_Oracle_, version
-  4.3.1 or higher. You will also want to read the database-specific notes for
-  the :ref:`Oracle backend `.
+* If you're using Oracle, you'll need a copy of cx_Oracle_, but please
+  read the database-specific notes for the
+  :ref:`Oracle backend ` for important information
+  regarding supported versions of both Oracle and ``cx_Oracle``.
 
 If you plan to use Django's ``manage.py syncdb`` command to
 automatically create database tables for your models, you'll need to


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10377: Improve database notes with respect to cx_Oracle 5.0 Unicode bug

[Django]

#10377: Improve database notes with respect to cx_Oracle 5.0 Unicode bug
+---
  Reporter:  ubernostrum| Owner:  ubernostrum
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ikelly):

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

Comment:

 I've run the test suite against cx_Oracle 5.0.1 and found no problems, so
 I think we're good there.  The text looks good to me, except that we also
 mention cx_Oracle versions in docs/topcis/install.txt; that should be
 updated as 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
-~--~~~~--~~--~--~---

[Changeset] r9921 - in django/trunk: django/core/management/commands docs/ref tests/modeltests/fixtures tests/modeltests/fixtures/fixtures

[noreply]

Author: russellm
Date: 2009-02-27 23:35:22 -0600 (Fri, 27 Feb 2009)
New Revision: 9921

Modified:
   django/trunk/django/core/management/commands/dumpdata.py
   django/trunk/docs/ref/django-admin.txt
   django/trunk/tests/modeltests/fixtures/fixtures/fixture1.json
   django/trunk/tests/modeltests/fixtures/models.py
Log:
Fixed #5610 -- Added the ability for dumpdata to take individual model names, 
as well as entire applications. Thanks to David Reynolds for his work on this 
patch.

Modified: django/trunk/django/core/management/commands/dumpdata.py
===
--- django/trunk/django/core/management/commands/dumpdata.py2009-02-28 
04:52:16 UTC (rev 9920)
+++ django/trunk/django/core/management/commands/dumpdata.py2009-02-28 
05:35:22 UTC (rev 9921)
@@ -1,3 +1,4 @@
+from django.core.exceptions import ImproperlyConfigured
 from django.core.management.base import BaseCommand, CommandError
 from django.core import serializers
 
@@ -9,14 +10,14 @@
 help='Specifies the output serialization format for fixtures.'),
 make_option('--indent', default=None, dest='indent', type='int',
 help='Specifies the indent level to use when pretty-printing 
output'),
-make_option('-e', '--exclude', dest='exclude',action='append', 
default=[], 
+make_option('-e', '--exclude', dest='exclude',action='append', 
default=[],
 help='App to exclude (use multiple --exclude to exclude multiple 
apps).'),
 )
 help = 'Output the contents of the database as a fixture of the given 
format.'
 args = '[appname ...]'
 
 def handle(self, *app_labels, **options):
-from django.db.models import get_app, get_apps, get_models
+from django.db.models import get_app, get_apps, get_models, get_model
 
 format = options.get('format','json')
 indent = options.get('indent',None)
@@ -26,10 +27,35 @@
 excluded_apps = [get_app(app_label) for app_label in exclude]
 
 if len(app_labels) == 0:
-app_list = [app for app in get_apps() if app not in excluded_apps]
+app_list = dict([(app, None) for app in get_apps() if app not in 
excluded_apps])
 else:
-app_list = [get_app(app_label) for app_label in app_labels]
+app_list = {}
+for label in app_labels:
+try:
+app_label, model_label = label.split('.')
+try:
+app = get_app(app_label)
+except ImproperlyConfigured:
+raise CommandError("Unknown application: %s" % 
app_label)
 
+model = get_model(app_label, model_label)
+if model is None:
+raise CommandError("Unknown model: %s.%s" % 
(app_label, model_label))
+
+if app in app_list.keys():
+if app_list[app] and model not in app_list[app]:
+app_list[app].append(model)
+else:
+app_list[app] = [model]
+except ValueError:
+# This is just an app - no model qualifier
+app_label = label
+try:
+app = get_app(app_label)
+except ImproperlyConfigured:
+raise CommandError("Unknown application: %s" % 
app_label)
+app_list[app] = None
+
 # Check that the serialization format exists; this is a shortcut to
 # avoid collating all the objects and _then_ failing.
 if format not in serializers.get_public_serializer_formats():
@@ -41,9 +67,13 @@
 raise CommandError("Unknown serialization format: %s" % format)
 
 objects = []
-for app in app_list:
-for model in get_models(app):
-objects.extend(model._default_manager.all())
+for app, model_list in app_list.items():
+if model_list is None:
+model_list = get_models(app)
+
+for model in model_list:
+objects.extend(model.objects.all())
+
 try:
 return serializers.serialize(format, objects, indent=indent)
 except Exception, e:

Modified: django/trunk/docs/ref/django-admin.txt
===
--- django/trunk/docs/ref/django-admin.txt  2009-02-28 04:52:16 UTC (rev 
9920)
+++ django/trunk/docs/ref/django-admin.txt  2009-02-28 05:35:22 UTC (rev 
9921)
@@ -186,7 +186,7 @@
 dumpdata
 
 
-.. django-admin:: dumpdata 
+.. django-admin:: dumpdata 
 
 Outputs to standard output all data in the database associated with the named
 application(s).
@@ -228,6 +228,14 @@
 easy for humans to read, so you can use the ``--indent`` option to
 pretty-print the output with a number of indentation spaces.
 
+.. 

Re: [Django] #9084: File-based session does not store any data on Windows

[Django]

#9084: File-based session does not store any data on Windows
--+-
  Reporter:  mizutori | Owner: 
Status:  new  | Milestone: 
 Component:  django.contrib.sessions  |   Version:  1.0
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by mtredinnick):

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

Comment:

 I'm not going to have time to work on this for a bit and I want to clean
 out my list of "reserved" bugs. So giving it back to the pool. Thoughts in
 comment:2 are still valid, I feel. It's tricky, but I'm happy to review
 any patches that come along.

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

[noreply]

Author: mtredinnick
Date: 2009-02-27 22:52:16 -0600 (Fri, 27 Feb 2009)
New Revision: 9920

Modified:
   django/branches/releases/1.0.X/django/utils/dateformat.py
Log:
[1.0.X] Fixed #10048 -- Handle non-existent timezone in dateformat functions.

Backport of r9919 from trunk.

Modified: django/branches/releases/1.0.X/django/utils/dateformat.py
===
--- django/branches/releases/1.0.X/django/utils/dateformat.py   2009-02-28 
04:51:13 UTC (rev 9919)
+++ django/branches/releases/1.0.X/django/utils/dateformat.py   2009-02-28 
04:52:16 UTC (rev 9920)
@@ -131,7 +131,7 @@
 
 def I(self):
 "'1' if Daylight Savings Time, '0' otherwise."
-if self.timezone.dst(self.data):
+if self.timezone and self.timezone.dst(self.data):
 return u'1'
 else:
 return u'0'
@@ -192,14 +192,14 @@
 
 def T(self):
 "Time zone of this machine; e.g. 'EST' or 'MDT'"
-name = self.timezone.tzname(self.data)
+name = self.timezone and self.timezone.tzname(self.data) or None
 if name is None:
 name = self.format('O')
 return unicode(name)
 
 def U(self):
 "Seconds since the Unix epoch (January 1 1970 00:00:00 GMT)"
-off = self.timezone.utcoffset(self.data)
+off = self.timezone and self.timezone.utcoffset(self.data) or 0
 return int(time.mktime(self.data.timetuple())) + off.seconds * 60
 
 def w(self):
@@ -253,6 +253,8 @@
 timezones west of UTC is always negative, and for those east of UTC is
 always positive.
 """
+if not self.timezone:
+return 0
 offset = self.timezone.utcoffset(self.data)
 # Only days can be negative, so negative offsets have days=-1 and
 # seconds positive. Positive offsets have days=0


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

[noreply]

Author: mtredinnick
Date: 2009-02-27 22:51:13 -0600 (Fri, 27 Feb 2009)
New Revision: 9919

Modified:
   django/trunk/django/utils/dateformat.py
Log:
Fixed #10048 -- Handle non-existent timezone in dateformat functions.

Modified: django/trunk/django/utils/dateformat.py
===
--- django/trunk/django/utils/dateformat.py 2009-02-28 04:46:38 UTC (rev 
9918)
+++ django/trunk/django/utils/dateformat.py 2009-02-28 04:51:13 UTC (rev 
9919)
@@ -131,7 +131,7 @@
 
 def I(self):
 "'1' if Daylight Savings Time, '0' otherwise."
-if self.timezone.dst(self.data):
+if self.timezone and self.timezone.dst(self.data):
 return u'1'
 else:
 return u'0'
@@ -192,14 +192,14 @@
 
 def T(self):
 "Time zone of this machine; e.g. 'EST' or 'MDT'"
-name = self.timezone.tzname(self.data)
+name = self.timezone and self.timezone.tzname(self.data) or None
 if name is None:
 name = self.format('O')
 return unicode(name)
 
 def U(self):
 "Seconds since the Unix epoch (January 1 1970 00:00:00 GMT)"
-off = self.timezone.utcoffset(self.data)
+off = self.timezone and self.timezone.utcoffset(self.data) or 0
 return int(time.mktime(self.data.timetuple())) + off.seconds * 60
 
 def w(self):
@@ -253,6 +253,8 @@
 timezones west of UTC is always negative, and for those east of UTC is
 always positive.
 """
+if not self.timezone:
+return 0
 offset = self.timezone.utcoffset(self.data)
 # Only days can be negative, so negative offsets have days=-1 and
 # seconds positive. Positive offsets have days=0


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] r9918 - in django/trunk: django/core/management/commands django/test tests

[noreply]

Author: mtredinnick
Date: 2009-02-27 22:46:38 -0600 (Fri, 27 Feb 2009)
New Revision: 9918

Modified:
   django/trunk/django/core/management/commands/test.py
   django/trunk/django/test/utils.py
   django/trunk/tests/runtests.py
Log:
Fixed #10165 -- Use settings.TEST_RUNNER in runtests.py

This permits running Django's core tests under an alternative test runner. Most
likely useful to non-CPython implementations, rather than much else (since
Django's core tests might assume things about the test runner).

Patch from Leo Soto.

Modified: django/trunk/django/core/management/commands/test.py
===
--- django/trunk/django/core/management/commands/test.py2009-02-28 
03:02:52 UTC (rev 9917)
+++ django/trunk/django/core/management/commands/test.py2009-02-28 
04:46:38 UTC (rev 9918)
@@ -14,19 +14,12 @@
 
 def handle(self, *test_labels, **options):
 from django.conf import settings
+from django.test.utils import get_runner
 
 verbosity = int(options.get('verbosity', 1))
 interactive = options.get('interactive', True)
+test_runner = get_runner(settings)
 
-test_path = settings.TEST_RUNNER.split('.')
-# Allow for Python 2.5 relative paths
-if len(test_path) > 1:
-test_module_name = '.'.join(test_path[:-1])
-else:
-test_module_name = '.'
-test_module = __import__(test_module_name, {}, {}, test_path[-1])
-test_runner = getattr(test_module, test_path[-1])
-
 failures = test_runner(test_labels, verbosity=verbosity, 
interactive=interactive)
 if failures:
 sys.exit(failures)

Modified: django/trunk/django/test/utils.py
===
--- django/trunk/django/test/utils.py   2009-02-28 03:02:52 UTC (rev 9917)
+++ django/trunk/django/test/utils.py   2009-02-28 04:46:38 UTC (rev 9918)
@@ -65,3 +65,14 @@
 
 del mail.outbox
 
+
+def get_runner(settings):
+test_path = settings.TEST_RUNNER.split('.')
+# Allow for Python 2.5 relative paths
+if len(test_path) > 1:
+test_module_name = '.'.join(test_path[:-1])
+else:
+test_module_name = '.'
+test_module = __import__(test_module_name, {}, {}, test_path[-1])
+test_runner = getattr(test_module, test_path[-1])
+return test_runner

Modified: django/trunk/tests/runtests.py
===
--- django/trunk/tests/runtests.py  2009-02-28 03:02:52 UTC (rev 9917)
+++ django/trunk/tests/runtests.py  2009-02-28 04:46:38 UTC (rev 9918)
@@ -149,8 +149,12 @@
 pass
 
 # Run the test suite, including the extra validation tests.
-from django.test.simple import run_tests
-failures = run_tests(test_labels, verbosity=verbosity, 
interactive=interactive, extra_tests=extra_tests)
+from django.test.utils import get_runner
+if not hasattr(settings, 'TEST_RUNNER'):
+settings.TEST_RUNNER = 'django.test.simple.run_tests'
+test_runner = get_runner(settings)
+
+failures = test_runner(test_labels, verbosity=verbosity, 
interactive=interactive, extra_tests=extra_tests)
 if failures:
 sys.exit(failures)
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10193: Meaning of 'path to file' parameter is unclear in documentation

[Django]

#10193: Meaning of 'path to file' parameter is unclear in documentation
+---
  Reporter:  Art_S  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by mtredinnick):

 What's the difference between a "path" and a "path name"? I don't see how
 this can be unclear. It's saying you have to specify the location of the
 file, using the normal syntax for doing so. Needs clarification from the
 reporter as to what the perceived problem is here.

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

[Django]

#10173: Add a setting to set up pg binaries for test_runner
-+--
  Reporter:  laureline.gue...@makina-corpus.org  | Owner:  
nobody
Status:  closed  | Milestone:   
 
 Component:  GIS |   Version:  1.0  
 
Resolution:  wontfix |  Keywords:   
 
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

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

Comment:

 Yeah, this is becoming settings overload. It's a sysadmin issue: making
 sure the right binaries can be found.

 if these binaries really are all over the place on different distros, or
 not on standard paths normally, then the more traditional solution would
 be an environment variable to declare which binary should be run. That can
 then be set in the users environment. Wontfixing the current approach.
 Seems a bit too specialised and not really the right approach.

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

[Django]

#10151: url tag causes TypeError: dict objects are unhashable
+---
  Reporter:  pclerie| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 There's no information here about how to repeat the problem. I cannot
 imagine how this would be happening, so please provide a short, step-by-
 step example of how to trigger it. If we can't repeat it, we cannot
 evaluate the issue.

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

Re: [Django] #10139: Slicing an EmptyQuerySet gives a list, not another EmptyQuerySet

[Django]

#10139: Slicing an EmptyQuerySet gives a list, not another EmptyQuerySet
+---
  Reporter:  forest | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0-beta-1
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

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

Comment:

 This isn't quite as clear as it looks. Slicing a normal `QuerySet` will
 sometimes return a list as well; it depends upon whether the results have
 already been retrieved from the database or not.

 ''Probably'' the solution here is a documentation one, but it's worth
 thinking about what else might be possible. Always returning a `QuerySet`,
 though, is, from memory, a little fiddly to organise efficiently and
 always correctly.

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

Re: [Django] #7338: Method .cache(timeout) in QuerySet

[Django]

#7338: Method .cache(timeout) in QuerySet
---+
  Reporter:  marinho   | Owner:  marinho
Status:  assigned  | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Design decision needed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by mtredinnick):

 All the latest reasons I've seen to include this are because "it's a
 compromise because of ". So fix the real issue,
 rather than trying to put in a compromise. Sure, it's harder. But it's
 much more worthwhile in the long run and helps us work out whether it
 really is a bigger problem, or not really a problem and what the possible
 alternatives are.

 For example, maybe an identity manager, a la #17 (or, at least some
 variation on #17, since that ticket wanders all over the place) is the
 solution. Maybe the sort of thing we want to do for Django 1.2 or 1.3
 allowing specifying an alternative default `QuerySet` class is the right
 solution. Maybe it's something else.

 Right now, though, I'm unconvinced that we're forced to compromise yet.

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

[Django]

#9885: post_batch_update Signal on QuerySets
---+
  Reporter:  matehat   | Owner:  matehat
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Design decision needed| Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by matehat):

 Even if we can't be totally sure of the rows that are being updated or
 deleted, we still have a queryset in hand with the where clauses that
 should, in many cases, point the same rows before and after the update
 query, but an update query that updates the very columns that were used to
 build the queryset would indeed see that kind of signal useless.

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

[Django]

#10099: MySQL 5.0 does not support LIMIT in subqueries
---+
  Reporter:  Anossov   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by mtredinnick):

 comment:9 is not an accurate diagnosis. The older syntax is still valid
 (after all, that's basically what is used internally). However, we've now
 introduced a better public API (the previous method shouldn't have ever
 really been documented, so as not to expose internal details).

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

[Django]

#10377: Improve database notes with respect to cx_Oracle 5.0 Unicode bug
---+
 Reporter:  ubernostrum|   Owner:  ubernostrum
   Status:  new|   Milestone: 
Component:  Documentation  | Version:  1.0
 Keywords: |   Stage:  Unreviewed 
Has_patch:  1  |  
---+
 Since #9935 documented multiple people getting bit by a Unicode-corrupting
 bug in `cx_Oracle` 5.0, it might be a good idea to have the database notes
 section of the docs be a bit more clear on the fact that 5.0 should not be
 used (currently it says, misleadingly, "4.3.1 or later" in one place,
 while stating the requirement of 4.x further back in the paragraph.

 The attached patch tries to make this clear, and also recommends
 `cx_Oracle` 5.0.1 which, per upstream announce, resolved the bug.

 If one of our Oracle gurus (I'm cc'ing Ian on this) could verify the text
 (and maybe double-check against 5.0.1 to make sure it really did fix
 things), I'll commit this and do a backport into the 1.0.x docs as 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] #9885: post_batch_update Signal on QuerySets

[Django]

#9885: post_batch_update Signal on QuerySets
---+
  Reporter:  matehat   | Owner:  matehat
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Design decision needed| Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by mtredinnick):

 I'm still very reluctant to add this signal, but I'm not going to wontfix
 until another developer concurs. For the record, it's not even going to be
 a reliable result, since the rows that are updated are decided by the
 database and not available to Django (whereas the single model save case
 knows exactly which row is updated).

 Would like another core developer to sanity check before we resolve this
 one way or the other.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10037: id column is created in ManyToMany link (relation) table

[Django]

#10037: id column is created in ManyToMany link (relation) table
---+
  Reporter:  powerfox  | Owner:  nobody 

Status:  closed| Milestone: 

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

Resolution:  wontfix   |  Keywords:  
ManyToManyField
 Stage:  Design decision needed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 This isn't a bug, in that it's intentional behaviour. Removing it would at
 least be backwards incompatible.

 A proposal to add an API to not create that column might be interesting to
 discuss (in the Django 1.2 timeframe, most likely). Start a thread on
 django-dev when proposals are discussed for Django 1.2 if you can think of
 an API. Also, have a check in the ticket system -- I have a feeling there
 might already be a ticket open about such an API (or, at least, a
 discussion on the mailing lists).


 Not worth removing at this time, however.

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

Re: [Django] #10032: ORM switches incorrectly to OUTER JOIN in certain cases with isnull=True

[Django]

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

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

Comment:

 There's no way for Django to read the user's mind here and there are two
 quite acceptable ways to interpret that filter. Django has chosen one way
 (which matches the fairly natural way the equivalent SQL query might fall
 out). You have chosen the other way. Unfortunately we can't have both.

 You will need to write your query as
 {{{
 #!python
 Group.objects.filter(person__stamp__isnull=True, person__isnul=False)
 }}}
 or, similarly,
 {{{
 #!python
 Group.objects.exclude(person=None).filter(person__stamp=None)
 }}}
 etc.

 The current behaviour isn't "incorrect". It's an interpretation of an
 ambiguous situation and we're very consistent about how that
 interpretation is applied. If you'd like to propose a documentation
 clarification, that would be worth looking at.

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

[noreply]

Author: mtredinnick
Date: 2009-02-27 21:02:52 -0600 (Fri, 27 Feb 2009)
New Revision: 9917

Modified:
   django/branches/releases/1.0.X/django/db/models/sql/query.py
   django/branches/releases/1.0.X/tests/regressiontests/queries/models.py
Log:
[1.0.X] Fixed #10028 -- Fixed a problem when ordering by related models.

Some results were inadvertently being excluded if we were ordering across a
nullable relation which itself ordering by a non-nullable relation.

Backport of r9916 from trunk.

Modified: django/branches/releases/1.0.X/django/db/models/sql/query.py
===
--- django/branches/releases/1.0.X/django/db/models/sql/query.py
2009-02-28 02:59:40 UTC (rev 9916)
+++ django/branches/releases/1.0.X/django/db/models/sql/query.py
2009-02-28 03:02:52 UTC (rev 9917)
@@ -687,8 +687,9 @@
 # the model.
 self.ref_alias(alias)
 
-# Must use left outer joins for nullable fields.
-self.promote_alias_chain(joins)
+# Must use left outer joins for nullable fields and their relations.
+self.promote_alias_chain(joins,
+self.alias_map[joins[0]][JOIN_TYPE] == self.LOUTER)
 
 # If we get to this point and the field is a relation to another model,
 # append the default ordering for that model.

Modified: django/branches/releases/1.0.X/tests/regressiontests/queries/models.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/queries/models.py  
2009-02-28 02:59:40 UTC (rev 9916)
+++ django/branches/releases/1.0.X/tests/regressiontests/queries/models.py  
2009-02-28 03:02:52 UTC (rev 9917)
@@ -237,7 +237,33 @@
 class PointerB(models.Model):
 connection = models.ForeignKey(SharedConnection)
 
+# Multi-layer ordering
+class SingleObject(models.Model):
+name = models.CharField(max_length=10)
 
+class Meta:
+ordering = ['name']
+
+def __unicode__(self):
+return self.name
+
+class RelatedObject(models.Model):
+single = models.ForeignKey(SingleObject)
+
+class Meta:
+ordering = ['single']
+
+class Plaything(models.Model):
+name = models.CharField(max_length=10)
+others = models.ForeignKey(RelatedObject, null=True)
+
+class Meta:
+ordering = ['others']
+
+def __unicode__(self):
+return self.name
+
+
 __test__ = {'API_TESTS':"""
 >>> t1 = Tag.objects.create(name='t1')
 >>> t2 = Tag.objects.create(name='t2', parent=t1)


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

[noreply]

Author: mtredinnick
Date: 2009-02-27 20:59:40 -0600 (Fri, 27 Feb 2009)
New Revision: 9916

Modified:
   django/trunk/django/db/models/sql/query.py
   django/trunk/tests/regressiontests/queries/models.py
Log:
Fixed #10028 -- Fixed a problem when ordering by related models.

Some results were inadvertently being excluded if we were ordering across a
nullable relation which itself ordering by a non-nullable relation.

Modified: django/trunk/django/db/models/sql/query.py
===
--- django/trunk/django/db/models/sql/query.py  2009-02-28 01:29:00 UTC (rev 
9915)
+++ django/trunk/django/db/models/sql/query.py  2009-02-28 02:59:40 UTC (rev 
9916)
@@ -716,7 +716,7 @@
 result, params = [], []
 if self.group_by is not None:
 group_by = self.group_by or []
-
+
 extra_selects = []
 for extra_select, extra_params in self.extra_select.itervalues():
 extra_selects.append(extra_select)
@@ -834,8 +834,9 @@
 # the model.
 self.ref_alias(alias)
 
-# Must use left outer joins for nullable fields.
-self.promote_alias_chain(joins)
+# Must use left outer joins for nullable fields and their relations.
+self.promote_alias_chain(joins,
+self.alias_map[joins[0]][JOIN_TYPE] == self.LOUTER)
 
 # If we get to this point and the field is a relation to another model,
 # append the default ordering for that model.

Modified: django/trunk/tests/regressiontests/queries/models.py
===
--- django/trunk/tests/regressiontests/queries/models.py2009-02-28 
01:29:00 UTC (rev 9915)
+++ django/trunk/tests/regressiontests/queries/models.py2009-02-28 
02:59:40 UTC (rev 9916)
@@ -238,7 +238,33 @@
 class PointerB(models.Model):
 connection = models.ForeignKey(SharedConnection)
 
+# Multi-layer ordering
+class SingleObject(models.Model):
+name = models.CharField(max_length=10)
 
+class Meta:
+ordering = ['name']
+
+def __unicode__(self):
+return self.name
+
+class RelatedObject(models.Model):
+single = models.ForeignKey(SingleObject)
+
+class Meta:
+ordering = ['single']
+
+class Plaything(models.Model):
+name = models.CharField(max_length=10)
+others = models.ForeignKey(RelatedObject, null=True)
+
+class Meta:
+ordering = ['others']
+
+def __unicode__(self):
+return self.name
+
+
 __test__ = {'API_TESTS':"""
 >>> t1 = Tag.objects.create(name='t1')
 >>> t2 = Tag.objects.create(name='t2', parent=t1)
@@ -1044,6 +1070,11 @@
 >>> Annotation.objects.filter(notes__in=Note.objects.filter(note="n1").values_list('note').values('id'))
 []
 
+Bug #10028 -- ordering by model related to nullable relations(!) should use
+outer joins, so that all results are included.
+>>> _ = Plaything.objects.create(name="p1")
+>>> Plaything.objects.all()
+[]
 """}
 
 # In Python 2.3 and the Python 2.6 beta releases, exceptions raised in __len__


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

[Django]

#8576: Multiple AutoFields in a model
---+
  Reporter:  honeyman  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:  wontfix   |  Keywords:  multiple 
autofield
 Stage:  Design decision needed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Without a compelling use-case, this isn't worth doing. One auto-
 incrementing field per model is almost always going to be enough
 (everything else can be derived from the single source, e.g, in the
 `save()` method). Whilst the comments about auto-increment fields not
 being required to be primary key, etc, are valid, Django's `AutoField`
 isn't just an auto-increment field. It's also a primary key field and all
 the other goodies. So there's two ways of looking for that.

 If there's some really strong use-case that's been overlooked here, it can
 be brought up in a thread on django-dev. But "just because we can" isn't a
 reason to do something.

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

Re: [Django] #5863: list_display does not allow functions of referenced objects

[Django]

#5863: list_display does not allow functions of referenced objects
---+
  Reporter:  Beat Bolli   | Owner:  nobody 
 
Status:  reopened  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  
list_display
 Stage:  Design decision needed| Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  0  
 
Needs_better_patch:  1 |  
---+
Changes (by codekoala):

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

Comment:

 oops... didn't mean to adjust the ticket properties like that.

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

Re: [Django] #5863: list_display does not allow functions of referenced objects

[Django]

#5863: list_display does not allow functions of referenced objects
---+
  Reporter:  Beat Bolli   | Owner:  nobody 
 
Status:  reopened  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  
list_display
 Stage:  Design decision needed| Has_patch:  0  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by codekoala):

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

Comment:

 Would someone like to review the snippet I've come up with as a "work
 around" of sorts?  It would definitely need some work before it could be
 used in Django if it's deemed worthy, but I hope it's an option at
 least...  I'm not sure I feel comfortable posting it as a patch because of
 the issues involved with my approach, but I still think it's worth looking
 at.

 You can find it here, along with some details about the issues involved:
 http://www.codekoala.com/blog/2009/feb/27/model-relationships-and-
 list_display/

 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] #10028: Incorrect SQL join construction

[Django]

#10028: Incorrect SQL join construction
---+
  Reporter:  brian | Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  Database layer (models, ORM)  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by mtredinnick):

 In this particular case, the potential problems in comment:2 don't apply.
 The class names and attribute names are in different namespaces, so
 clashes won't occur (although it certainly makes the code confusing).
 There is a legitimate bug here.

 The issue is that ordering joins aren't being promoted to outer joins in
 all the right circumstances.

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

[Django]

#10133: "Years" translation in french is wrong
---+
  Reporter:  Sephi | Owner:  nobody
Status:  closed| Milestone:  1.1   
 Component:  Translations  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 I'm going to close this as a "duplicate' of #10013. I realise it's not a
 true duplicate, but, as claudep mentions, it's worhtwhile making a single
 patch and there's some improvements needed over there anyway (which
 anybody can do, so if Sephi wants to move things along, that would be a
 place to start).

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

Re: [Django] #10013: Updated French translation

[Django]

#10013: Updated French translation
---+
  Reporter:  stephaner | Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by mtredinnick):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted

Comment:

 This patch introduces errors into the PO file. It is always necessary to
 check the format of your changes by running
 {{{
 django-admin.py compilemessages -l fr
 }}}
 from the `django/` directory. If you do that, you'll notice a bunch of
 problems are reported. In particular, you cannot have both `msgstr[0]` and
 `msgstr` lines for a single `msgid`.

 Also, we do not put individual contributors' names into any file in Django
 (except for the last-translator name). So the names you have put into the
 comments at the top of the file should actually be patches against the
 AUTHORS file. David's name is already in AUTHORS. In the revised patch,
 please put the other two names into AUTHORS.

 Finally, as proposed in the first comment to #10133, please include the
 fix mentioned there, so that there's only a single patch to apply when the
 time comes. It's always a little fragile applying two patches to the same
 locale files.

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

[Django]

#10011: Updates to Thai translations
---+
  Reporter:  KayEss| Owner:  nobody 
Status:  closed| Milestone:  1.1
 Component:  Translations  |   Version:  SVN
Resolution:  fixed |  Keywords:  thai th
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by mtredinnick):

 I've applied this to trunk (see previous comment), but I am struggling to
 backport the patch to the 1.0.X branch. I've mentioned in the past that I
 will only do this if it's easy. In this case, there are conflicts.

 So if anybody who can speak Thai would like to create a reliable patch
 against the 1.0.X branch, I'm happy to apply that. For now, the branch
 uses a slightly older set of translations.

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

[noreply]

Author: mtredinnick
Date: 2009-02-27 19:29:00 -0600 (Fri, 27 Feb 2009)
New Revision: 9915

Modified:
   django/trunk/django/conf/locale/th/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/th/LC_MESSAGES/django.po
   django/trunk/django/conf/locale/th/LC_MESSAGES/djangojs.mo
   django/trunk/django/conf/locale/th/LC_MESSAGES/djangojs.po
Log:
Fixed #10011 -- Updated Thai translation from Kowito Charoenratchatabhan.

Modified: django/trunk/django/conf/locale/th/LC_MESSAGES/django.mo
===
--- django/trunk/django/conf/locale/th/LC_MESSAGES/django.mo2009-02-28 
01:24:24 UTC (rev 9914)
+++ django/trunk/django/conf/locale/th/LC_MESSAGES/django.mo2009-02-28 
01:29:00 UTC (rev 9915)
@@ -1,108 +1,121 @@
-��
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10376: I need to point feeds to get their templates from my template directory

[Django]

#10376: I need to point feeds to get their templates from my template directory
-+--
  Reporter:  RuslanPopov | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Generic views   |   Version:  SVN   
Resolution:  wontfix |  Keywords:  feed  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

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

Comment:

 I don't think this is worth doing. You can already put templates in app
 template directories (where the app-based template loader will find them).
 That's pretty common. If you wanted to do things in the way you've got
 above, you can hard-code the app name into the template load path.

 Your patch seems to add a slightly similar, but not identical, template
 loading scheme to the app-based template loader. If you really wanted to
 do that, it would be better to write your own template loader that worked
 in exactly that way.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10376: I need to point feeds to get their templates from my template directory

[Django]

#10376: I need to point feeds to get their templates from my template directory
-+--
  Reporter:  RuslanPopov | Owner:  nobody
Status:  new | Milestone:
 Component:  Generic views   |   Version:  SVN   
Resolution:  |  Keywords:  feed  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 No patch that makes the assumption the app name is a specific part of the
 URL is going to be accepted, second why can't you just put your feed
 template at project_name/templates/feeds/ ?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #4092: django/contrib/localflavor/usa/forms.py USStateSelect missing blank options

[Django]

#4092: django/contrib/localflavor/usa/forms.py USStateSelect missing blank 
options
-+--
  Reporter:  polpak    | Owner:  rokclimb15
Status:  new | Milestone:
 Component:  django.contrib.localflavor  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by rokclimb15):

  * owner:  rokclim...@gmail.com => rokclimb15
  * needs_better_patch:  1 => 0

Comment:

 I have updated dougn's patch so it is now compatible with r9912.  I
 removed modifications to forms.models since I don't think we want all
 model generated choicefields to have this type of widget.  Eliminating the
 empty label option produced failures in the forms test cases.  If someone
 wants to use this widget with their ModelChoiceField, they can override
 the widget for the ChoiceField in kwargs.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10375: Additional info to documentation (date and time filters)

[Django]

#10375: Additional info to documentation (date and time filters)
+---
  Reporter:  sayane | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  filter time date
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by sayane):

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

Comment:

 Sorry, there's a mistake. Description should start with "Documentation
 about" ;-)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10375: Additional info to documentation (date and time filters)

[Django]

#10375: Additional info to documentation (date and time filters)
--+-
 Reporter:  sayane|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:  1.0   
 Keywords:  filter time date  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Documentation od "date" and "time" filters should contain info about
 default formatting. When you use them without arguments, they use
 DATE_FORMAT and TIME_FORMAT settings. This information should be added to
 django documentation.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #9503: "Model instance reference" docs don't really discuss delete.

[Django]

#9503: "Model instance reference" docs don't really discuss delete.
+---
  Reporter:  Beetle_B   | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 #10351 reported this also and notes that doc for delete can currently be
 fond under "Making queries"

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

[Django]

#10351: Omision from the documentation for Model Instances page
---+
  Reporter:  dh...@mintel.com  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Documentation |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 #9503 looks to already cover this.

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

Re: [Django] #9897: Misleading model formsets docs

[Django]

#9897: Misleading model formsets docs
+---
  Reporter:  sorl   | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by sorl):

 Reviewing it again I realize it should read:

 {{{
 from django.forms.models import BaseModelFormSet

 class BaseAuthorFormSet(BaseModelFormSet):
 def get_queryset(self):
 if not hasattr(self, '_queryset'):
 if self.queryset is not None:
 qs = self.queryset
 else:
 qs = self.model._default_manager.get_query_set()
 qs = qs.filter(name__startswith='O')
 if self.max_num > 0:
 self._queryset = qs[:self.max_num]
 else:
 self._queryset = qs
 return self._queryset

 }}}

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

[Django]

#10134: unique_for_* broken?
---+
  Reporter:  wdoekes   | Owner:  nobody 
 
Status:  new   | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
unique_for_date unique_for_month unique_for_year
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.1

Comment:

 I think we need a similar stop-gap to unique_together for unique_for_date
 in 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] #10130: Support setting deletion

[Django]

#10130: Support setting deletion
-+--
  Reporter:  jcassee | Owner:  nobody  
Status:  new | Milestone:  1.1 
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  settings
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10126: Add sanitize and tidy options to textile filter.

[Django]

#10126: Add sanitize and tidy options to textile filter.
-+--
  Reporter:  anonymous   | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Contrib apps|   Version:  1.0
Resolution:  |  Keywords:  textile
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * stage:  Unreviewed => Design decision needed

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

Re: [Django] #10123: {% url %} template tag prepends project path to absolute url

[Django]

#10123: {% url %} template tag prepends project path to absolute url
+---
  Reporter:  patrick.schoenm...@cinetis.ch  | Owner:  nobody

Status:  closed | Milestone:

 Component:  Template system|   Version:  1.0   

Resolution:  invalid|  Keywords:  url, 
reverse, template tag
 Stage:  Unreviewed | Has_patch:  0 

Needs_docs:  1  |   Needs_tests:  1 

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

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10119: Optionally append index.html for directories in static media serving view

[Django]

#10119: Optionally append index.html for directories in static media serving 
view
+---
  Reporter:  floguy | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 The `serve` view isn't intended to pretend to be a real web server. It's
 deliberately crippled.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10117: Test server sometimes causes 'Connection reset by peer' when retrieving POST data

[Django]

#10117: Test server sometimes causes 'Connection reset by peer' when retrieving
POST data
+---
  Reporter:  Almad  | Owner:  nobody
Status:  closed | Milestone:
 Component:  HTTP handling  |   Version:  1.0   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 No, this is indeed a duplicate of #3357.

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

[Django]

#10116: Documentation about serving media files should mention Nginx
+---
  Reporter:  Uninen | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  media, docs, nginx
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

Re: [Django] #10114: spaces are inserted for 'blank' fields

[Django]

#10114: spaces are inserted for 'blank' fields
---+
  Reporter:  wmstudio  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 The admin strips leading and trailing spaces, so I don't quite see how
 this would be happening, and sure enough I can't reproduce this. Please
 investigate further to make sure it's not a bug in your own code, and
 reopen if you can provide more details to help us track this down.

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

[Django]

#10111: InlineModelAdmin documentation is confusing
+---
  Reporter:  medhat | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

Re: [Django] #10109: Move raw sql from models.fields.related to models.sql.query

[Django]

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

  * stage:  Unreviewed => Accepted

Comment:

 This needs to happen as part of a bigger refactor of related fields.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10108: Two classes with a common superclass have multiple ForeignKeys from one to the other if the one has a single Foreign Key to the other.

[Django]

#10108: Two classes with a common superclass have multiple ForeignKeys from one 
to
the other if the one has a single Foreign Key to the other.
-+--
  Reporter:  m...@hjmills.co.uk  | Owner:  nobody   
 
Status:  closed  | Milestone:   
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  wontfix |  Keywords:  foreign key, 
inheritance, ForeignKey, OneToOne
 Stage:  Unreviewed  | Has_patch:  0
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

Comment:

 Karen's correct: a `OneToOneField` is a `ForeignKey`, and we can't ignore
 one of 'em automatically. `fk_name` exists precisely for this purpose.

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

[Django]

#10106: default admin config for User should include is_active filter
-+--
  Reporter:  carljm  | Owner:  nobody
Status:  new | Milestone:  1.1   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

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

Re: [Django] #10102: daily_cleanup.py should have svn:executable set

[Django]

#10102: daily_cleanup.py should have svn:executable set
+---
  Reporter:  john_scott | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

Re: [Django] #10099: MySQL 5.0 does not support LIMIT in subqueries

[Django]

#10099: MySQL 5.0 does not support LIMIT in subqueries
---+
  Reporter:  Anossov   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 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 jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10094: do_extenbds function incorrectly parses Token

[Django]

#10094: do_extenbds function incorrectly parses Token
--+-
  Reporter:  pe...@monicol.co.uk  | Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  Uncategorized|   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10092: Reference documentation lowest-level headings too small and lack indents

[Django]

#10092: Reference documentation lowest-level headings too small and lack indents
+---
  Reporter:  adrian_nye | Owner:  nobody   
Status:  new| Milestone:  1.1  
 Component:  Documentation  |   Version:  1.0  
Resolution: |  Keywords:  reference
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10091: QuerySet documentation of slicing syntax misleading/incomplete

[Django]

#10091: QuerySet  documentation of slicing syntax misleading/incomplete
+---
  Reporter:  adrian_nye | Owner:  nobody  
Status:  new| Milestone:  1.1 
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  QuerySet
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

Re: [Django] #10087: Missing models.py in django.contrib.localflavor.fr

[Django]

#10087: Missing models.py in django.contrib.localflavor.fr
-+--
  Reporter:  lstep   | Owner:  nobody
Status:  new | Milestone:
 Component:  django.contrib.localflavor  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by jacob):

  * stage:  Unreviewed => Accepted

Comment:

 Yup, documentation and tests will be required to check this in.

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

[Django]

#10084: RadioSelect documentation leaves out a lot of details
+---
  Reporter:  mark0978   | Owner:  nobody 
Status:  new| Milestone:  1.1
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords:  RadioSelect
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

Re: [Django] #10083: Site __unicode__ value should be the name of the instance instead of the domain.

[Django]

#10083: Site __unicode__ value should be the name of the instance instead of the
domain.
---+
  Reporter:  sethtrain | Owner:  nobody
Status:  closed| Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Let's just leave this as is. If we change it, six months from now we'll
 just get a ticket suggesting that the domain would be more useful.

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

Re: [Django] #10188: HttpResponse does not filter CR/LF characters from headers

[Django]

#10188: HttpResponse does not filter CR/LF characters from headers
+---
  Reporter:  bthomas| Owner:  rokclimb15
Status:  new| Milestone:  1.1   
 Component:  HTTP handling  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Comment (by bthomas):

 I discussed security implications with Jacob already; I'd rather not add
 any details here :)

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

[Django]

#10082: Attribute BaseFormetSet.ordered_forms is broken with blank formsets
+---
  Reporter:  Petr Marhoun   | Owner:  
nobody
Status:  new| Milestone:  
1.1   
 Component:  Forms  |   Version:  
SVN   
Resolution: |  Keywords:

 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

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

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

Re: [Django] #10080: call_command doesn't take into account command's default options

[Django]

#10080: call_command doesn't take into account command's default options
-+--
  Reporter:  alexkoshelev| Owner:  alexkoshelev
Status:  new | Milestone:  1.1 
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

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

Re: [Django] #10079: [trivial, patch] Make template.context usable outside of Django

[Django]

#10079: [trivial, patch] Make template.context usable outside of Django
--+-
  Reporter:  kcarnold | Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  Template system  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by jacob):

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

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

Re: [Django] #10077: Chinese translation error in django.po

[Django]

#10077: Chinese translation error in django.po
---+
  Reporter:  wizun...@gmail.com| Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Can you please provide this change as an actual patch?

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

Re: [Django] #10074: Can't delete objects with lazy GenericRelations

[Django]

#10074: Can't delete objects with lazy GenericRelations
---+
  Reporter:  clay  | Owner:  nobody 
   
Status:  new   | Milestone:  1.1
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:|  Keywords:  
genericrelation delete
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * milestone:  => 1.1

Comment:

 I'm pretty sure the bug here is that generic relations aren't correctly
 accepting strings and need an actual class.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10073: Collapsed fields in admin break Save as new functionality

[Django]

#10073: Collapsed fields in admin break Save as new functionality
---+
  Reporter:  Uninen| Owner:  nobody 
 
Status:  new   | Milestone:  1.1
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  admin, saveasnew, 
saveas
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

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

Re: [Django] #10071: month and day lookup arguments should be integers

[Django]

#10071: month and day lookup arguments should be integers
+---
  Reporter:  leosoto| Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:  jython
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10068: Search box at top of the page on doc site

[Django]

#10068: Search box at top of the page on doc site
--+-
  Reporter:  phoebebright | Owner:  nobody  
Status:  new  | Milestone:  1.1 
 Component:  Django Web site  |   Version:  1.0 
Resolution:   |  Keywords:  search,documentation
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by jacob):

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

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

Re: [Django] #10065: url patterns exception message missing space

[Django]

#10065: url patterns exception message missing space
+---
  Reporter:  Matthew Flanagan   | 
Owner:  nobody
Status:  new| 
Milestone:  1.1   
 Component:  Core framework |   
Version:  1.0   
Resolution: |  
Keywords:
 Stage:  Accepted   | 
Has_patch:  1 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10188: HttpResponse does not filter CR/LF characters from headers

[Django]

#10188: HttpResponse does not filter CR/LF characters from headers
+---
  Reporter:  bthomas| Owner:  rokclimb15
Status:  new| Milestone:  1.1   
 Component:  HTTP handling  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * stage:  Design decision needed => Accepted
  * 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] #10262: Allow to clear object before deleting to avoid data loss because delete cascade behaviour

[Django]

#10262: Allow to clear object before deleting to avoid data loss because delete
cascade behaviour
---+
  Reporter:  msaelices | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Duplicate of #7539

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

[Django]

#9970: Add a mod_wsgi page to the Django docs
+---
  Reporter:  Alex   | Owner:  Alex
Status:  new| Milestone:  1.1 
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by rokclimb15):

 * cc: rokclimb15 (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] #10188: HttpResponse does not filter CR/LF characters from headers

[Django]

#10188: HttpResponse does not filter CR/LF characters from headers
-+--
  Reporter:  bthomas | Owner:  rokclimb15
Status:  new | Milestone:
 Component:  HTTP handling   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by rokclimb15):

  * owner:  nobody => rokclimb15
  * needs_tests:  0 => 1
  * stage:  Unreviewed => Design decision needed

Comment:

 I think this is an excellent idea from a security perspective.  This will
 eliminate the possibility of HTTP response splitting in Django apps.  I
 will test this patch over the weekend and seek a design decision on
 whether or not it should be included.

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

[Django]

#10321: Dont hardcode form label html.
-+--
  Reporter:  MockSoul| Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by rokclimb15):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

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

Re: [Django] #10046: ModPythonHandler class should check for IOError when writing response

[Django]

#10046: ModPythonHandler class should check for IOError when writing response
-+--
  Reporter:  ewoudenberg | Owner:  nobody
Status:  new | Milestone:
 Component:  HTTP handling   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ewoudenberg):

 Replying to [comment:8 jacob]:

 On its behalf: Without this change we get several Apache 500 errors per
 day (on a 50K hit-per-day website). Since the change is added to handle an
 expected condition (remote client closing the socket prematurely) I think
 it is better to include it, even with the caveat that the upper layer
 (mis-)handling of this error, when uncaught, still needs to be understood.
 Graham?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10063: postgres dbshell asks for password even though I have .pgpass

[Django]

#10063: postgres dbshell asks for password even though I have .pgpass
---+
  Reporter:  walter+dja...@wjd.nu  | Owner:  nobody 
   
Status:  new   | Milestone:  1.1
   
 Component:  django-admin.py   |   Version:  SVN
   
Resolution:|  Keywords:  dbshell postgres 
psql password
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10059: New admin formfield_for_dbfield doesn't play nice with subclassing

[Django]

#10059: New admin formfield_for_dbfield doesn't play nice with subclassing
---+
  Reporter:  Alex  | Owner:  Alex
Status:  new   | Milestone:  1.1 
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Wow, I never knew `mro` existed. Learn something new every day.

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

[Django]

#10057: ModelAdmin.render_change_form should not override the 'has_delete' 
option
---+
  Reporter:  rajeesh   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:  wontfix   |  Keywords:  ModelAdmin 
render_change_form
 Stage:  Unreviewed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 A better approach would be to just make a custom template for the model in
 question; see http://docs.djangoproject.com/en/dev/ref/contrib/admin
 /#overriding-admin-templates

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

[Django]

#10056: Problem with non-ASCII characters in FilePathField in contrib.admin
+---
  Reporter:  andrew.mcmu...@ifi.uio.no  | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  django.contrib.admin   |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

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

Re: [Django] #10055: Documentation clarification

[Django]

#10055: Documentation clarification
+---
  Reporter:  TLS| Owner:  nobody 
Status:  new| Milestone:  1.1
 Component:  Documentation  |   Version:  1.0
Resolution: |  Keywords:  URLconf
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10053: Incorrect pydoc in django.template.loaders.app_directories.load_template_source

[Django]

#10053: Incorrect pydoc in
django.template.loaders.app_directories.load_template_source
--+-
  Reporter:  kylev| Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  Template system  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by jacob):

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

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

Re: [Django] #10048: Check for no timezone in dateformat.py

[Django]

#10048: Check for no timezone in dateformat.py
-+--
  Reporter:  claudep | Owner:  nobody
Status:  new | Milestone:  1.1   
 Component:  Core framework  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

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

Re: [Django] #10047: TemporaryFile.seek has bad interface under Windows NT

[Django]

#10047: TemporaryFile.seek has bad interface under Windows NT
---+
  Reporter:  ftartag...@h-umus.it  | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10046: ModPythonHandler class should check for IOError when writing response

[Django]

#10046: ModPythonHandler class should check for IOError when writing response
-+--
  Reporter:  ewoudenberg | Owner:  nobody
Status:  new | Milestone:
 Component:  HTTP handling   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * stage:  Unreviewed => Design decision needed

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

Re: [Django] #10043: widthratio tag does not accept a variable as the max_width argument

[Django]

#10043: widthratio tag does not accept a variable as the max_width argument
--+-
  Reporter:  obeattie | Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  Template system  |   Version:  1.0   
Resolution:   |  Keywords:  widthratio
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by jacob):

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

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

Re: [Django] #10372: get_svn_version() should be more robust

[Django]

#10372: get_svn_version() should be more robust
-+--
  Reporter:  rjaarts | Owner:  nobody   

Status:  new | Milestone:  1.1  

 Component:  Core framework  |   Version:  1.0  

Resolution:  |  Keywords:  version Google App 
Engine GAE
 Stage:  Unreviewed  | Has_patch:  0

Needs_docs:  0   |   Needs_tests:  0

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

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

Comment:

 This isn't a feature and thus isn't for the 1.1 beta.

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

[Django]

#6464: memcached cache backend incr/decr not implemented
--+-
  Reporter:  pa...@fragstore.net  | Owner:  nobody  
 
Status:  new  | Milestone:  1.1 beta
 
 Component:  Cache system |   Version:  SVN 
 
Resolution:   |  Keywords:  cache memcached 
incr decr
 Stage:  Accepted | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Comment (by mmalone):

 I agree w/ Jacob, and feel the same way about much of the memcache API.
 While some of the operations may not be "general" caching primitives,
 nearly all of them are extremely useful caching primitives. The memcache
 API is pretty simple, and if memcache implements a particular API and
 Django doesn't, I think it's worth seriously questioning why.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10038: BaseModelFormSet's method save_existing_objects uses form.changed_data instead of form.has_changed()

[Django]

#10038: BaseModelFormSet's method save_existing_objects uses form.changed_data
instead of form.has_changed()
---+
  Reporter:  karihre   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Forms |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

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

Re: [Django] #10036: admin list_display with broken foreignkey fails

[Django]

#10036: admin list_display with broken foreignkey fails
---+
  Reporter:  danros| Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Indeed; Django isn't happy with invalid references, and you shouldn't be
 either. A nasty error is exactly what I'd expect to see in this case.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, 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] #10034: FormWizard has a security_hash check failure with Textareas with leading/trailing newlines in Safari

[Django]

#10034: FormWizard has a security_hash check failure with Textareas with
leading/trailing newlines in Safari
---+
  Reporter:  danaspiegel   | Owner:  nobody 
  
Status:  new   | Milestone:  1.1
  
 Component:  django.contrib.formtools  |   Version:  1.0
  
Resolution:|  Keywords:  security_hash 
textarea formwizard
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

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

Re: [Django] #10032: ORM switches incorrectly to OUTER JOIN in certain cases with isnull=True

[Django]

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

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

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

Re: [Django] #10031: Recommend against Windows/SQLite < 3.3.6 much more strongly

[Django]

#10031: Recommend against Windows/SQLite < 3.3.6 much more strongly
+---
  Reporter:  russellm   | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * summary:  Test failures with DateFields and DecimalField under Windows
  and Python 2.5 => Recommend against
  Windows/SQLite < 3.3.6 much more strongly
  * stage:  Unreviewed => Accepted
  * component:  Database layer (models, ORM) => Documentation
  * milestone:  => 1.1

Old description:

> The aggregation and aggregation_regress system tests fail due to problems
> with DateFields and DecimalFields under Windows and Python 2.5
>
> The problem manifests as the following failures:
> {{{
> ==
> FAIL: Doctest: modeltests.aggregation.models.__test__.API_TESTS
> --
> Traceback (most recent call last):
>   File "d:\u\kmt\django\aggregation\django\test\_doctest.py", line 2180,
> in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for
> modeltests.aggregation.models.__test__.API_TESTS
>   File
> "D:\u\kmt\django\aggregation\tests\modeltests\aggregation\models.py",
> line unknown line number, in API_TESTS
>
> --
> File
> "D:\u\kmt\django\aggregation\tests\modeltests\aggregation\models.py",
> line ?, in modeltests.aggregation.models.__test__.API_TESTS
> Failed example:
> Book.objects.filter(pk=1).annotate(mean_age=Avg('authors__age')).values()
> Expected:
> [{'rating': 4.5, 'isbn': u'159059725', 'name': u'The Definitive Guide
> to Django: Web Development Done Right', 'pubdate': datetime.date(2007,
> 12, 6), 'price': Decimal("30..."), 'id': 1, 'publisher_id': 1, 'pages':
> 447, 'mean_age': 34.5}]
> Got:
> [{'rating': 4.5, 'isbn': u'159059725', 'name': u'The Definitive Guide
> to Django: Web Development Done Right', 'pubdate': u'2007-12-06',
> 'price': 30, 'id': 1, 'publisher_id': 1, 'pages': 447, 'mean_age': 34.5}]
> --
> File
> "D:\u\kmt\django\aggregation\tests\modeltests\aggregation\models.py",
> line ?, in modeltests.aggregation.models.__test__.API_TESTS
> Failed example:
> Book.objects.filter(pk=1).values().annotate(mean_age=Avg('authors__age'))
> Expected:
> [{'rating': 4.5, 'isbn': u'159059725', 'name': u'The Definitive Guide
> to Django: Web Development Done Right', 'pubdate': datetime.date(2007,
> 12, 6), 'price': Decimal("30..."), 'id': 1, 'publisher_id': 1, 'pages':
> 447, 'mean_age': 34.5}]
> Got:
> [{'rating': 4.5, 'isbn': u'159059725', 'name': u'The Definitive Guide
> to Django: Web Development Done Right', 'pubdate': u'2007-12-06',
> 'price': 30, 'id': 1, 'publisher_id': 1, 'pages': 447, 'mean_age': 34.5}]
>

> ==
> FAIL: Doctest:
> regressiontests.aggregation_regress.models.__test__.API_TESTS
> --
> Traceback (most recent call last):
>   File "d:\u\kmt\django\aggregation\django\test\_doctest.py", line 2180,
> in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for
> regressiontests.aggregation_regress.models.__test__.API_TESTS
>   File
> "D:\u\kmt\django\aggregation\tests\regressiontests\aggregation_regress\models.py",
> line unknown line number, in API_TESTS
>
> --
> File
> "D:\u\kmt\django\aggregation\tests\regressiontests\aggregation_regress\models.py",
> line ?, in regressiontests.aggregation_regress.models.__test__.API_TESTS
> Failed example:
> sorted(Book.objects.all().annotate(mean_auth_age=Avg('authors__age')).extra(select={'manufacture_cost'
> : 'price * .5'}).get(pk=2).__dict__.items())
> Expected:
> [('id', 2), ('isbn', u'067232959'), ('manufacture_cost',
> ...11.545...), ('mean_auth_age', 45.0), ('name', u'Sams Teach Yourself
> Django in 24 Hours'), ('pages', 528), ('price', Decimal("23.09")),
> ('pubdate', datetime.date(2008, 3, 3)), ('publisher_id', 2), ('rating',
> 3.0)]
> Got:
> [('id', 2), ('isbn', u'067232959'), ('manufacture_cost', 11.545),
> ('mean_auth_age', 45.0), ('name', u'Sams Teach Yourself Django in 24
> Hours'), ('pages', 528), ('price', 23.09), ('pubdate', u'2008-03-03'),
> 

Re: [Django] #10028: Incorrect SQL join construction

[Django]

#10028: Incorrect SQL join construction
---+
  Reporter:  brian | Owner:  mtredinnick
Status:  new   | Milestone:  1.1
 Component:  Database layer (models, ORM)  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10026: Possible error in django.contrib.auth.views.password_reset_confirm

[Django]

#10026: Possible error in django.contrib.auth.views.password_reset_confirm
-+--
  Reporter:  jwmayfield  | Owner:  nobody
Status:  new | Milestone:  1.1   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  password reset
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

Comment:

 In the future, please generate patches from the root of the SVN tree.
 There are 22 files in the Django tree named "views.py", and without
 knowing to which one this patch applies it took a bit of time to figure
 out what you were trying to fix here.

 I'm also fairly sure this patch just papers over the problem and doesn't
 get to the root cause. Can you share more details about your setup to help
 us reproduce this?

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

Re: [Django] #10018: Small mistake in django.core.management.base.BaseCommand.__doc__

[Django]

#10018: Small mistake in django.core.management.base.BaseCommand.__doc__
+---
  Reporter:  dswistowski| 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 jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10016: Cache middleware with memcached can't handle long URLs

[Django]

#10016: Cache middleware with memcached can't handle long URLs
---+
  Reporter:  jacob | Owner:  tim
Status:  assigned  | Milestone:  1.1
 Component:  Cache system  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10011: Updates to Thai translations

[Django]

#10011: Updates to Thai translations
---+
  Reporter:  KayEss| Owner:  nobody 
Status:  new   | Milestone:  1.1
 Component:  Translations  |   Version:  SVN
Resolution:|  Keywords:  thai th
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Unreviewed => Accepted
  * 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] #10002: Data does not display in TabularInline when validation fails for an ImageField

[Django]

#10002: Data does not display in TabularInline when validation fails for an
ImageField
---+
  Reporter:  anonymous | Owner:  nobody 
  
Status:  new   | Milestone:  1.1
  
 Component:  django.contrib.admin  |   Version:  1.0
  
Resolution:|  Keywords:  TabularInline, 
ImageField
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

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

Re: [Django] #9886: File-like interface for HttpRequest

[Django]

#9886: File-like interface for HttpRequest
-+--
  Reporter:  isagalaev   | Owner:  mtredinnick  
Status:  new | Milestone:   
 Component:  HTTP handling   |   Version:  1.0  
Resolution:  |  Keywords:  streaming request
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  1   |   Needs_tests:  1
Needs_better_patch:  0   |  
-+--
Comment (by jacob):

 I marked this DDN because I want a second opinion before this gets
 accepted; bringing it to django-dev is one way for you to prod that
 process along.

 However, since this is a feature addition it would need to be in the beta
 to get into 1.1, and there's a long list of other features we decided upon
 earlier in the release process. So realistically if this gets in it'll be
 1.2.

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

[Django]

#10263: order_by parameter for inlineformset_factory and BaseInlineFormSet
-+--
  Reporter:  Paulo Scardine   | Owner:  
nobody  
Status:  new | Milestone:   
   
 Component:  Forms   |   Version:  
1.0 
Resolution:  |  Keywords:  
inlineformset_factory BaseInlineFormSet inline model formset
 Stage:  Design decision needed  | Has_patch:  
1   
Needs_docs:  0   |   Needs_tests:  
0   
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 At first it also looked like a good idea to pass a queryset ready.

 But giving it some thought to this issue, my opinion changed. I think the
 purpose of inlineformset_factory is very specific: making a formset linked
 by the parent_model PK.

 So what is the point of passing a queryset as argument? If it is for
 flexibility, it seems out of place, because we should address the common
 use case and not the exception.

 If you could make the point for a broader solution I will be happy to
 provide a patch.

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