Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  
raw-id-fields nfa-someday design_ux
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

 #13221 was submitted with an alternate 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13221: Enhanced version of RawId related fields for admin

[Django]

#13221: Enhanced version of RawId related fields for admin
---+
  Reporter:  IsakovAN  | Owner:  nobody
Status:  closed| Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Duplicte of #7028.

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

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

Re: [Django] #13224: style of m2m readonly_fields in admin change_form

[Django]

#13224: style of m2m readonly_fields in admin change_form
-+--
  Reporter:  benc| Owner:   
  
Status:  new | Milestone:   
  
 Component:  User Experience |   Version:  1.2-beta 
  
Resolution:  |  Keywords:  admin, 
readonly_fields, m2m
 Stage:  Design decision needed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  wontfix|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 In short, no, I don't have any ideas. If you want to follow this up, I
 suggest starting a thread in django-developers. It's a non-trivial topic,
 and it's going to require a lot of thought and discussion if we're going
 to get it right. Trac isn't the best place to have this discussion.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] r12863 - django/branches/releases/1.1.X/docs/topics/i18n

[noreply]

Author: gwilson
Date: 2010-03-26 19:14:44 -0500 (Fri, 26 Mar 2010)
New Revision: 12863

Modified:
   django/branches/releases/1.1.X/docs/topics/i18n/internationalization.txt
Log:
[1.1.X] Fixed #13189 -- Fixed typo in code example, thanks to gabrielhurley for 
patch.

Backport of r12862 from trunk.


Modified: 
django/branches/releases/1.1.X/docs/topics/i18n/internationalization.txt
===
--- django/branches/releases/1.1.X/docs/topics/i18n/internationalization.txt
2010-03-27 00:14:10 UTC (rev 12862)
+++ django/branches/releases/1.1.X/docs/topics/i18n/internationalization.txt
2010-03-27 00:14:44 UTC (rev 12863)
@@ -486,7 +486,7 @@
 
 To use the catalog, just pull in the dynamically generated script like this::
 
-
+
 
 This uses reverse URL lookup to find the URL of the JavaScript catalog view.
 When the catalog is loaded, your JavaScript code can use the standard

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

[noreply]

Author: gwilson
Date: 2010-03-26 19:14:10 -0500 (Fri, 26 Mar 2010)
New Revision: 12862

Modified:
   django/trunk/docs/topics/i18n/internationalization.txt
Log:
Fixed #13189 -- Fixed typo in code example, thanks to gabrielhurley for patch.


Modified: django/trunk/docs/topics/i18n/internationalization.txt
===
--- django/trunk/docs/topics/i18n/internationalization.txt  2010-03-27 
00:10:44 UTC (rev 12861)
+++ django/trunk/docs/topics/i18n/internationalization.txt  2010-03-27 
00:14:10 UTC (rev 12862)
@@ -488,7 +488,7 @@
 
 To use the catalog, just pull in the dynamically generated script like this::
 
-
+
 
 This uses reverse URL lookup to find the URL of the JavaScript catalog view.
 When the catalog is loaded, your JavaScript code can use the standard

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] r12861 - django/branches/releases/1.1.X/docs/ref/contrib

[noreply]

Author: gwilson
Date: 2010-03-26 19:10:44 -0500 (Fri, 26 Mar 2010)
New Revision: 12861

Modified:
   django/branches/releases/1.1.X/docs/ref/contrib/index.txt
Log:
[1.1.X] Fixed #13202 -- Documented required libraries for markup template tags, 
based on patch from steveed.

Backport of r12860 from trunk.


Modified: django/branches/releases/1.1.X/docs/ref/contrib/index.txt
===
--- django/branches/releases/1.1.X/docs/ref/contrib/index.txt   2010-03-27 
00:07:31 UTC (rev 12860)
+++ django/branches/releases/1.1.X/docs/ref/contrib/index.txt   2010-03-27 
00:10:44 UTC (rev 12861)
@@ -133,22 +133,27 @@
 
 A collection of template filters that implement common markup languages:
 
-* ``textile`` -- implements `Textile`_
-* ``markdown`` -- implements `Markdown`_
+* ``textile`` -- implements `Textile`_ -- requires `PyTextile`_
+* ``markdown`` -- implements `Markdown`_ -- requires `Python-markdown`_
 * ``restructuredtext`` -- implements `ReST (ReStructured Text)`_
+  -- requires `doc-utils`_
 
 In each case, the filter expects formatted markup as a string and returns a
 string representing the marked-up text. For example, the ``textile`` filter
 converts text that is marked-up in Textile format to HTML.
 
 To activate these filters, add ``'django.contrib.markup'`` to your
-:setting:`INSTALLED_APPS` setting. Once you've done that, use ``{% load markup 
%}`` in
-a template, and you'll have access to these filters. For more documentation,
-read the source code in django/contrib/markup/templatetags/markup.py.
+:setting:`INSTALLED_APPS` setting. Once you've done that, use
+``{% load markup %}`` in a template, and you'll have access to these filters.
+For more documentation, read the source code in
+:file:`django/contrib/markup/templatetags/markup.py`.
 
 .. _Textile: http://en.wikipedia.org/wiki/Textile_%28markup_language%29
 .. _Markdown: http://en.wikipedia.org/wiki/Markdown
 .. _ReST (ReStructured Text): http://en.wikipedia.org/wiki/ReStructuredText
+.. _PyTextile: http://loopcore.com/python-textile/
+.. _Python-markdown: http://www.freewisdom.org/projects/python-markdown
+.. _doc-utils: http://docutils.sf.net/
 
 redirects
 =

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

[noreply]

Author: gwilson
Date: 2010-03-26 19:07:31 -0500 (Fri, 26 Mar 2010)
New Revision: 12860

Modified:
   django/trunk/docs/ref/contrib/index.txt
Log:
Fixed #13202 -- Documented required libraries for markup template tags, based 
on patch from steveed.


Modified: django/trunk/docs/ref/contrib/index.txt
===
--- django/trunk/docs/ref/contrib/index.txt 2010-03-26 23:56:56 UTC (rev 
12859)
+++ django/trunk/docs/ref/contrib/index.txt 2010-03-27 00:07:31 UTC (rev 
12860)
@@ -118,7 +118,7 @@
 A world-class geospatial framework built on top of Django, that enables
 storage, manipulation and display of spatial data.
 
-See the :ref:`ref-contrib-gis` documentation for more. 
+See the :ref:`ref-contrib-gis` documentation for more.
 
 humanize
 
@@ -143,22 +143,27 @@
 
 A collection of template filters that implement common markup languages:
 
