Re: [Django] #14174: Support for string interpolation in lazy translation

[Django]

#14174: Support for string interpolation in lazy translation
---+
  Reporter:  zimnyx| Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by zimnyx):

 Hi!

 Let users decide.

 If they want to pass mutable which can later change, and they want
 translation to be always up-to-date with this value, they just pass
 mutable param:
 {{{
 >>> lst = [1,2,3]
 >>> s = ugettext_lazy('Hello %s') % (lst,)
 >>> unicode(s)
 'Hello [1,2,3]'
 >>> lst.append(4)
 >>> unicode(s)
 'Hello [1,2,3,4]'
 }}}
 ... or if they want to see value with its state during creation of lazy:
 {{{
 >>> lst = [1,2,3]
 >>> s = ugettext_lazy('Hello %s') % (lst[:],)
 >>> unicode(s)
 'Hello [1,2,3]'
 >>> lst.append(4)
 >>> unicode(s)
 'Hello [1,2,3]'
 }}}

 I'm not sure about backwards compatibility though... please decide.

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

-- 
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] #11559: urlresolvers.reverse do not work with namespaced urls and captured parameters in parent urlconf

[Django]

#11559: urlresolvers.reverse do not work with namespaced urls and captured
parameters in parent urlconf
+---
  Reporter:  kmik...@gmail.com  | Owner:  nobody
Status:  new| Milestone:
 Component:  Core framework |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Someday/Maybe  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by anonymous):

 * cc: trowb...@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] #14402: help_text is not displayed for ManyToMany raw_id fields

[Django]

#14402: help_text is not displayed for ManyToMany raw_id fields
---+
  Reporter:  tyrion| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   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

Comment:

 The attached fix involves moving the ''"Hold down the Control key..."''
 literal as the default `help_text` from its historically location in the
 model M2M field to the respective form field (`ModelMultipleChoiceField`).
 This way, it's available to the default form widget and the admin-specific
 `FilteredSelectMultiple` widget.

 In IRC discussions, one idea suggested was to push this even more in the
 presentation layer by moving it to the widget realm (that would be more
 correct because it wouldn't force that help text on potential custom
 widgets whose operation doesn't involve selecting things with mouse clicks
 and Contrl/Command keypresses). The only problem I see with this is that
 it would mean we should put and maintain the ''"Hold down the Control
 key..."'' literal in two locations (`SelectMultiple` and
 `FilteredSelectMultiple`). Hopefully the tests contained in the patch are
 of help if this is the chosen path.

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

-- 
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] #7722: EMail Message with CC - Carbon CopyFixed patch

[Django]

#7722: EMail Message with CC - Carbon CopyFixed patch
-+--
  Reporter:  roberto.digirolamo   | Owner:  
nobody
Status:  new | Milestone:   
 
 Component:  django.core.mail|   Version:  
SVN   
Resolution:  |  Keywords:   
 
 Stage:  Ready for checkin   | Has_patch:  
1 
Needs_docs:  0   |   Needs_tests:  
0 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

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

Comment:

 Good changes, doug.

 I modified the docs very slightly:
 http://github.com/SmileyChris/django/compare/master...7722-email-cc

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

-- 
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:  SmileyChris
Status:  assigned| Milestone: 
 Component:  Authentication  |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * owner:  nobody => SmileyChris
  * needs_better_patch:  1 => 0
  * status:  new => assigned

Comment:

 This started as a small change to thasonic's code, then grew into a larger
 fix and some refactoring.

 Better diff can be found here:
 http://github.com/SmileyChris/django/compare/master...11025-absolute-
 login_url

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

-- 
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] #14402: help_text is not displayed for ManyToMany raw_id fields

[Django]

#14402: help_text is not displayed for ManyToMany raw_id fields
---+
  Reporter:  tyrion| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by carljm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * version:  1.2 => SVN
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Yes, not sure what the right solution is, but it should be possible to set
 custom help text for an m2m raw id widget.

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

-- 
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] #14403: Missing/incomplete documentation for FloatField?

[Django]

#14403: Missing/incomplete documentation for FloatField?
-+--
 Reporter:  typeshige   |   Owner:  nobody
   Status:  new  |   Milestone:  1.3   
Component:  Documentation| Version:  1.2   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 [http://docs.djangoproject.com/en/dev/ref/models/fields/#floatfield]

 There is no description of options for model floatfields.

 It invites people to read the release notes for 1.0 for changes, but there
 is no description of what changed as far as I can see.

 [http://docs.djangoproject.com/en/dev/releases/1.0/]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14402: help_text is not displayed for ManyToMany raw_id fields

[Django]

#14402: help_text is not displayed for ManyToMany raw_id fields
--+-
 Reporter:  tyrion|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 {{{
 #!python
 if db_field.name in self.raw_id_fields:
 kwargs['widget'] = widgets.ManyToManyRawIdWidget(db_field.rel,
 using=db)
 kwargs['help_text'] = ''
 }}}
 In `contrib.admin.options.BaseModelAdmin.formfield_for_manytomany` the
 help_text is reset to `""` because otherwise `ManyToManyField.__init__`
 would prependo to it 'Hold down "Control", or "Command"...':
 {{{
 #!python
 msg = _('Hold down "Control", or "Command" on a Mac, to select more than
 one.')
 self.help_text = string_concat(self.help_text, ' ', msg)
 }}}

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

-- 
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] #14401: Add a contributing HOWTO page for new contributors

[Django]

#14401: Add a contributing HOWTO page for new contributors
---+
 Reporter:  gabrielhurley  |   Owner:  gabrielhurley
   Status:  new|   Milestone:  1.3  
Component:  Documentation  | Version:  SVN  
 Keywords:  contributing   |   Stage:  Unreviewed   
Has_patch:  0  |  
---+
 There has been repeated talk of consolidating the "community wisdom" and
 "the spirit of contributing to Django" in a way that's more accessible and
 to-the-point for new users in a way that the current contributing docs may
 not be. Most recently Russell mentioned it in this thread:

 http://groups.google.com/group/django-
 developers/browse_frm/thread/9ebc3e57d539d1ff

 I would like to put such a page in the official docs together, and to that
 end I have created a wiki page to serve as the basis for the eventual
 patch:

 http://code.djangoproject.com/wiki/ContributingHowTo

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

-- 
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] #11941: FilteredMultipleSelect does not render help text

[Django]

#11941: FilteredMultipleSelect does not render help text
+---
  Reporter:  techieone  | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by tyrion):

  * 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] #11941: FilteredMultipleSelect does not render help text