-* ``textile`` -- implements `Textile`_
-* ``markdown`` -- implements `Markdown`_
+* ``textile`` -- implements `Textile`_ -- requires `PyTextile`_
+* ``markdown`` -- implements `Markdown`_ -- requires `Python-markdown`_
 * ``restructuredtext`` -- implements `ReST (ReStructured Text)`_
+  -- requires `doc-utils`_
 
 In each case, the filter expects formatted markup as a string and returns a
 string representing the marked-up text. For example, the ``textile`` filter
 converts text that is marked-up in Textile format to HTML.
 
 To activate these filters, add ``'django.contrib.markup'`` to your
-:setting:`INSTALLED_APPS` setting. Once you've done that, use ``{% load markup 
%}`` in
-a template, and you'll have access to these filters. For more documentation,
-read the source code in django/contrib/markup/templatetags/markup.py.
+:setting:`INSTALLED_APPS` setting. Once you've done that, use
+``{% load markup %}`` in a template, and you'll have access to these filters.
+For more documentation, read the source code in
+:file:`django/contrib/markup/templatetags/markup.py`.
 
 .. _Textile: http://en.wikipedia.org/wiki/Textile_%28markup_language%29
 .. _Markdown: http://en.wikipedia.org/wiki/Markdown
 .. _ReST (ReStructured Text): http://en.wikipedia.org/wiki/ReStructuredText
+.. _PyTextile: http://loopcore.com/python-textile/
+.. _Python-markdown: http://www.freewisdom.org/projects/python-markdown
+.. _doc-utils: http://docutils.sf.net/
 
 messages
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] r12859 - django/branches/releases/1.1.X/django/contrib/markup/templatetags

[noreply]

Author: gwilson
Date: 2010-03-26 18:56:56 -0500 (Fri, 26 Mar 2010)
New Revision: 12859

Modified:
   django/branches/releases/1.1.X/django/contrib/markup/templatetags/markup.py
Log:
[1.1.X] Removed out-of-date statement in markdown templatetags docstring (refs 
#1204).

Backport of r12858 from trunk.


Modified: 
django/branches/releases/1.1.X/django/contrib/markup/templatetags/markup.py
===
--- django/branches/releases/1.1.X/django/contrib/markup/templatetags/markup.py 
2010-03-26 23:56:08 UTC (rev 12858)
+++ django/branches/releases/1.1.X/django/contrib/markup/templatetags/markup.py 
2010-03-26 23:56:56 UTC (rev 12859)
@@ -9,9 +9,6 @@
   http://www.freewisdom.org/projects/python-markdown
 
 * ReStructuredText, which requires docutils from http://docutils.sf.net/
-
-In each case, if the required library is not installed, the filter will
-silently fail and return the un-marked-up text.
 """
 
 from django import template

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

[noreply]

Author: gwilson
Date: 2010-03-26 18:56:08 -0500 (Fri, 26 Mar 2010)
New Revision: 12858

Modified:
   django/trunk/django/contrib/markup/templatetags/markup.py
Log:
Removed out-of-date statement in markdown templatetags docstring (refs #1204).


Modified: django/trunk/django/contrib/markup/templatetags/markup.py
===
--- django/trunk/django/contrib/markup/templatetags/markup.py   2010-03-26 
23:38:05 UTC (rev 12857)
+++ django/trunk/django/contrib/markup/templatetags/markup.py   2010-03-26 
23:56:08 UTC (rev 12858)
@@ -9,9 +9,6 @@
   http://www.freewisdom.org/projects/python-markdown
 
 * ReStructuredText, which requires docutils from http://docutils.sf.net/
-
-In each case, if the required library is not installed, the filter will
-silently fail and return the un-marked-up text.
 """
 
 from django import template

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

Re: [Django] #10863: Email full stack traces like in the debug error pages

[Django]

#10863: Email full stack traces like in the debug error pages
-+--
  Reporter:  boxed   | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  stack, errors, email
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  1   
Needs_better_patch:  1   |  
-+--
Changes (by obeattie):

 * cc: obeattie (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-upda...@googlegroups.com.
To unsubscribe from this group, 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] r12857 - in django/trunk: django/contrib/admin tests/regressiontests/admin_inlines

[noreply]

Author: gwilson
Date: 2010-03-26 18:38:05 -0500 (Fri, 26 Mar 2010)
New Revision: 12857

Modified:
   django/trunk/django/contrib/admin/helpers.py
   django/trunk/tests/regressiontests/admin_inlines/models.py
   django/trunk/tests/regressiontests/admin_inlines/tests.py
Log:
Fixed #13174 -- Fixed missing field label for `readonly_fields` when used in 
`StackedInline`, thanks to benc for the report and ptone for the investigation 
and initial patch.
 * Corrected `InlineAdminForm.__init__` to pass along `model_admin` parameter 
in `super` call.
 * Lookup the field label in the form's model, not the `model_admin` model.


Modified: django/trunk/django/contrib/admin/helpers.py
===
--- django/trunk/django/contrib/admin/helpers.py2010-03-26 20:14:53 UTC 
(rev 12856)
+++ django/trunk/django/contrib/admin/helpers.py2010-03-26 23:38:05 UTC 
(rev 12857)
@@ -140,7 +140,7 @@
 if not self.is_first:
 attrs["class"] = "inline"
 name = forms.forms.pretty_name(
-label_for_field(self.field, self.model_admin.model, 
self.model_admin)
+label_for_field(self.field, self.form._meta.model, 
self.model_admin)
 )
 contents = force_unicode(escape(name)) + u":"
 return mark_safe('%(contents)s' % {
@@ -232,7 +232,7 @@
 self.original_content_type_id = 
ContentType.objects.get_for_model(original).pk
 self.show_url = original and hasattr(original, 'get_absolute_url')
 super(InlineAdminForm, self).__init__(form, fieldsets, 
prepopulated_fields,
-readonly_fields)
+readonly_fields, model_admin)
 
 def __iter__(self):
 for name, options in self.fieldsets:

Modified: django/trunk/tests/regressiontests/admin_inlines/models.py
===
--- django/trunk/tests/regressiontests/admin_inlines/models.py  2010-03-26 
20:14:53 UTC (rev 12856)
+++ django/trunk/tests/regressiontests/admin_inlines/models.py  2010-03-26 
23:38:05 UTC (rev 12857)
@@ -38,11 +38,13 @@
 class Inner(models.Model):
 dummy = models.IntegerField()
 holder = models.ForeignKey(Holder)
+readonly = models.CharField("Inner readonly label", max_length=1)
 
 
 class InnerInline(admin.StackedInline):
 model = Inner
 can_delete = False
+readonly_fields = ('readonly',) # For bug #13174 tests.
 
 
 class Holder2(models.Model):

Modified: django/trunk/tests/regressiontests/admin_inlines/tests.py
===
--- django/trunk/tests/regressiontests/admin_inlines/tests.py   2010-03-26 
20:14:53 UTC (rev 12856)
+++ django/trunk/tests/regressiontests/admin_inlines/tests.py   2010-03-26 
23:38:05 UTC (rev 12857)
@@ -4,6 +4,7 @@
 from models import Holder, Inner, InnerInline
 from models import Holder2, Inner2, Holder3, Inner3
 
+
 class TestInline(TestCase):
 fixtures = ['admin-views-users.xml']
 
@@ -29,6 +30,15 @@
 actual = inner_formset.can_delete
 self.assertEqual(expected, actual, 'can_delete must be equal')
 
+def test_readonly_stacked_inline_label(self):
+"""Bug #13174."""
+holder = Holder.objects.create(dummy=42)
+inner = Inner.objects.create(holder=holder, dummy=42, readonly='')
+response = self.client.get('/test_admin/admin/admin_inlines/holder/%i/'
+   % holder.id)
+self.assertContains(response, 'Inner readonly label:')
+
+
 class TestInlineMedia(TestCase):
 fixtures = ['admin-views-users.xml']
 
@@ -63,4 +73,4 @@
 change_url = '/test_admin/admin/admin_inlines/holder2/%i/' % holder.id
 response = self.client.get(change_url)
 self.assertContains(response, 'my_awesome_admin_scripts.js')
-self.assertContains(response, 'my_awesome_inline_scripts.js')
\ No newline at end of file
+self.assertContains(response, 'my_awesome_inline_scripts.js')

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

Re: [Django] #13226: Documentation error for custom auth form docs

[Django]

#13226: Documentation error for custom auth form docs
+---
  Reporter:  rokclimb15 | Owner:  nobody  
Status:  new| Milestone:  1.2 
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  get_user
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

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

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

Re: [Django] #13225: new object with readonly m2m field through an error in the admin

[Django]

#13225: new object with readonly m2m field through an error in the admin
---+
  Reporter:  benc  | Owner:  nobody 

Status:  closed| Milestone: 

 Component:  django.contrib.admin  |   Version:  1.2-beta   

Resolution:  duplicate |  Keywords:  admin, 
readonly_fields, m2m
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 This is a dupe of #13004.

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

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

Re: [Django] #13223: ValueError with inline and save as new

[Django]

#13223: ValueError with inline and save as new
---+
  Reporter:  lucalenardi   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:  admin, save-as-new
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 #10448 was an earlier ticket in the same area, but it does not seem to
 have addressed the inline 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-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13226: Documentation error for custom auth form docs

[Django]

#13226: Documentation error for custom auth form docs
---+
 Reporter:  rokclimb15 |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Documentation  | Version:  SVN   
 Keywords:  get_user   |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 {{{
 This form must accept a request keyword argument in its __init__ method,
 and provide a get_user argument which returns the authenticated user
 object...
 }}}

 {{{
 This form must accept a request keyword argument in its __init__ method,
 and provide a get_user method which returns the authenticated user
 object...
 }}}

 Patch is attached

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

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

Re: [Django] #13202: Contrib/Markup documentation should mention requirement for external libraries

[Django]

#13202: Contrib/Markup documentation should mention requirement for external
libraries
+---
  Reporter:  hunajakippo| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by steveed):

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

Comment:

 Added the required libraries.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13225: new object with readonly m2m field through an error in the admin

[Django]

#13225: new object with readonly m2m field through an error in the admin
-+--
 Reporter:  benc |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.admin | Version:  1.2-beta  
 Keywords:  admin, readonly_fields, m2m  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 I have a model with m2m field that I want to be readonly.

 I want the admin user to be able to see this field but not edit it and
 I'll populate it in the model save method.

 When trying to create a new model instance I'm getting:

 {{{
 instance needs to have a primary key value before a many-to-many
 relationship can be used.
 }}}


 It should be able to just put an empty string or None in the readonly
 field.

 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-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13224: style of m2m readonly_fields in admin change_form

[Django]

#13224: style of m2m readonly_fields in admin change_form
-+--
 Reporter:  benc |   Owner:
   Status:  new  |   Milestone:
Component:  User Experience  | Version:  1.2-beta  
 Keywords:  admin, readonly_fields, m2m  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 When setting readononly_fields on a m2m field we get a comma separate list
 of the m2m objects.

 I think that it's easier to read when each object is in a newline.

 At least, each object can be wrapped with a  so it will be possible to style it.

 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-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13223: ValueError with inline and save as new

[Django]

#13223: ValueError with inline and save as new
--+-
 Reporter:  lucalenardi   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:  admin, save-as-new|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Given two models that are related to each other with a foreign key, as
 follows:

 {{{
 class Post(models.Model):
 title = models.CharField()
 slug = models.CharField(max_length=200, unique = True)

 class Block(models.Model):
 post = models.ForeignKey(Post)
 slug = models.CharField(max_length=200, unique = True)
 }}}

 Suppose you have set {{{ save_as = true }}} in the admin.py for the class
 PostAdmin. When you try to create a new Post, generated from an existing
 one with the "save as new" button after correcting some validation errors,
 the following exception is being generated:
 {{{ ValueError: invalid literal for int() with base 10: '' }}}

 If you take a look at the request POST parameters, you could find some
 empty values for the block_set-N-post block_set-N-id (FK and id).

 To replicate the error, follow this sequence:

   1. Create a new object with at least one inline
   2. Save it as new with some validation errors
   3. Try to save it again, after correcting the errors of the form

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

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

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

[Django]

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

 * cc: gorsky@gmail.com (added)

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  wontfix|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by harm):

 Yeah, I get (now) that this can't be solved for views that actually
 require translation.

 Its rather unfortunate though , that using i18n renders the '''complete'''
 site 0% cachable. (except  media/) Even parts of the site that are not
 related to i18n at all.
 I really feel this is an undesired situation

 I still wonder if adding some settings/parameters. to LocaleMiddleWare can
 improve the current situation.
 For example:  the ability to exclude/include apps (by means of urls)  from
 LocaleMiddleware. this prevents LocaleMiddleware from touching the session
 for urls where you as site builder you don't want translations.

 That would give the freedom to explicitly control (if desired) what parts
 of your site you want to i18n enable. (or the reverse which parts of you
 site you want to exclude). All possible with backwards compatibility.

 Any thoughts ?

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

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

Re: [Django] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
+---
  Reporter:  teepark| Owner:  nobody
Status:  reopened   | Milestone:
 Component:  HTTP handling  |   Version:
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by teepark):

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