[Django]

#11941: FilteredMultipleSelect does not render help text
+---
  Reporter:  techieone  | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by tyrion):

 The help text is not displayed because `SelectFilter2.js` removes all
 paragraphs that "get in the way".
 {{{
 #!javascript
 // Remove , because it just gets in the way.
 var ps = from_box.parentNode.getElementsByTagName('p');
 for (var i=0; i
Django 
The Web framework for perfectionists with deadlines.

-- 
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] #13914: Add natural keys to contrib.auth.User and Group models

[Django]

#13914: Add natural keys to contrib.auth.User and Group models
-+--
  Reporter:  jbochi  | Owner:  nobody   
   
Status:  new | Milestone:  1.3  
   
 Component:  Authentication  |   Version:  SVN  
   
Resolution:  |  Keywords:  Contrib, Auth, User, 
Group, natural keys
 Stage:  Accepted| Has_patch:  1
   
Needs_docs:  1   |   Needs_tests:  1
   
Needs_better_patch:  0   |  
-+--
Comment (by gabrielhurley):

 Agreed, needs tests and docs, but otherwise the patch seems fine to me.

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

-- 
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] #10944: Site app should be able to make absolute URLs.

[Django]

#10944: Site app should be able to make absolute URLs.
---+
  Reporter:  jdunck| Owner:  laurentluce
Status:  assigned  | Milestone:  1.3
 Component:  Contrib apps  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Changes (by gabrielhurley):

  * needs_better_patch:  0 => 1

Comment:

 Two thoughts:

  1. This method should be available on both Site and RequestSite. Using
 the new `django.contrib.sites.models.get_current_site` function (which
 returns either a Site or RequestSite instance) you could then construct
 full URLs without being tied to the sites framework.

  2. It seems like constructing the full URL is good, but personally I'd
 like to have it add the protocol (http:// or https://) as well. That bit
 is a little bit trickier and may not be within the scope of the Site
 object to know what the right protocol is. It just seems like a halfway-
 there solution to get a full URL but have to manually type the "http://;.

 And, as you already noted, the patch would need docs before it's done.

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

-- 
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] #13749: Link from admin-site to site

[Django]

#13749: Link from admin-site to site
---+
  Reporter:  romankrv  | Owner:  joelklabo
Status:  reopened  | Milestone:  1.3  
 Component:  django.contrib.admin  |   Version:  1.2  
Resolution:|  Keywords:  admin url
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by SmileyChris):

  * needs_better_patch:  0 => 1

Comment:

 This should use the sites framework, and should be .. for
 valid HTML.

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

-- 
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] #14398: runfcgi umask option should use literal value

[Django]

#14398: runfcgi umask option should use literal value
--+-
  Reporter:  petteyg  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by ramiro):

  * has_patch:  0 => 1
  * needs_tests:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 Patch for this issue using the ''radix'' parameter to `int()` taht allows
 to pass octal numbers in the usual `0nnn` notation. Plus associated yak
 shaving: Intended to clarificate of the notations accepted for the `umask`
 `runfcgi` command option docs -> Addition of docs for the command ->
 Modification of our Sphinx customization to accept command options not
 prefixed with `'--'` so the `:djadminopt:` xrefs work as expected.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14391: update man django-admin.1 to include missing commands

[Django]

#14391: update man django-admin.1 to include missing commands
--+-
  Reporter:  laurentluce  | Owner:  laurentluce
Status:  assigned | Milestone:  1.3
 Component:  django-admin.py  |   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by laurentluce):

  * has_patch:  0 => 1

Comment:

 update django-admin man page to match django-admin.txt

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

-- 
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] r13987 - in django/branches/releases/1.2.X: django/contrib/auth django/contrib/auth/tests django/contrib/contenttypes django/contrib/gis/sitemaps django/contrib/sitemaps django/contrib/sit

[noreply]

Author: lukeplant
Date: 2010-10-05 15:31:02 -0500 (Tue, 05 Oct 2010)
New Revision: 13987

Modified:
   django/branches/releases/1.2.X/django/contrib/auth/forms.py
   django/branches/releases/1.2.X/django/contrib/auth/tests/views.py
   django/branches/releases/1.2.X/django/contrib/auth/views.py
   django/branches/releases/1.2.X/django/contrib/contenttypes/tests.py
   django/branches/releases/1.2.X/django/contrib/contenttypes/views.py
   django/branches/releases/1.2.X/django/contrib/gis/sitemaps/views.py
   django/branches/releases/1.2.X/django/contrib/sitemaps/__init__.py
   django/branches/releases/1.2.X/django/contrib/sitemaps/tests/basic.py
   django/branches/releases/1.2.X/django/contrib/sitemaps/views.py
   django/branches/releases/1.2.X/django/contrib/sites/models.py
   django/branches/releases/1.2.X/django/contrib/sites/tests.py
   django/branches/releases/1.2.X/django/contrib/syndication/views.py
   django/branches/releases/1.2.X/docs/ref/contrib/sites.txt
Log:
[1.2.X] Fixed #14386, #8960, #10235, #10909, #10608, #13845, #14377 - 
standardize Site/RequestSite usage in various places.

Many thanks to gabrielhurley for putting most of this together.  Also to
bmihelac, arthurk, qingfeng, hvendelbo, petr.p...@s-cape.cz, Hraban for
reports and some initial patches.

The patch also contains some whitespace/PEP8 fixes.

Backport of [13980] from trunk. Some items could be considered features
(i.e.  supporting RequestSite in various contrib apps), others are definite
bugs, but it was much more robust to backport all these tightly related
changes together.

Modified: django/branches/releases/1.2.X/django/contrib/auth/forms.py
===
--- django/branches/releases/1.2.X/django/contrib/auth/forms.py 2010-10-05 
20:27:11 UTC (rev 13986)
+++ django/branches/releases/1.2.X/django/contrib/auth/forms.py 2010-10-05 
20:31:02 UTC (rev 13987)
@@ -1,7 +1,7 @@
 from django.contrib.auth.models import User
 from django.contrib.auth import authenticate
 from django.contrib.auth.tokens import default_token_generator
-from django.contrib.sites.models import Site
+from django.contrib.sites.models import get_current_site
 from django.template import Context, loader
 from django import forms
 from django.utils.translation import ugettext_lazy as _
@@ -117,14 +117,14 @@
 return email
 
 def save(self, domain_override=None, 
email_template_name='registration/password_reset_email.html',
- use_https=False, token_generator=default_token_generator):
+ use_https=False, token_generator=default_token_generator, 
request=None):
 """
 Generates a one-use only link for resetting password and sends to the 
user
 """
 from django.core.mail import send_mail
 for user in self.users_cache:
 if not domain_override:
-current_site = Site.objects.get_current()
+current_site = get_current_site(request)
 site_name = current_site.name
 domain = current_site.domain
 else:

Modified: django/branches/releases/1.2.X/django/contrib/auth/tests/views.py
===
--- django/branches/releases/1.2.X/django/contrib/auth/tests/views.py   
2010-10-05 20:27:11 UTC (rev 13986)
+++ django/branches/releases/1.2.X/django/contrib/auth/tests/views.py   
2010-10-05 20:31:02 UTC (rev 13987)
@@ -249,6 +249,12 @@
 self.assert_('Logged out' in response.content)
 self.confirm_logged_out()
 
+def test_14377(self):
+# Bug 14377
+self.login()
+response = self.client.get('/logout/')
+self.assertTrue('site' in response.context)
+
 def test_logout_with_next_page_specified(self): 
 "Logout with next_page option given redirects to specified resource"
 self.login()

Modified: django/branches/releases/1.2.X/django/contrib/auth/views.py
===
--- django/branches/releases/1.2.X/django/contrib/auth/views.py 2010-10-05 
20:27:11 UTC (rev 13986)
+++ django/branches/releases/1.2.X/django/contrib/auth/views.py 2010-10-05 
20:31:02 UTC (rev 13987)
@@ -10,7 +10,7 @@
 from django.views.decorators.csrf import csrf_protect
 from django.core.urlresolvers import reverse
 from django.shortcuts import render_to_response, get_object_or_404
-from django.contrib.sites.models import Site, RequestSite
+from django.contrib.sites.models import get_current_site
 from django.http import HttpResponseRedirect, Http404
 from django.template import RequestContext
 from django.utils.http import urlquote, base36_to_int
@@ -26,21 +26,21 @@
 """Displays the login form and handles the login action."""
 
 redirect_to = request.REQUEST.get(redirect_field_name, '')
-
+
 if request.method == "POST":
 form = authentication_form(data=request.POST)
 if form.is_valid():
 # 

[Changeset] r13986 - in django/branches/releases/1.2.X: django/test tests/regressiontests/test_client_regress

[noreply]

Author: lukeplant
Date: 2010-10-05 15:27:11 -0500 (Tue, 05 Oct 2010)
New Revision: 13986

Modified:
   django/branches/releases/1.2.X/django/test/utils.py
   
django/branches/releases/1.2.X/tests/regressiontests/test_client_regress/models.py
Log:
[1.2.X] Fixed #13092 -- Added support for the "in" operator when dealing with 
context lists. Thanks to clelland for the patch.

Backport of [13510] from trunk.  Backported in order to support some other
tests which need to be backported.

Modified: django/branches/releases/1.2.X/django/test/utils.py
===
--- django/branches/releases/1.2.X/django/test/utils.py 2010-10-05 19:41:48 UTC 
(rev 13985)
+++ django/branches/releases/1.2.X/django/test/utils.py 2010-10-05 20:27:11 UTC 
(rev 13986)
@@ -36,6 +36,12 @@
 else:
 return super(ContextList, self).__getitem__(key)
 