Comment:

 Replying to [comment:5 ubernostrum]:
 > Duplicate of #7581, which is already open for dealing with issues
 related to iterators/generators in response content.
 >
 > In the future please search existing tickets before opening new ones.

 I did search through and I saw that ticket. #7581 deals with
 HttpResponse.content, which accesses `_container` directly, so is
 orthogonal to iteration behavior. My patch won't fix #7581, and fixing
 #7581 won't help this 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
+---
  Reporter:  teepark| Owner:  nobody
Status:  closed | Milestone:
 Component:  HTTP handling  |   Version:
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 Duplicate of #7581, which is already open for dealing with issues related
 to iterators/generators in response content.

 In the future please search existing tickets before opening new ones.

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

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

Re: [Django] #13204: `values()` returns empty list after `extra(order_by)`

[Django]

#13204: `values()` returns empty list after `extra(order_by)`
---+
  Reporter:  adurdin   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by gabrielhurley):

 Ah, very interesting bug report there. Thanks Karen! I like the comment
 "This function never fails.
 Accordingly, it will mask exceptions raised in either method." That's just
 asking for trouble. Ha!

 Perhaps, since 2.6.1 is installed on Snow Leopard by default, a note
 somewhere in the docs would be helpful... like a small item in:

 http://docs.djangoproject.com/en/1.1/intro/install/#install-python

 Pointing out the problem might save a few people. While it seems obvious
 that outdated bugfix releases of Python are going to have bugs, it seems
 like this particular one might be worth noting since it may affect a fair
 number of people.

 Just a thought.

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

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

Re: [Django] #13204: `values()` returns empty list after `extra(order_by)`

[Django]

#13204: `values()` returns empty list after `extra(order_by)`
---+
  Reporter:  adurdin   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 The Python bug that swallows any exceptions raised by `__len__` is here:
 http://bugs.python.org/issue1242657

 We have run into trouble with it before, see #7786. Malcolm notes in one
 of the comments that he tried at one point to avoid doing anything in
 `__len__` that could raise an exception but that had terrible performance
 impacts. Given that, I'm not sure there is much we can do 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13204: `values()` returns empty list after `extra(order_by)`

[Django]

#13204: `values()` returns empty list after `extra(order_by)`
---+
  Reporter:  adurdin   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

 * cc: gabrielhurley (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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
+---
  Reporter:  teepark| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by teepark):

 * cc: travis.par...@gmail.com (removed)

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

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

Re: [Django] #13204: `values()` returns empty list after `extra(order_by)`

[Django]

#13204: `values()` returns empty list after `extra(order_by)`
---+
  Reporter:  adurdin   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by gabrielhurley):

 I wouldn't be surprised if this is another instance of the Python 2.6.1
 bug I encountered the other day on #13171 and #13172... I never did
 pinpoint it, but it had something to do with the exception not bubbling up
 through the __len__ method of QuerySet in django.db.models.query.

 I did a stacktrace from where the error was supposed to be raised and
 found that it ran through this line of code, which is where the Exception
 vanishes:

 
http://code.djangoproject.com/browser/django/trunk/django/db/models/query.py#L81

 When the queryset is converted to a list there, it calls __len__, the
 exception disappears, and an empty list is returned instead of the
 FieldError (or whichever error you're looking for). Raising the error
 manually before that line will return the error, raising it after that
 line of code it is simply ignored. I spent over an hour hacking at the
 Django code to try and fix it to no avail. The bug was pretty clearly in
 Python itself.

 Upgrading Python to a more recent version is my solution. Though it seems
 this problem is gonna keep popping up since 2.6.1 is the default Snow
 Leopard install.

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

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

Re: [Django] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
+---
  Reporter:  teepark| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by teepark):

 * cc: travis.par...@gmail.com (added)

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

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

Re: [Django] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
+---
  Reporter:  teepark| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by teepark):

  * version:  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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
+---
  Reporter:  teepark| Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by teepark):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13222: unexpected HttpResponse iteration behavior

[Django]

#13222: unexpected HttpResponse iteration behavior
---+
 Reporter:  teepark|   Owner:  nobody
   Status:  new|   Milestone:
Component:  HTTP handling  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 For all the builtin iterables, and most from libraries, the `__iter__`
 method returns something representing one and only one iteration.
 `django.http.HttpResponse.__iter__` sets an iterator attribute on itself,
 then returns self (it also defines a `next` method so it is its own
 iterator). This is bad behavior for an iterable and causes problems when
 trying to do anything but basic iteration.

 A use case (and where I encountered this issue) is in a WSGI server that
 pulls off the first item in the iterable app return value, prefixes
 anything that was sent via `write` calls, and then rebuilds the iterable
 with `itertools.chain`:

 {{{
 if prefix:
 body_iterator = iter(body)
 try:
 first_chunk = body_iterator.next()
 except StopIteration:
 first_chunk = ''
 body = itertools.chain((prefix + first_chunk,), body_iterator)
 }}}

 Using `django.core.handlers.wsgi.WSGIHandler` (which just returns the
 HttpResponse, since it's iterable) with this server, the first chunk of
 the HttpResponse gets doubled because `itertools.chain` calls `iter` on
 its arguments, and that resets the HttpResponse's iterator.

 To compare with some builtins and other libraries:

 {{{
 >>> it = iter(["foobar"])
 >>> list(it), list(it)
 (['foobar'], [])
 >>> it = iter("foobar" for i in [1])
 >>> list(it), list(it)
 (['foobar'], [])
 >>> import werkzeug
 >>> it = iter(werkzeug.Response("foobar").response)
 >>> list(it), list(it)
 (['foobar'], [])
 >>> import webob
 >>> it = iter(webob.Response("foobar").app_iter)
 >>> list(it), list(it)
 (['foobar'], [])
 >>> import django.http
 >>> it = iter(django.http.HttpResponse("foobar"))
 >>> list(it), list(it)
 (['foobar'], ['foobar'])
 }}}

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

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

Re: [Django] #13204: `values()` returns empty list after `extra(order_by)`

[Django]

#13204: `values()` returns empty list after `extra(order_by)`
---+
  Reporter:  adurdin   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by adurdin):

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

Comment:

 I can still reproduce this on a fresh project, on both django 1.1.1 and
 trunk (revision 12855). I was running with python 2.6.1, with both mysql
 5.0.77 and sqlite 3.6.12, all running on Mac OS X 10.6.2. I will attach
 the minimal project to this ticket for reference.

 You are right, the expected result for each of the three statements is a
 `FieldError`.

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

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

Re: [Django] #13070: Wrong exception on django.contrib.gis from SVN

[Django]