+def __contains__(self, key):
+try:
+value = self[key]
+except KeyError:
+return False
+return True
 
 def instrumented_test_render(self, context):
 """

Modified: 
django/branches/releases/1.2.X/tests/regressiontests/test_client_regress/models.py
===
--- 
django/branches/releases/1.2.X/tests/regressiontests/test_client_regress/models.py
  2010-10-05 19:41:48 UTC (rev 13985)
+++ 
django/branches/releases/1.2.X/tests/regressiontests/test_client_regress/models.py
  2010-10-05 20:27:11 UTC (rev 13986)
@@ -620,6 +620,7 @@
 "Context variables can be retrieved from a single context"
 response = self.client.get("/test_client_regress/request_data/", 
data={'foo':'whiz'})
 self.assertEqual(response.context.__class__, Context)
+self.assertTrue('get-foo' in response.context)
 self.assertEqual(response.context['get-foo'], 'whiz')
 self.assertEqual(response.context['request-foo'], 'whiz')
 self.assertEqual(response.context['data'], 'sausage')
@@ -635,6 +636,7 @@
 response = 
self.client.get("/test_client_regress/request_data_extended/", 
data={'foo':'whiz'})
 self.assertEqual(response.context.__class__, ContextList)
 self.assertEqual(len(response.context), 2)
+self.assertTrue('get-foo' in response.context)
 self.assertEqual(response.context['get-foo'], 'whiz')
 self.assertEqual(response.context['request-foo'], 'whiz')
 self.assertEqual(response.context['data'], 'bacon')

-- 
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] #13842: XViewMiddleware fails with class-based views

[Django]

#13842: XViewMiddleware fails with class-based views
-+--
  Reporter:  ch0wn   | Owner:  mk   
   
Status:  assigned| Milestone:  1.3  
   
 Component:  Core framework  |   Version:  SVN  
   
Resolution:  |  Keywords:  middleware 
class-based-views
 Stage:  Accepted| Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

  * keywords:  middleware => middleware class-based-views
  * 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] #6735: Class-based generic views

[Django]

#6735: Class-based generic views
+---
  Reporter:  jkocherhans| Owner:  david
Status:  assigned   | Milestone:  1.3  
 Component:  Generic views  |   Version:   
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  1  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by david):

 Current discussion: http://groups.google.com/group/django-
 developers/browse_thread/thread/27cec79b784ef73f?hl=en

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

-- 
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] #11358: Flatpage sitemap shows all pages, even private pages

[Django]

#11358: Flatpage sitemap shows all pages, even private pages
+---
  Reporter:  dburke | Owner:  kmtracey 
Status:  closed | Milestone:   
 Component:  Contrib apps   |   Version:  1.0  
Resolution:  fixed  |  Keywords:  sprintSep2010
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by lukeplant):

 I backported it now - [13985]

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

-- 
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] r13985 - in django/branches/releases/1.2.X: django/contrib/sitemaps django/contrib/sitemaps/tests docs/ref/contrib

[noreply]

Author: lukeplant
Date: 2010-10-05 14:41:48 -0500 (Tue, 05 Oct 2010)
New Revision: 13985

Modified:
   django/branches/releases/1.2.X/django/contrib/sitemaps/__init__.py
   django/branches/releases/1.2.X/django/contrib/sitemaps/tests/basic.py
   django/branches/releases/1.2.X/django/contrib/sitemaps/tests/urls.py
   django/branches/releases/1.2.X/docs/ref/contrib/sitemaps.txt
Log:
[1.2.X] Fixed #11358: Don't include private flatpages in sitemap. Thanks dburke 
and mlavin.

Backport of [13734] from trunk

Modified: django/branches/releases/1.2.X/django/contrib/sitemaps/__init__.py
===
--- django/branches/releases/1.2.X/django/contrib/sitemaps/__init__.py  
2010-10-05 01:44:12 UTC (rev 13984)
+++ django/branches/releases/1.2.X/django/contrib/sitemaps/__init__.py  
2010-10-05 19:41:48 UTC (rev 13985)
@@ -79,7 +79,7 @@
 def items(self):
 from django.contrib.sites.models import Site
 current_site = Site.objects.get_current()
-return current_site.flatpage_set.all()
+return current_site.flatpage_set.filter(registration_required=False)
 
 class GenericSitemap(Sitemap):
 priority = None

Modified: django/branches/releases/1.2.X/django/contrib/sitemaps/tests/basic.py
===
--- django/branches/releases/1.2.X/django/contrib/sitemaps/tests/basic.py   
2010-10-05 01:44:12 UTC (rev 13984)
+++ django/branches/releases/1.2.X/django/contrib/sitemaps/tests/basic.py   
2010-10-05 19:41:48 UTC (rev 13985)
@@ -1,6 +1,7 @@
 from datetime import date
 from django.conf import settings
 from django.contrib.auth.models import User
+from django.contrib.flatpages.models import FlatPage
 from django.test import TestCase
 from django.utils.formats import localize
 from django.utils.translation import activate
@@ -51,3 +52,26 @@
 http://example.com/users/testuser/
 
 """)
+
+def test_flatpage_sitemap(self):
+"Basic FlatPage sitemap test"
+public = FlatPage.objects.create(
+url=u'/public/',
+title=u'Public Page',
+enable_comments=True,
+registration_required=False,
+)
+public.sites.add(settings.SITE_ID)
+private = FlatPage.objects.create(
+url=u'/private/',
+title=u'Public Page',
+enable_comments=True,
+registration_required=True
+)
+private.sites.add(settings.SITE_ID)
+response = self.client.get('/flatpages/sitemap.xml')
+# Public flatpage should be in the sitemap
+self.assertContains(response, 'http://example.com%s' % 
public.url)
+# Private flatpage should not be in the sitemap
+self.assertNotContains(response, 'http://example.com%s' % 
private.url)
+

Modified: django/branches/releases/1.2.X/django/contrib/sitemaps/tests/urls.py
===
--- django/branches/releases/1.2.X/django/contrib/sitemaps/tests/urls.py
2010-10-05 01:44:12 UTC (rev 13984)
+++ django/branches/releases/1.2.X/django/contrib/sitemaps/tests/urls.py
2010-10-05 19:41:48 UTC (rev 13985)
@@ -1,6 +1,6 @@
 from datetime import datetime
 from django.conf.urls.defaults import *
-from django.contrib.sitemaps import Sitemap, GenericSitemap
+from django.contrib.sitemaps import Sitemap, GenericSitemap, FlatPageSitemap
 from django.contrib.auth.models import User
 
 class SimpleSitemap(Sitemap):
@@ -22,7 +22,12 @@
 }),
 }
 
+flatpage_sitemaps = {
+'flatpages': FlatPageSitemap,
+}
+
 urlpatterns = patterns('django.contrib.sitemaps.views',
 (r'^simple/sitemap\.xml$', 'sitemap', {'sitemaps': simple_sitemaps}),
 (r'^generic/sitemap\.xml$', 'sitemap', {'sitemaps': generic_sitemaps}),
+(r'^flatpages/sitemap\.xml$', 'sitemap', {'sitemaps': flatpage_sitemaps}),
 )

Modified: django/branches/releases/1.2.X/docs/ref/contrib/sitemaps.txt
===
--- django/branches/releases/1.2.X/docs/ref/contrib/sitemaps.txt
2010-10-05 01:44:12 UTC (rev 13984)
+++ django/branches/releases/1.2.X/docs/ref/contrib/sitemaps.txt
2010-10-05 19:41:48 UTC (rev 13985)
@@ -215,8 +215,8 @@
 .. class:: FlatPageSitemap
 
 The :class:`django.contrib.sitemaps.FlatPageSitemap` class looks at all
-:mod:`flatpages ` defined for the current
-:setting:`SITE_ID` (see the
+publicly visible :mod:`flatpages `
+defined for the current :setting:`SITE_ID` (see the
 :mod:`sites documentation `) and
 creates an entry in the sitemap. These entries include only the
 :attr:`~Sitemap.location` attribute -- not :attr:`~Sitemap.lastmod`,

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

Re: [Django] #14389: Future url replacement

[Django]

#14389: Future url replacement
--+-
  Reporter:  seanbrant| Owner:  nobody
Status:  new  | Milestone:  1.3   
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by seanbrant):

 I thought about this, i think its a good idea. URLNode is easy we can
 define a resolve_view method on the class. What do we do about the url
 function? Should we not use parser.compile_filter in the url function and
 just pass the string to URLNode and have resolve_view do
 Variable(self.view_name).resolve(context)?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14389: Future url replacement

[Django]

#14389: Future url replacement
--+-
  Reporter:  seanbrant| Owner:  nobody
Status:  new  | Milestone:  1.3   
 Component:  Template system  |   Version:  1.2   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Alex):

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

Comment:

 There's gotta be a way to do this with less copy-paste.  Perhaps the
 "normal" URLNode can defer resolving the URL name to a method and this can
 just override this to actually consult the context.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14400: Latvian localflavor

[Django]

#14400: Latvian localflavor
---+
  Reporter:  krikulis  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12812: Inheriting from comments breaks comment moderation

[Django]

#12812: Inheriting from comments breaks comment moderation
--+-
  Reporter:  Beetle_B | Owner:  nobody  
   
Status:  reopened | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  1.1 
   
Resolution:   |  Keywords:  comments 
inheritance moderation
 Stage:  Unreviewed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by philgyford):

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

Comment:

 I think there's something up here. I've created a testcase that's as
 simple as I can make it to demonstrate the situation I've come across that
 seems to cause this error.

 This project is an extremely simple weblog, with comments that are
 extended from django.contrib.comments: http://github.com/philgyford
 /django-commentstest/

 As it is, the moderation works fine - if enable_comments on an Entry is
 set to false, then posting a comment is prevented.

 But if you add "from weblog.models import Entry" to either
 customcomments/forms.py or customcomments/models.py, then moderation is
 ignored, and comments can always be posted. (Why would you add this?
 Because you might want to extend the comment class to use something from
 the Entry model.)

 Checking what's happening in django/contrib/comments/__init__.py's
 get_model() function, in the first case it's returning a CommentWithTitle
 class. But in the second case, when moderation isn't working, it's
 returning a standard Comment class.

 I'm too new to Django to know how to proceed with this, and whether this
 really is a bug or it's something I've done, but after a couple of days of
 poking at this (and posting to django-users today), I'm stumped.

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

-- 
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] #14301: django crashes on email address that passed validate_email() (utf8-tld)

[Django]

#14301: django crashes on email address that passed validate_email()  (utf8-tld)
---+
  Reporter:  harm  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.core.mail  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by anonymous):

 I added such test to regressiontests/mail.py and it worked fine.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14399: Site's get_current() not thread safe?

[Django]

#14399: Site's get_current() not thread safe?
+---
  Reporter:  Kronuz | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 No, it appears to me to be fine.  If something you get out of the cache
 gets invalidated during the course of your request there's nothing sane we
 can do about this, *all* caching solutions will suffer from this problem.

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

-- 
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] #14400: Latvian localflavor

[Django]

#14400: Latvian localflavor
--+-
 Reporter:  krikulis  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Contrib apps  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 latvian local flavor, with identity code, postal code and phone number
 phone 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] #14398: runfcgi umask option should use literal value

[Django]

#14398: runfcgi umask option should use literal value
--+-
  Reporter:  petteyg  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  1.2   
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:

 Replying to [ticket:14398 petteyg]:
 > A user on IRC suggested use of ast.literal_eval() instead.
 The `ast` module was added to the stdlib in python 2.6 and Django
 (currently) needs to be compatible with Python 2.4.

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

-- 
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] #14399: Site's get_current() not thread safe?

[Django]