#13070: Wrong exception on django.contrib.gis from SVN
+---
  Reporter:  Guilherme Gondim (semente)   |   
  Owner:  nobody   
Status:  reopened   | 
Milestone:  1.2  
 Component:  GIS|   
Version:  SVN  
Resolution: |  
Keywords:  geodjango
 Stage:  Accepted   | 
Has_patch:  0
Needs_docs:  0  |   
Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by steveed):

 I was unable to reproduce this error:

 I am using:
 Xubuntu 9.10
 Django version 1.2 beta 1 SVN-12855
 sqlite 3.6.16
 spatialite 2.3.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-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13221: Enhanced version of RawId related fields for admin

[Django]

#13221: Enhanced version of RawId related fields for admin
--+-
 Reporter:  IsakovAN  |   Owner:  nobody
   Status:  new   |   Milestone:  1.3   
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Changes:
 1) RawIdField becomes readonly
 2) Add ability to open related objects, clicking on it label
 3) Update related label when dismissing related popup
 4) Add ability to clear field(individual links for ManyToMany 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13219: contrib.flatpages needs tests

[Django]

#13219: contrib.flatpages needs tests
---+
  Reporter:  bjunix| Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Contrib apps  |   Version:  1.1 
Resolution:|  Keywords:  flatpages, tests
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by faldridge):

 Hi, bjunix.  It seems there is some overlap here with ticket #6932.  In
 #6932, Mnewman added a new template tag to the flatpages app with unit
 tests.

 In the course of working on that ticket, he noticed the lack of tests for
 the flatpages app in general and already started filling in the gaps.

 It would probably be most convenient to start from there, and just added
 tests for trailing and leading slashes to the existing test suite.

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

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

Re: [Django] #11956: ReverseManyRelatedObjectsDescriptor wrongly assumes symmetry between inherited objects

[Django]

#11956: ReverseManyRelatedObjectsDescriptor wrongly assumes symmetry between
inherited objects
---+
  Reporter:  nidi  | Owner:  malcalypse
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by malcalypse):

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

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

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

Re: [Django] #13220: Documentation on pre- and post-save/delete hooks misses key arguments

[Django]

#13220: Documentation on pre- and post-save/delete hooks misses key arguments
+---
  Reporter:  nikoftime  | Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  1.2-beta  
   
Resolution:  invalid|  Keywords:  pre save, post save, 
hook, delete hook, save hook
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 What you've found isn't current Django documentation; it's documentation
 from the 0.96 era. It #13201 covers the process of deprecating these
 documentation pages.

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

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

Re: [Django] #11025: [patch] Ability to specify LOGIN_URL as full qualified absolute URL, ex: https://passport.example.com/passport?mode=login

[Django]

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

 I've updated patch according to comment of Russel. Is it OK now?

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

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

Re: [Django] #13219: contrib.flatpages needs tests

[Django]

#13219: contrib.flatpages needs tests
---+
  Reporter:  bjunix| Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Contrib apps  |   Version:  1.1 
Resolution:|  Keywords:  flatpages, tests
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

Comment:

 Some elaboration for the benefit of anyone interested in pursuing this:
  - There is both the flatpages view and the flatpages middleware to
 consider
  - Most of the edge cases revolve around the first few lines of the
 flatpages view, where ambiguities in trailing and leading slashes are
 resolved. Historically, this has been the cause of a couple of bug
 reports.

 All that is really needed is path coverage of the view and middleware.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13220: Documentation on pre- and post-save/delete hooks misses key arguments

[Django]

#13220: Documentation on pre- and post-save/delete hooks misses key arguments
---+
 Reporter:  nikoftime  |   Owner:  
nobody
   Status:  new|   Milestone:  
1.2   
Component:  Documentation  | Version:  
1.2-beta  
 Keywords:  pre save, post save, hook, delete hook, save hook  |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 The documentation at
 http://www.djangoproject.com/documentation/models/save_delete_hooks/

 Has the following code example:
 {{{
 from django.db import models

 class Person(models.Model):
 first_name = models.CharField(max_length=20)
 last_name = models.CharField(max_length=20)

 def __unicode__(self):
 return u"%s %s" % (self.first_name, self.last_name)

 def save(self):
 print "Before save"
 super(Person, self).save() # Call the "real" save() method
 print "After save"

 def delete(self):
 print "Before deletion"
 super(Person, self).delete() # Call the "real" delete() method
 print "After deletion"
 }}}

 However, using method definitions like these to override
 models.Model.save() and .delete() causes some problems with the optional
 arguments to both functions.
 A better way to do this might be to have the method signatures use *args,
 and **kwargs, so that arguments to these overridden methods are properly
 passed to the parent method implementations:

 {{{
 from django.db import models

 class Person(models.Model):
 first_name = models.CharField(max_length=20)
 last_name = models.CharField(max_length=20)

 def __unicode__(self):
 return u"%s %s" % (self.first_name, self.last_name)

 def save(self, *args, **kwargs):
 print "Before save"
 super(Person, self).save(*args, **kwargs) # Call the "real" save()
 method
 print "After save"

 def delete(self, *args, **kwargs):
 print "Before deletion"
 super(Person, self).delete(*args, **kwargs) # Call the "real"
 delete() method
 print "After deletion"
 }}}

 This also helps future-proof overridden method implementations to changes
 in the Django core.

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

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

Re: [Django] #13087: m2m_changed fires before a clear but after add/remove

[Django]

#13087: m2m_changed fires before a clear but after add/remove
---+
  Reporter:  rcatherman| Owner:  nobody  
Status:  new   | Milestone:  1.2 
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta
Resolution:|  Keywords:  
 Stage:  Design decision needed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by malcalypse):

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

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

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

Re: [Django] #13219: contrib.flatpages needs tests

[Django]

#13219: contrib.flatpages needs tests
---+
  Reporter:  bjunix| Owner:  nobody  
Status:  new   | Milestone:  
 Component:  Contrib apps  |   Version:  1.1 
Resolution:|  Keywords:  flatpages, tests
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by bjunix):

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

Comment:

 Flatpages is a rather minimal app so I guess only few tests need to get
 written.

 On django-users[1] Russel stated there are a couple of edge cases to be
 considered. I can't think of any straight away, but they could get summed
 up here.

 [1] http://groups.google.com/group/django-
 users/browse_thread/thread/157afb4fbf668f18

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13219: contrib.flatpages needs tests

[Django]

#13219: contrib.flatpages needs tests
--+-
 Reporter:  bjunix|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Contrib apps  | Version:  1.1   
 Keywords:  flatpages, tests  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 There aren't any tests for the contrib.flatpages app.

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

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

Re: [Django] #10302: Add some date features to aggregation