#14399: Site's get_current() not thread safe?
---+
 Reporter:  Kronuz |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Is the Site caching system thread safe? I don't think it is. The patch in
 Ticket #7517 (as well as the code for get_current()) will get invalid or
 deleted sites when Site objects get deleted/updated in other thread other
 than the one using get_current(), since the objects wont get invalidated
 from such other threads to the one making the request.

 I would believe shared memory is needed for that, to invalidate the object
 in all threads (it can be done using a "sync" time in a shared memory
 medium (memcache even))

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

-- 
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] #9666: ssi tag don't works with context variables

[Django]

#9666: ssi tag don't works with context variables
--+-
  Reporter:  andrews  | Owner:  ericholscher  
Status:  assigned | Milestone:  1.3   
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:  tag, ssi, template
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Comment (by seanbrant):

 #14389 is trying to introduce a from future concept for the url tag fixes.
 My latest patch does the same thing for the ssi tag. See #14389 for more
 details.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14395: Error message typo

[Django]

#14395: Error message typo
---+
  Reporter:  agabel| Owner:  agabel
Status:  assigned  | Milestone:  1.3   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by agabel):

  * owner:  nobody => agabel
  * needs_better_patch:  => 0
  * status:  new => assigned
  * needs_tests:  => 0
  * needs_docs:  => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14327: Custom Manager not honored in related queries

[Django]

#14327: Custom Manager not honored in related queries
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mk):

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

Comment:

 Duplicate of #3871

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

-- 
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] #14398: runfcgi umask option should use literal value

[Django]

#14398: runfcgi umask option should use literal value
-+--
 Reporter:  petteyg  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django-admin.py  | Version:  1.2   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The umask option is converted to an int, instead of taken as typed.

 ./manage.py runfcgi umask=0111 (decimal int) creates a socket with umask
 0157 (octal). umask=0022 creates a socket with umask 0026. umask=0027
 creares a socket with umask 0033.

 A user on IRC suggested use of ast.literal_eval() instead.

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

-- 
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] #5590: JSON encoding fails on Promise (result of gettext_lazy)

[Django]

#5590: JSON encoding fails on Promise (result of gettext_lazy)
+---
  Reporter:  jdunck | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Serialization  |   Version:  SVN   
 
Resolution: |  Keywords:  unicode json 
serialization i18n
 Stage:  Ready for checkin  | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: bkonkle (added)
  * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14397: Missing ending quotation in logging documentation

[Django]

#14397: Missing ending quotation in logging documentation
+---
  Reporter:  hunterford | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by hunterford):

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

Comment:

 There's also a missing comma on line 30:

 {{{
 #!python
 'class': 'django.utils.log.AdminEmailHandler'
 }}}

 should become:

 {{{
 #!python
 'class': 'django.utils.log.AdminEmailHandler',
 }}}

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

-- 
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] #14397: Missing ending quotation in logging documentation

[Django]

#14397: Missing ending quotation in logging documentation
---+
 Reporter:  hunterford |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The logging documentation contains a missing ending quotation mark in the
 example code snippet located at:
 http://docs.djangoproject.com/en/dev/topics/logging/

 Line 46 of the configuration example:
 {{{
 #!python
 'handlers: ['console', 'mail_admins'],
 }}}

 should be changed to:

 {{{
 #!python
 'handlers': ['console', 'mail_admins'],
 }}}

 Keep up the good work!

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

-- 
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] #14396: Admin generates a query burst on ForeignKey with null = True

[Django]

#14396: Admin generates a query burst on ForeignKey with null = True
---+
  Reporter:  piro  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  1.2
   
Resolution:|  Keywords:  admin database 
performance
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by piro):

  * keywords:  qdmin database performance => admin database performance
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14396: Admin generates a query burst on ForeignKey with null = True

[Django]

#14396: Admin generates a query burst on ForeignKey with null = True
+---
 Reporter:  piro|   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.admin| Version:  1.2   
 Keywords:  qdmin database performance  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 When the The admin loads a list of objects to display the change list, it
 is supposed to
 
[http://docs.djangoproject.com/en/1.2/ref/contrib/admin/#django.contrib.admin.ModelAdmin.list_select_related
 use select_related()] to fetch ForeignKey fields in the display list.

 Because it uses the form select_related() without the filed name,
 
[http://docs.djangoproject.com/en/1.2/ref/models/querysets/#django.db.models.QuerySet.select_related
 the records are not fetched if the property has null=True]. This generates
 a burst of up of 100 query to display the admin page for such a model.

 Attached there is a preliminary patch to fix the issue. It is probably to
 be improved as it doesn't kick in if the model is configured with
 list_select_related=True or if select_related() was already called on the
 query.

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

-- 
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] #14395: Error message typo

[Django]

#14395: Error message typo
--+-
 Reporter:  agabel|   Owner:  nobody
   Status:  new   |   Milestone:  1.3   
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 This seems to be a typo:
 "You must default a 'default' database"

 Should be:
 "You must define a 'default' database"

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

-- 
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] #14126: blocktrans count is parsing incorrectly

[Django]

#14126: blocktrans count is parsing incorrectly
---+
  Reporter:  mark0978  | Owner:  nobody   
Status:  closed| Milestone:   
 Component:  Translations  |   Version:  1.2  
Resolution:  worksforme|  Keywords:  blocktrans plural
 Stage:  Unreviewed| Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by mk):

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

Comment:

 Can't reproduce with attached test.

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

-- 
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] #11256: Fail loudly and clearly when an Annotation alias matches a field name.

[Django]

#11256: Fail loudly and clearly when an Annotation alias matches a field name.
--+-
  Reporter:  donspaulding | Owner: 
Status:  new  | Milestone:  1.3
 Component:  ORM aggregation  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by carljm):

 New patch updates tests to apply post-doctest-removal, and modifies the
 duplicate-alias error message to be a bit more informative (tells you what
 alias is a dupe).

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

-- 
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] #14393: 'Add Another' link appears next to ForeignKey field when user has no permission.

[Django]

#14393: 'Add Another' link appears next to ForeignKey field when user has no
permission.
---+
  Reporter:  menollo   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.2
  
Resolution:  fixed |  Keywords:  foreignkey admin 
add link
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

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

Comment:

 Its fixed in the trunk, see this ticket #1035
 and this changeset r13708

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

-- 
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] #14373: annotate() will gladly delete your data

[Django]

#14373: annotate() will gladly delete your data
--+-
  Reporter:  patrys   | Owner:  carljm
Status:  closed   | Milestone:  1.3   
 Component:  ORM aggregation  |   Version:  1.2   
Resolution:  duplicate|  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by carljm):

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

Comment:

 Closing this as duplicate of #11256. The possible data-loss aspect is new
 here, but the core issue and the fix are the same, and that ticket already
 has a patch.

 There's also the question of m2m-assignment behavior, but that's not
 aggregation-related; filed a separate ticket #14394.

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

-- 
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] #14394: Assigning bad data to an m2m attribute should not clear existing data

[Django]

#14394: Assigning bad data to an m2m attribute should not clear existing data
--+-
 Reporter:  carljm|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 If you assign something nonsensical to a many-to-many attribute on a model
 instance, you'll get a `TypeError`; but not until after Django has cleared
 all the existing relationship data. Ideally Django would verify that
 you've passed in something reasonable before it clears the existing data.

 (This issue was originally half of #14373).

 Attached patch with test demonstrating the issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14393: 'Add Another' link appears next to ForeignKey field when user has no permission.

[Django]

#14393: 'Add Another' link appears next to ForeignKey field when user has no
permission.
---+
  Reporter:  menollo   | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  1.2
  
Resolution:|  Keywords:  foreignkey admin 
add link
 Stage:  Unreviewed| Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * version:  SVN => 1.2
  * needs_tests:  => 0
  * 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.

[Django] #14393: 'Add Another' link appears next to ForeignKey field when user has no permission.

[Django]

#14393: 'Add Another' link appears next to ForeignKey field when user has no
permission.
---+
 Reporter:  menollo|   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  django.contrib.admin   | Version:  SVN   
 Keywords:  foreignkey admin add link  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When I have a model like this:
 {{{
 #!python
 class A(models.Model):
 title = models.CharField(max_length=255)

 class B(models.Model):
 title = models.CharField(max_length=255)
 a = models.ForeignKey(A)
 }}}
 and the user has no permission to add instances of class A.
 The 'Add Another' link is stil visible in the change form (admin) of class
 B. (on click it gives a permission denied page)

 while in the admin homepage, the 'Add' link is not visible at all (for
 that user)... this seems inconsistent.

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

-- 
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] #11256: Fail loudly and clearly when an Annotation alias matches a field name.

[Django]

#11256: Fail loudly and clearly when an Annotation alias matches a field name.
--+-
  Reporter:  donspaulding | Owner: 
Status:  new  | Milestone:  1.3
 Component:  ORM aggregation  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by carljm):

  * milestone:  => 1.3

Comment:

 #14373 reported this same issue, with the additional factor that under
 certain (not yet entirely clear) circumstances with m2m fields, this can
 lead to data loss. Bumping to 1.3 milestone.

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

-- 
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] #14312: list_editable causes 500s for ?p>maximum

[Django]

#14312: list_editable causes 500s for ?p>maximum
---+
  Reporter:  Tuttle| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mk):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * milestone:  => 1.3
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 I see two possible approaches to fix this problem:

 1. Return an EmptyQuerySet instead of a tuple. The changelist still shows
 up, but is empty (at least it does not crash).

 2. Raise an IncorrectLookupParameters exception, all GET parameters are
 reset.

 Assigning milestone 1.3, because this is a reproducible bug which always
 crashes with a 500 Internal Server Error.

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

-- 
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] #14174: Support for string interpolation in lazy translation

[Django]

#14174: Support for string interpolation in lazy translation
---+
  Reporter:  zimnyx| Owner:  nobody
Status:  new   | Milestone:
 Component:  Translations  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mk):

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

Comment:

 You need to extend on your proposal a bit. What should happen in this
 case:

 {{{
 >>> lst = [1,2,3]
 >>> s = ugettext_lazy('Hello %s') % (lst,)
 >>> unicode(s)
 'Hello [1,2,3]'
 >>> lst.append(4)
 >>> unicode(s)
 'Hello [1,2,3]'

 OR

 'Hello [1,2,3,4]'
 }}}

 Would you want to deepcopy all arguments to %?

 I'm not convinced this ticket is worth the trouble though.

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

-- 
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] #14169: Improve TemplateSyntaxError for invalid block tags

[Django]

#14169: Improve TemplateSyntaxError for invalid block tags
--+-
  Reporter:  filipd   | Owner:  nobody  

Status:  new  | Milestone:  

 Component:  Template system  |   Version:  SVN 

Resolution:   |  Keywords:  TemplateSyntaxError, 
exception value
 Stage:  Unreviewed   | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

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

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