[Django]

#10302: Add some date features to aggregation
--+-
  Reporter:  tolano   | Owner:   
Status:  new  | Milestone:   
 Component:  ORM aggregation  |   Version:  SVN  
Resolution:   |  Keywords:  aggregation dates
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Comment (by kmpm):

 I made a method something like this in a manager.
 When I didn't have that last .order_by things went mad as for @gmayer but
 as soon as I added my own order I could put back the ordering in the
 model's Meta class.
 Don't know if will help but it's a workaround if you need ordering in the
 Meta class.

 def period_avrage(self, start_at=None, end_at=None, period_size='day'):
 extra_psql={'period': "DATE_TRUNC('%s',
 \"collector_taglog\".\"created_at\")" % period_size}
 qs = self.filter(data_good=True) #only good values
 if start_at: qs = qs.filter(created_at__gte=start_at)
 if end_at: qs = qs.filter(created_at__lte=end_at)
 #do not remove the order by. Otherwise the ordering on the model will
 screw things up
 return
 
qs.extra(select=extra_psql).values('period').annotate(avg=Avg('v_num')).order_by('period')

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

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

Re: [Django] #13174: readonly_fields in StackedInline forms in the admin are missing the field label.

[Django]

#13174: readonly_fields in StackedInline forms in the admin are missing the 
field
label.
---+
  Reporter:  benc  | Owner:  gwilson

Status:  new   | Milestone:  1.2

 Component:  django.contrib.admin  |   Version:  1.2-beta   

Resolution:|  Keywords:  admin, forms, 
inline, label
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * owner:  anonymous => gwilson
  * status:  assigned => new

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

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

Re: [Django] #13174: readonly_fields in StackedInline forms in the admin are missing the field label.

[Django]

#13174: readonly_fields in StackedInline forms in the admin are missing the 
field
label.
---+
  Reporter:  benc  | Owner:  anonymous  

Status:  assigned  | Milestone:  1.2

 Component:  django.contrib.admin  |   Version:  1.2-beta   

Resolution:|  Keywords:  admin, forms, 
inline, label
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

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

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

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

[noreply]

Author: russellm
Date: 2010-03-26 10:15:55 -0500 (Fri, 26 Mar 2010)
New Revision: 12855

Modified:
   django/branches/releases/1.1.X/django/core/handlers/base.py
   
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/middleware.py
   
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/tests.py
Log:
[1.1.X] Fixed #12594 -- Ensured that a meaningful exception is raised when the 
urlconf_module is None. Thanks to buriy for the report and patch.

Backport of r12854 from trunk.

Modified: django/branches/releases/1.1.X/django/core/handlers/base.py
===
--- django/branches/releases/1.1.X/django/core/handlers/base.py 2010-03-26 
15:08:24 UTC (rev 12854)
+++ django/branches/releases/1.1.X/django/core/handlers/base.py 2010-03-26 
15:15:55 UTC (rev 12855)
@@ -172,6 +172,9 @@
 request_repr = "Request repr() unavailable"
 message = "%s\n\n%s" % (self._get_traceback(exc_info), request_repr)
 mail_admins(subject, message, fail_silently=True)
+# If Http500 handler is not installed, re-raise last exception
+if resolver.urlconf_module is None:
+raise exc_info[1], None, exc_info[2]
 # Return an HttpResponse that displays a friendly error message.
 callback, param_dict = resolver.resolve500()
 return callback(request, **param_dict)

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/middleware.py
===
--- 
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/middleware.py
  2010-03-26 15:08:24 UTC (rev 12854)
+++ 
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/middleware.py
  2010-03-26 15:15:55 UTC (rev 12855)
@@ -5,3 +5,7 @@
 class ChangeURLconfMiddleware(object):
 def process_request(self, request):
 request.urlconf = urlconf_inner.__name__
+
+class NullChangeURLconfMiddleware(object):
+def process_request(self, request):
+request.urlconf = None

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/tests.py
===
--- 
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/tests.py
   2010-03-26 15:08:24 UTC (rev 12854)
+++ 
django/branches/releases/1.1.X/tests/regressiontests/urlpatterns_reverse/tests.py
   2010-03-26 15:15:55 UTC (rev 12855)
@@ -17,6 +17,7 @@
 import unittest
 
 from django.conf import settings
+from django.core.exceptions import ImproperlyConfigured
 from django.core.urlresolvers import reverse, resolve, NoReverseMatch, 
Resolver404
 from django.http import HttpResponseRedirect, HttpResponsePermanentRedirect
 from django.shortcuts import redirect
@@ -276,3 +277,16 @@
 response = self.client.get('/second_test/')
 self.assertEqual(response.status_code, 200)
 self.assertEqual(response.content, 'outer:,inner:/second_test/')
+
+def test_urlconf_overridden_with_null(self):
+settings.MIDDLEWARE_CLASSES += (
+'%s.NullChangeURLconfMiddleware' % middleware.__name__,
+)
+self.assertRaises(ImproperlyConfigured, self.client.get, '/test/me/')
+
+class NoRootUrlConfTests(TestCase):
+"""Tests for handler404 and handler500 if urlconf is None"""
+urls = None
+
+def test_no_handler_exception(self):
+self.assertRaises(ImproperlyConfigured, self.client.get, '/test/me/')

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

[noreply]

Author: russellm
Date: 2010-03-26 10:08:24 -0500 (Fri, 26 Mar 2010)
New Revision: 12854

Modified:
   django/trunk/django/core/handlers/base.py
   django/trunk/tests/regressiontests/urlpatterns_reverse/middleware.py
   django/trunk/tests/regressiontests/urlpatterns_reverse/tests.py
Log:
Fixed #12594 -- Ensured that a meaningful exception is raised when the 
urlconf_module is None. Thanks to buriy for the report and patch.

Modified: django/trunk/django/core/handlers/base.py
===
--- django/trunk/django/core/handlers/base.py   2010-03-25 20:01:40 UTC (rev 
12853)
+++ django/trunk/django/core/handlers/base.py   2010-03-26 15:08:24 UTC (rev 
12854)
@@ -173,6 +173,9 @@
 request_repr = "Request repr() unavailable"
 message = "%s\n\n%s" % (self._get_traceback(exc_info), request_repr)
 mail_admins(subject, message, fail_silently=True)
+# If Http500 handler is not installed, re-raise last exception
+if resolver.urlconf_module is None:
+raise exc_info[1], None, exc_info[2]
 # Return an HttpResponse that displays a friendly error message.
 callback, param_dict = resolver.resolve500()
 return callback(request, **param_dict)

Modified: django/trunk/tests/regressiontests/urlpatterns_reverse/middleware.py
===
--- django/trunk/tests/regressiontests/urlpatterns_reverse/middleware.py
2010-03-25 20:01:40 UTC (rev 12853)
+++ django/trunk/tests/regressiontests/urlpatterns_reverse/middleware.py
2010-03-26 15:08:24 UTC (rev 12854)
@@ -5,3 +5,7 @@
 class ChangeURLconfMiddleware(object):
 def process_request(self, request):
 request.urlconf = urlconf_inner.__name__
+
+class NullChangeURLconfMiddleware(object):
+def process_request(self, request):
+request.urlconf = None

Modified: django/trunk/tests/regressiontests/urlpatterns_reverse/tests.py
===
--- django/trunk/tests/regressiontests/urlpatterns_reverse/tests.py 
2010-03-25 20:01:40 UTC (rev 12853)
+++ django/trunk/tests/regressiontests/urlpatterns_reverse/tests.py 
2010-03-26 15:08:24 UTC (rev 12854)
@@ -17,6 +17,7 @@
 import unittest
 
 from django.conf import settings
+from django.core.exceptions import ImproperlyConfigured
 from django.core.urlresolvers import reverse, resolve, NoReverseMatch, 
Resolver404
 from django.http import HttpResponseRedirect, HttpResponsePermanentRedirect
 from django.shortcuts import redirect
@@ -282,16 +283,22 @@
 self.assertEqual(response.status_code, 200)
 self.assertEqual(response.content, 'outer:,inner:/second_test/')
 
+def test_urlconf_overridden_with_null(self):
+settings.MIDDLEWARE_CLASSES += (
+'%s.NullChangeURLconfMiddleware' % middleware.__name__,
+)
+self.assertRaises(ImproperlyConfigured, self.client.get, '/test/me/')
+
 class ErrorHandlerResolutionTests(TestCase):
 """Tests for handler404 and handler500"""
-
+
 def setUp(self):
 from django.core.urlresolvers import RegexURLResolver
 urlconf = 'regressiontests.urlpatterns_reverse.urls_error_handlers'
 urlconf_callables = 
'regressiontests.urlpatterns_reverse.urls_error_handlers_callables'
 self.resolver = RegexURLResolver(r'^$', urlconf)
 self.callable_resolver = RegexURLResolver(r'^$', urlconf_callables)
-
+
 def test_named_handlers(self):
 from views import empty_view
 handler = (empty_view, {})
@@ -303,3 +310,10 @@
 handler = (empty_view, {})
 self.assertEqual(self.callable_resolver.resolve404(), handler)
 self.assertEqual(self.callable_resolver.resolve500(), handler)
+
+class NoRootUrlConfTests(TestCase):
+"""Tests for handler404 and handler500 if urlconf is None"""
+urls = None
+
+def test_no_handler_exception(self):
+self.assertRaises(ImproperlyConfigured, self.client.get, '/test/me/')

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

Re: [Django] #13087: m2m_changed fires before a clear but after add/remove

[Django]

#13087: m2m_changed fires before a clear but after add/remove
---+
  Reporter:  rcatherman| Owner:  malcalypse
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta  
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by malcalypse):

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

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

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

Re: [Django] #11916: Extra params + aggregation creates incorrect SQL.

[Django]

#11916: Extra params + aggregation creates incorrect SQL.
---+
  Reporter:  jaklaas...@gmail.com  | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 Not critical for 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11890: Defer/only + annotate is broken

[Django]

#11890: Defer/only + annotate is broken
---+
  Reporter:  jaklaas...@gmail.com  | Owner:  ruosteinen
Status:  assigned  | Milestone:  1.3   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * milestone:  1.2 => 1.3

Comment:

 Not critical for 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11811: No error raised on update(foreignkey=unsavedobject) on nullable fk

[Django]

#11811: No error raised on update(foreignkey=unsavedobject) on nullable fk
---+
  Reporter:  Afief | Owner:  ashearer
Status:  assigned  | Milestone:  1.3 
 Component:  Database layer (models, ORM)  |   Version:  1.1 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  1 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * milestone:  1.2 => 1.3

Comment:

 Not critical for 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11716: Various methods in django.db.models.fields don't wrap ValueErrors and allow them to escape

[Django]

#11716: Various methods in django.db.models.fields don't wrap ValueErrors and 
allow
them to escape
---+
  Reporter:  Leo   | Owner:  Leo
Status:  assigned  | Milestone:  1.3
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * milestone:  1.2 => 1.3

Comment:

 Not critical for 1.3

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

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

Re: [Django] #11333: ORA-01830 date format picture ends before converting entire input

[Django]

#11333: ORA-01830 date format picture ends before converting entire input
---+
  Reporter:  jtiai | Owner:  nobody 

Status:  new   | Milestone:  1.3

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

Resolution:|  Keywords:  oracle 
date formats
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

  * milestone:  => 1.3

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

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

Re: [Django] #11333: ORA-01830 date format picture ends before converting entire input

[Django]

#11333: ORA-01830 date format picture ends before converting entire input
---+
  Reporter:  jtiai | Owner:  nobody 

Status:  new   | Milestone: 

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

Resolution:|  Keywords:  oracle 
date formats
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

  * milestone:  1.2 =>

Comment:

 Not critical for 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  wontfix|  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Replying to [comment:8 harm]:
 > Should we allow LocalMiddleware to read out a session via a backdoor?
 (because the LocalMiddleware _knows_ that it only looks at the language,
 and that it adds the correct Vary: Content-Language  anyway. So that as
 fas as LocalMiddleware knows, Vary: cookie should not be set.

 Incorrect. It would be true if Django were *only* using the Accept-
 Language header to choose the page language. However, the session *is*
 being read to determine the site language, and a user can modify the site
 language using the i18n views. As a result, this means that Vary: Cookie
 is actually correct. The page *is* varying based on what is in the cookie,
 and as a result, it isn't cacheable independent of the cookie.

 I completely agree that this is annoying from a page caching perspective,
 but I'm not sure I see what we can do about it, other than changing the
 way i18n works so that it doesn't have any dependency on the cookie -- but
 this would mean (1) breaking backwards compatibility, and/or (2) removing
 the ability for users to select their language.

 Regrettably, I'm going to close this wontfix.

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by harm):

 I can't test trunk right now.

 But reading [12546]  and [12624] i don't think they are related. They
 touch django caching stuff. Not the logic when to add Vary: headers

 Thinking about this problem more, its actually quite hard to get this
 right.  Where else as from the session can LocaleMiddleware his info ?
 With the current code ,if it reads the session, than automatically
 session.accessed gets set. If session.accessed is set -> Vary: Cookie is
 added.

 Should we allow LocalMiddleware to read out a session via a backdoor?
 (because the LocalMiddleware _knows_ that it only looks at the language,
 and that it adds the correct Vary: Content-Language  anyway. So that as
 fas as LocalMiddleware knows, Vary: cookie should not be set.

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

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

Re: [Django] #12903: Missing plural forms in admin

[Django]

#12903: Missing plural forms in admin
---+
  Reporter:  stephaner | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  Internationalization  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

  * has_patch:  0 => 1

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 Ok - I can now reproduce. The problem was that I had USE_I18N=False in my
 settings, which meant that the dummy translation functions were being
 used.

 I can verify this also occurs on 1.1, so it isn't a recent change.

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 I don't have time to set up an environment to tests this right now, but
 just wanted to point that 1.2-beta 1 got bundled on Feb 06 and the [12546]
 and [12624] changes were committed after that (Feb 23 and March 01
 respectively). If you are effectively using the beta1 tarball, can you
 retry with a newer SVN checkout?

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

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

Re: [Django] #12924: Pickling QuerySet with related fields fails

[Django]

#12924: Pickling QuerySet with related fields fails
---+
  Reporter:  dmishe| Owner:  Alex
Status:  assigned  | Milestone:  1.2 
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by sjaensch):

 * cc: s...@sjaensch.org (added)

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by harm):

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