Comment:

 This is hard to do, next to impossible even with the current code base.

 In django.template.Parser.invalid_block_tag, we can determine which tags
 are allowed using self.tags. However, this dict only contains f.e.
 'block', not 'endblock', only 'blocktrans', not 'endblocktrans'. We have
 no way of knowing whether 'endblock' or 'endblocktrans' are valid tags
 because the template tag author can freely choose tag names as he/she
 wants. It gets even worse with {% plural %} inside a blocktrans-block...

 Here's my stupid attempt at a patch, if anyone wants to continue:

 {{{
 diff --git a/django/template/__init__.py b/django/template/__init__.py
 index c316786..de460d0 100644
 --- a/django/template/__init__.py
 +++ b/django/template/__init__.py
 @@ -330,6 +330,8 @@ class Parser(object):

  def invalid_block_tag(self, token, command, parse_until=None):
  if parse_until:
 +if command not in self.tags:
 +raise self.error(token, "Invalid block tag: '%s', did you
 forget to load it?" % command)
  raise self.error(token, "Invalid block tag: '%s', expected
 %s" % (command, get_text_list(["'%s'" % p for p in parse_until])))
  raise self.error(token, "Invalid block tag: '%s'" % command)

 diff --git a/tests/regressiontests/templates/tests.py
 b/tests/regressiontests/templates/tests.py
 index 9e2d175..3ca8bf8 100644
 --- a/tests/regressiontests/templates/tests.py
 +++ b/tests/regressiontests/templates/tests.py
 @@ -318,6 +318,16 @@ class Templates(unittest.TestCase):
  except TemplateSyntaxError, e:
  self.assertEquals(e.args[0], "Invalid block tag: 'endblock',
 expected 'else' or 'endif'")

 +try:
 +t = Template("{% if 1 %}lala{% anything 'something' %}{%
 endif %}")
 +except TemplateSyntaxError, e:
 +self.assertEquals(e.args[0], "Invalid block tag: 'anything',
 did you forget to load it?")
 +
 +try:
 +t = Template("{% load i18n %}{% if 1 %}lala{% trans
 'something' %}{% bla %}{% endif %}")
 +except TemplateSyntaxError, e:
 +self.assertEquals(e.args[0], "Invalid block tag: 'bla',
 expected 'else' or 'endif'")
 +
  def test_templates(self):
  template_tests = self.get_template_tests()
  filter_tests = filters.get_filter_tests()
 }}}

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

-- 
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] #14045: makemessage miss some gettext in javascript

[Django]

#14045: makemessage miss some gettext in javascript
---+
  Reporter:  shaohao   | Owner:  nobody  
Status:  closed| Milestone:  
 Component:  Internationalization  |   Version:  1.2 
Resolution:  worksforme|  Keywords:  xgettext
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by mk):

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

Comment:

 I cannot reproduce this failure:

 {{{

 $ xgettext -d out -L Perl --keyword=gettext_noop --keyword=gettext_lazy
 --keyword=ngettext_lazy:1,2 --from-code UTF-8 -o - "result.pl"
 # SOME DESCRIPTIVE TITLE.
 # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
 # This file is distributed under the same license as the PACKAGE package.
 # FIRST AUTHOR , YEAR.
 #
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2010-10-05 12:32+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=CHARSET\n"
 "Content-Transfer-Encoding: 8bit\n"

 #: result.pl:5
 msgid "o"
 msgstr ""
 }}}

 Even if this would happen this would not be a Django but a gettext bug.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14011: QuerySet.none().values('x').query causes "DatabaseError: subquery has too many columns" when used in filters.

[Django]

#14011: QuerySet.none().values('x').query causes "DatabaseError: subquery has 
too
many columns" when used in filters.
--+-
  Reporter:  skatei   | Owner:  

Status:  new  | Milestone:  

 Component:  ORM aggregation  |   Version:  1.2 

Resolution:   |  Keywords:  none 
query DatabaseError
 Stage:  Accepted | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

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

  * stage:  Unreviewed => Accepted

Comment:

 Here's a test for this issue. The failure is still present in trunk.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #13999: include tag should support compiled template.

[Django]

#13999: include tag should support compiled template.
--+-
  Reporter:  DaNmarner| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  worksforme   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by mk):

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

Comment:

 Not enough information. Reopen if you have a better description of what
 you think is wrong here or could be improved.

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

-- 
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] #14392: Inconsistency for "creating forms with models"

[Django]

#14392: Inconsistency for "creating forms with models"
---+
 Reporter:  lspcity|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 on http://docs.djangoproject.com/en/1.2/topics/forms/modelforms/
 search for: fields = ['name', 'title', 'birth_date']
 and replace it with: fields = ('name', 'title', 'birth_date')

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14387: pre_save problem with inherrited model

[Django]

#14387: pre_save problem with inherrited model
--+-
  Reporter:  iskren   | Owner:  
   
Status:  new  | Milestone:  
   
 Component:  ORM aggregation  |   Version:  1.2 
   
Resolution:   |  Keywords:  pre_save inheritance 
inherited save
 Stage:  Unreviewed   | Has_patch:  0   
   
Needs_docs:  0|   Needs_tests:  0   
   
Needs_better_patch:  0|  
--+-
Changes (by iskren):

  * owner:  iskren =>
  * 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] #2507: [patch] LDAPBackend in django/contrib/auth/backends.py

[Django]

#2507: [patch] LDAPBackend in django/contrib/auth/backends.py
---+
  Reporter:  s...@mahonri5.net  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:  wontfix   |  Keywords:  ldap,usernames
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 There's no reason this needs to exist in Django core. We added an
 extension API specifically so people can build external interfaces to
 auth.

 [http://pypi.python.org/pypi/django-auth-ldap/ django-auth-ldap]  is one
 example of an external LDAP implementation.

 Marking wontfix in favor of having a vibrant external project cover this
 need.

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

-- 
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] #13559: Need a contextprocessor for current site

[Django]

#13559: Need a contextprocessor for current site
---+
  Reporter:  tonnzor   | Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by wogan):

 * cc: dja...@wogan.id.au (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.