Comment:

 I made a copy/past error in the testcase {{{ tests.py }}}  above. (missing
 {{{ vary = response.get('vary',None) }}} )

 {{{
 #!python
 def test_hi(self):
 response = self.client.get('/hi')

 vary = response.get('vary',None)
 if vary:
 print "Vary: %s" % (vary)
 else:
 print " - no vary headers "

 }}}

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  worksforme |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by harm):

 here is a reproducible testcase.

 Start with a new project
 all default, no custom context processors, no custom middleware

 views.y
 {{{
 #!python
 from django.http import HttpResponse
 def hi(request):
  return HttpResponse("hi")
 }}}

 tests.py
 {{{
 #!python
 from django.test import TestCase
 from views import hi

 class SimpleTest(TestCase):
 def test_hi(self):
 response = self.client.get('/hi')
 vary = response.get('vary',None)
   if vary:
  print "Vary: %s" % (vary)
   else:
  print " - no vary headers "
 }}}

 without {{{ django.middleware.locale.LocaleMiddleware }}} issue  {{{
 python manage.py test }}}. The result is
 {{{
 - no vary headers
 }}}


 add   {{{'django.middleware.locale.LocaleMiddleware'}}}  to the
 {{{MIDDLEWARE_CLASSES}}} in {{{settings.py}}} and issue {{{ python
 manage.py test }}} again. Now you get the incorrect result. A Cookie is
 added
 {{{
 Vary: Accept-Language, Cookie
 }}}

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.2-beta
Resolution:  worksforme |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by harm):

  * version:  1.1-beta-1 => 1.2-beta

Comment:

 I selected the incorrect version -> 1.2-beta

 The problem is that the LocaleMiddleware reads the request.session.  The
 Session Middleware later detects that the session was touched
 (session.accessed) and appends the Vary: Cookie header.

 {{{
 #!python
 class LocaleMiddleware(object):
  def process_request(self, request):
 language = translation.get_language_from_request(request)   <-
 accesses session.
 }}}

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

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

Re: [Django] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
+---
  Reporter:  schaefer   | Owner:  nobody
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This isn't entirely true - syndication will honor https:// if it is
 provided in the links that are to be rendered. However, it is true that a
 feed will always assume that the URL scheme is HTTP, regardless of the
 request. The request scheme information is available when add_domain is
 called, so it should be used.

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1-beta-1
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I can't reproduce this. According to my testing, the locale middleware
 adds the "Vary: Accept-Language" and "Content-Language" headers. From a
 visual inspection of the code, I can't see anything that would modify the
 Cookie header.

 If you insist this is happening, you'll need to provide a specific example
 of a view and configuaration that doesn't set Vary: Cookie until you turn
 on the Locale middleware.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
---+
 Reporter:  schaefer   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  RSS framework  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 django-syndication will always use an `http` scheme for feed URLs, even if
 the site is using `https`. This can cause problems when the site is only
 using `https` and redirects all `http` requests to a default page.

 It seems to me that the main "culprit" here is `add_domain`:

 source:django/trunk/django/contrib/syndication/views.py#L11

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

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

Re: [Django] #13215: Random OperationalError when using FastCGI prefork + PostgreSQL

[Django]

#13215: Random OperationalError when using FastCGI prefork + PostgreSQL
-+--
  Reporter:  hcarvalhoalves  | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 I'll accept this, but I wouldn't hold my breath on getting a solution
 unless you can narrow down the cause of the problem. Does it matter what
 the view is doing? Does it happen consistently on the same view? Does it
 only occur under certain load conditions (CPU, memory, or HTTP access
 load)? Does it only occur on long-lived connections? Is the stack trace
 always the same? If it isn't, what is the common element?

 In short, we need *anything* that can make this less random, and more
 repeatable.

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

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

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
+---
  Reporter:  harm   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1-beta-1
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Comment:

 harm,

 Are you really reporting this against 1.1-beta1?. If the answer is no, we
 need the exact release/beta/SVN revision at which you are seeing this.

 #6552 was about a context processor not a middleware. Are you sure you are
 not using the same custom context processor that led you to erroneously
 reopen that ticket?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
---+
 Reporter:  harm   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1-beta-1
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Enabling {{{ django.middleware.locale.LocaleMiddleware }}}  causes that
 django adds a 'Vary: Cookie' header to every reponse.

 The net effects of responses with Vary: Cookie, is that they are not
 properly cached by reverse proxies, and worse, never cached by end
 browsers. (Browser may cache requests with the same cookie, but in reality
 NO browser is implemented like that,

 And this happens for _every_ response

 Is there a way to achieve this without always touching the session ? So
 that we just get a {{{ Vary : Accept-Language }}}

 similar tickets with other middleware #6552

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

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

Re: [Django] #13216: Document the limitations on foreign keys and m2m relations across databases

[Django]

#13216: Document the limitations on foreign keys and m2m relations across 
databases
+---
  Reporter:  russellm   | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, 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] #13216: Document the limitations on foreign keys and m2m relations across databases

[Django]

#13216: Document the limitations on foreign keys and m2m relations across 
databases
---+
 Reporter:  russellm   |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Many of the people investigating the new multi-db functionality are coming
 back to django-users and django-dev asking why they can't have a foreign
 key to an object on a remote database. We need to specifically document
 that this isn't possible (and why it isn't possible).

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

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