Re: [Django] #12879: jquery gets included multiple times

[Django]

#12879: jquery gets included multiple times
---+
  Reporter:  mariarchi | Owner:  tobias  
Status:  reopened  | Milestone:  1.2 
 Component:  django.contrib.admin  |   Version:  1.2-beta
Resolution:|  Keywords:  jquery  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by ubernostrum):

 The root issue is that JS is added in a list comprehension, which
 generates the list of JS file paths to add before adding any of them; thus
 the same file path can be added multiple times by a single declaration.
 Patch attached above resolves this by using a loop which checks after
 adding each path, and also includes a regression test case which
 demonstrates the problem and passes after the fix is applied.

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

-- 
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] #12972: flatpages chokes if the url doesn't begin and end with a slash (but doesn't validate for it)

[Django]

#12972: flatpages chokes if the url doesn't begin and end with a slash (but 
doesn't
validate for it)
-+--
  Reporter:  jabapyth| Owner:  jabapyth  
Status:  new | Milestone:
 Component:  Forms   |   Version:  SVN   
Resolution:  |  Keywords:  flatpages, validation, 404
 Stage:  Unreviewed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by gvangool):

  * needs_better_patch:  => 0
  * needs_tests:  => 1
  * 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] #12974: Admin docs omits several methods for a Model

[Django]

#12974: Admin docs omits several methods for a Model
+---
  Reporter:  jabapyth   | Owner:  jabapyth  

Status:  new| Milestone:

 Component:  Documentation  |   Version:  SVN   

Resolution: |  Keywords:  admin, docs, method, 
admindocs
 Stage:  Unreviewed | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  1 

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

  * needs_tests:  0 => 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #1807: [patch] union and intersection operating on lists

[Django]

#1807: [patch] union and intersection operating on lists
---+
  Reporter:  m...@noris.de  | Owner:  nobody
   
Status:  closed| Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:  wontfix   |  Keywords:  union 
performance and or ORM QuerySet
 Stage:  Design decision needed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

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

Comment:

 Several problems here.

 One is that the ticket was closed wontfix by one of Django's lead
 developers; in that case re-opening the ticket is the wrong action.
 Instead, bring it up on the django-developers list to get feedback and see
 if there's support for reopening.

 Another is that this is ostensibly a feature request, and Django 1.2 is
 feature-frozen, so no matter what this can't go on the 1.2 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.

[Django] #13016: Invalid ForeignKey ids in fixtures do not cause any error messages

[Django]

#13016: Invalid ForeignKey ids in fixtures do not cause any error messages
+---
   Reporter:  Art   |Owner:  nobody
 Status:  new   |Milestone:
  Component:  Testing framework |  Version:  1.1   
   Keywords:|Stage:  Unreviewed
  Has_patch:  0 |   Needs_docs:  0 
Needs_tests:  0 |   Needs_better_patch:  0 
+---
 When referencing a non-existing entity instance in fixtures for ForeignKey
 relationship no error message is thrown in test runner mode (./manage.py
 test). Please note below how in fixtures instance of Parent contains
 invalid ID for Child object (2 instead of 1).
 [[BR]]
 [[BR]]
 This seems to be related to "always opened transaction" natures of tests,
 because if I run ./manage.py testserver data.json I actually get an
 exception thrown.
 [[BR]]
 Backend is Postgresql 8.3.
 [[BR]]
 [[BR]]
 Model:
 {{{
   5 class Parent(models.Model):
   6 child = models.ForeignKey('Child')
   7
   8 class Child(models.Model):
   9 name = models.CharField(default='some name', max_length=100)


 }}}
 [[BR]]
 [[BR]]
 Fixture (data.json):
 {{{
 352 {
 353 "pk": 1,
 354 "model": "testapp.parent",
 355 "fields": {
 356 "child": 2
 357 }
 358 },
 359 {
 360 "pk": 1,
 361 "model": "testapp.child",
 362 "fields": {
 363 "name": "child"
 364 }
 365 }
 }}}
 [[BR]]
 [[BR]]
 Test:
 {{{
   5 class SimpleTest(TestCase):
   6
   7 fixtures = ['data.json']
   8
   9 def test_data(self):
  10 self.assertEqual(len(models.Parent.objects.all()), 1)
  11 self.assertEqual(len(models.Child.objects.all()), 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] #12962: Broken Admin Delete Action With Confirmation

[Django]

#12962: Broken Admin Delete Action With Confirmation
---+
  Reporter:  leveille  | Owner:  nobody  
Status:  new   | Milestone:  1.2 
 Component:  django.contrib.admin  |   Version:  1.2-beta
Resolution:|  Keywords:  admin delete
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by skevy):

  * version:  SVN => 1.2-beta

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12962: Broken Admin Delete Action With Confirmation

[Django]

#12962: Broken Admin Delete Action With Confirmation
---+
  Reporter:  leveille  | Owner:  nobody  
Status:  new   | Milestone:  1.2 
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  admin delete
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by skevy):

 * cc: adam.sk...@mac.com (added)

Comment:

 I've done a bit more research into this ticket.

 The patch does indeed work, and all currently written tests (including
 those written in changeset 12525) pass correctly.

 However, what I found interesting was that in the admin_view test suite,
 in the following test:
 {{{
 def test_model_admin_default_delete_action(self):
 "Tests the default delete action defined as a ModelAdmin method"
 action_data = {
 ACTION_CHECKBOX_NAME: [1, 2],
 'action' : 'delete_selected',
 'index': 0,
 }
 delete_confirmation_data = {
 ACTION_CHECKBOX_NAME: [1, 2],
 'action' : 'delete_selected',
 'index': 0,
 'post': 'yes',
 }
 confirmation =
 self.client.post('/test_admin/admin/admin_views/subscriber/', action_data)
 self.assertContains(confirmation, "Are you sure you want to delete
 the selected subscriber objects")
 self.failUnless(confirmation.content.count(ACTION_CHECKBOX_NAME)
 == 2)
 response =
 self.client.post('/test_admin/admin/admin_views/subscriber/',
 delete_confirmation_data)
 self.failUnlessEqual(Subscriber.objects.count(), 0)
 }}}

 Notice that it sets 'index' equal to 0 in delete_confirmation_data.  This
 is not what happens for real.  In fact, when you confirm you want to
 delete objects, 'index' is never set in the post data.  The fact that
 'index' is set to 0 in this test is what caused this test to pass way back
 when 12525 actually happened.

 So, I don't know if index SHOULD be set in the post data when the objects
 are actually deleted, or if the test is incorrect.  Some more info on how
 to proceed from someone who knows WAY more about this code than me would
 be awesome :-)

 Thanks,
 -Adam

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

-- 
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] #11263: Bug in lookup with generic relation in model inheritance

[Django]

#11263: Bug in lookup with generic relation in model inheritance
---+
  Reporter:  veena | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  generic 
relations, model inheritance
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by paltman):

  * 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] #10967: save(force_update=True) crashes with model inheritance

[Django]

#10967: save(force_update=True) crashes with model inheritance
---+
  Reporter:  lgs   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by paltman):

  * 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] #10099: MySQL 5.0 does not support LIMIT in subqueries

[Django]

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

  * 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] #13000: Deprecated code in admin forms triggers string translation too soon

[Django]

#13000: Deprecated code in admin forms triggers string translation too soon
---+
  Reporter:  lgs   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 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 paltman):

  * 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] #13015: Language regarding ModelForms with instances attached vs. bound Forms is unclear

[Django]

#13015: Language regarding ModelForms with instances attached vs. bound Forms is
unclear
+---
  Reporter:  Wedg   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * stage:  Unreviewed => Accepted

Comment:

 Yes, the model form documentation's use of an instance being "bound" to a
 form is confusing at best.

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

-- 
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] #13015: Language regarding ModelForms with instances attached vs. bound Forms is unclear

[Django]

#13015: Language regarding ModelForms with instances attached vs. bound Forms is
unclear
+---
  Reporter:  Wedg   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by Wedg):

 Replying to [ticket:13015 Wedg]:
 > I discovered that providing initial via the field =
 FormField(initial='foobar') method and form =
 ModelForm(initial={'field':'method'}) behaves differently when the
 ModelForm is attached to a difference.
 This should read "attached to an instance." This is what no sleep gets
 you. I apologize.

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

-- 
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] #13015: Language regarding ModelForms with instances attached vs. bound Forms is unclear

[Django]

#13015: Language regarding ModelForms with instances attached vs. bound Forms is
unclear
-+--
   Reporter:  Wedg   |Owner:  nobody
 Status:  new|Milestone:
  Component:  Documentation  |  Version:  SVN   
   Keywords: |Stage:  Unreviewed
  Has_patch:  0  |   Needs_docs:  0 
Needs_tests:  0  |   Needs_better_patch:  0 
-+--
 I discovered that providing initial via the field =
 FormField(initial='foobar') method and form =
 ModelForm(initial={'field':'method'}) behaves differently when the
 ModelForm is attached to a difference.

 The documentation refers to a model instance bound to a form (at least in
 one location: http://docs.djangoproject.com/en/1.1/topics/forms/modelforms
 /#overriding-the-clean-method).

 And also the documentation describing initial (both for fields and Forms)
 says that it only provides a value for unbound forms.

 Perhaps we could clarify the language to say that an instance is attached
 to a ModelForm, but the form itself is unbound - and maybe yet further
 explain that any initial= values for a FormField will be overridden by the
 values from an attached model instance, which in turn will be overridden
 by any initial= values provided to the ModelForm at runtime.

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

-- 
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] #13014: Cache templatetag is not locale aware

[Django]

#13014: Cache templatetag is not locale aware
-+--
  Reporter:  yml | Owner:  SmileyChris
Status:  assigned| Milestone:  1.2
 Component:  Template system |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  1   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * needs_docs:  0 => 1
  * stage:  Accepted => Design decision needed

Comment:

 Yann brought up the point that maybe a user should be told to just do this
 manually by passing the locale as a cache argument.

 Some short docs should be added to explain either the difference in
 behaviour or the parity.

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

-- 
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] #13014: Cache templatetag is not locale aware

[Django]

#13014: Cache templatetag is not locale aware
--+-
  Reporter:  yml  | Owner:  SmileyChris
Status:  assigned | Milestone:  1.2
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * status:  new => assigned
  * component:  Uncategorized => Template system
  * summary:  Cache templatetag and i18n => Cache templatetag is not locale
  aware
  * version:  1.1 => SVN
  * owner:  nobody => SmileyChris
  * 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] #11526: LDAP authentication backend

[Django]

#11526: LDAP authentication backend
-+--
  Reporter:  psagers | Owner:  dp_wiz
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  wontfix |  Keywords:  ldap  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ekohl):

 Thank you for your effort. I've been using it in production without issues
 for some time now.

 Perhaps you could tag your releases in mercurial as well.

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

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

[Django]

#13014: Cache templatetag and i18n
+---
  Reporter:  yml| Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Comment:

 I think that it makes sense to achieve parity between decorator and
 template tag caching before 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.

[Django] #13014: Cache templatetag and i18n

[Django]

#13014: Cache templatetag and i18n
---+
 Reporter:  yml|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 '''Issue:'''
 The cache templatetag does not take into account the Language (i18n).

 '''Solution:'''
 The cache templatetag[1] should be updated to use the new
 _i18n_cache_key_suffix[2]. Given context in which this code is evaluated
 the request is not required :
 cache_key = _i18n_cache_key_suffix(request=None, cache_key):

 This is in fact a follow up this ticket : #5691 which reported a similar
 issue with the cache middleware. the infrastructure for this change has
 been added in r12624 and r12546


 
[1]http://code.djangoproject.com/browser/django/trunk/django/templatetags/cache.py#L28
 [2]
 http://code.djangoproject.com/browser/django/trunk/django/utils/cache.py#L137

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

-- 
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] #11526: LDAP authentication backend

[Django]

#11526: LDAP authentication backend
-+--
  Reporter:  psagers | Owner:  dp_wiz
Status:  closed  | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  wontfix |  Keywords:  ldap  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by psagers):

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

Comment:

 Sorry, by closed I meant wontfix. Closing wontfix myself on the advice of
 jkocherhans (http://groups.google.com/group/django-
 developers/browse_thread/thread/bb74fcc467917996).

 This project has been on pypi for a while under the name django-auth-ldap
 (http://pypi.python.org/pypi/django-auth-ldap/). The source is hosted at
 http://bitbucket.org/psagers/django-auth-ldap/. Feedback and suggestions
 are welcome.

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

-- 
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] #1807: [patch] union and intersection operating on lists

[Django]

#1807: [patch] union and intersection operating on lists
---+
  Reporter:  m...@noris.de  | Owner:  nobody
   
Status:  reopened  | Milestone:  1.2
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  union 
performance and or ORM QuerySet
 Stage:  Design decision needed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by verveguy):

  * keywords:  => union performance and or ORM QuerySet
  * status:  closed => reopened
  * resolution:  wontfix =>
  * milestone:  => 1.2

Comment:

 So, I believe I have found a case where the standard behavior of the
 Django QuerySet code produces a highly suboptimal result due to lack of
 UNION over simple AND and OR

 The default query here takes 2mins to execute on MySQL 5.0 whereas the
 variant using UNION takes 0.17 seconds

 My model is a little complex perhaps, but not so unusual. In fact, it just
 so happens to be the underlying model of the JIRA issue tracking product
 from Atlassian which we're front-ending using Django.

 Given a datamodel with four tables all revolving around  the table Issue
 that has user-defined custom properties and tracks changes to these
 properties in an audit trail:

 Issue

 Customfield - defines "properties" of Issue that aren't columns in the
 schema
 Customfieldvalue - provides *current* instance values of a given
 Customfield for a given Issue

 Changegroup - tracks a group of related Changeitems against the
 "properties" of an Issue made at a time in the past
 Changeitem - an individual change of a property from value / to value

 Given a problem space where a single Customfield called "Iteration' has
 been defined against Issues,

 Goal is to build a Django query that will find "all Issues where Iteration
 is currently in [X,Y] or *has ever been* in [X,Y] in the past"

 (Naive?) approach:

 {{{
 currentIssues = models.Jiraissue.objects.distinct().filter(
 customfieldvalues__customfield__cfname="Iteration",
 customfieldvalues__stringvalue__in=[X,Y])

 oldIssues = models.Jiraissue.objects.distinct().filter(
 Q(  Q(changegroups__items__oldstring__in=[X,Y]])
 | Q(changegroups__items__newstring__in=[X,Y]),
changegroups__items__field='Iteration'))

 issues = currentIssues | oldIssues
 }}}


 The resulting query looks like this:


 {{{
 SELECT DISTINCT `jiraissue`.`PROJECT`, `jiraissue`.`ASSIGNEE`,
 `jiraissue`.`REPORTER`, `jiraissue`.`ID`,
 `jiraissue`.`pkey`, `jiraissue`.`issuetype`, `jiraissue`.`SUMMARY`,
 `jiraissue`.`DESCRIPTION`,
 `jiraissue`.`ENVIRONMENT`, `jiraissue`.`PRIORITY`,
 `jiraissue`.`RESOLUTION`, `jiraissue`.`issuestatus`,
 `jiraissue`.`CREATED`, `jiraissue`.`UPDATED`, `jiraissue`.`DUEDATE`,
 `jiraissue`.`RESOLUTIONDATE`,
 `jiraissue`.`VOTES`, `jiraissue`.`TIMEORIGINALESTIMATE`,
 `jiraissue`.`TIMEESTIMATE`, `jiraissue`.`TIMESPENT`,
 `jiraissue`.`WORKFLOW_ID`, `jiraissue`.`SECURITY`, `jiraissue`.`FIXFOR`,
 `jiraissue`.`COMPONENT`
 FROM `jiraissue`
 INNER JOIN `customfieldvalue` ON (`jiraissue`.`ID` =
 `customfieldvalue`.`ISSUE`)
 LEFT OUTER JOIN `customfield` ON (`customfieldvalue`.`CUSTOMFIELD` =
 `customfield`.`ID`)
 LEFT OUTER JOIN `changegroup` ON (`jiraissue`.`ID` =
 `changegroup`.`ISSUEID`)
 LEFT OUTER JOIN `changeitem` ON (`changegroup`.`ID` =
 `changeitem`.`GROUPID`)
 WHERE ((`customfield`.`cfname` = 'Iteration'  AND
 `customfieldvalue`.`STRINGVALUE` IN (X, Y))
 OR ((`changeitem`.`OLDSTRING` IN (X, Y) OR `changeitem`.`NEWSTRING` IN (X,
 Y)) AND `changeitem`.`FIELD` = 'Iteration' ))
 }}}


 The hand-crafted alternative using UNION on two subqueries which is *much*
 faster is this:


 {{{
 SELECT DISTINCT ji.PROJECT, ji.ASSIGNEE, ji.REPORTER, ji.ID,
 ji.pkey, ji.issuetype, ji.SUMMARY, ji.DESCRIPTION, ji.ENVIRONMENT,
 ji.PRIORITY, ji.RESOLUTION, ji.issuestatus, ji.CREATED, ji.UPDATED,
 ji.DUEDATE, ji.RESOLUTIONDATE, ji.VOTES, ji.TIMEORIGINALESTIMATE,
 ji.TIMEESTIMATE, ji.TIMESPENT, ji.WORKFLOW_ID, ji.SECURITY, ji.FIXFOR,
 ji.COMPONENT
 FROM jiraissue AS ji
 JOIN (
 SELECT cg.ISSUEID AS ISSUEID
   FROM changegroup AS cg
   JOIN changeitem AS ci ON (cg.ID = ci.GROUPID)
  WHERE ci.FIELD = 'Iteration'
AND (ci.OLDSTRING = 'March 17, 2010' OR ci.NEWSTRING IN (X,Y))
 UNION
 SELECT cfv.ISSUE AS ISSUEID
   FROM customfieldvalue AS cfv
   JOIN customfield AS cf ON (cfv.CUSTOMFIELD = cf.ID)
  WHERE cf.cfname = 'Iteration' 

Re: [Django] #13012: Model.objects.get_or_create() try/except is slightly yet insideously broken

[Django]

#13012: Model.objects.get_or_create() try/except is slightly yet insideously 
broken
--+-
  Reporter:  brantley (deadwis...@gmail.com)  | Owner:  nobody  
 
Status:  closed   | Milestone:  
 
 Component:  Database layer (models, ORM) |   Version:  1.1 
 
Resolution:  invalid  |  Keywords:  
get_or_create
 Stage:  Unreviewed   | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Changes (by kmtracey):

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

Comment:

 That's exactly what the get_or_create code wants to do: reflect the
 earlier exception, not the does not exist, to the caller. I doubt raising
 !DoesNotExist from get_or_create would make things any clearer. The
 problem is a subtle bug in the way you are calling it or how you have set
 unique constraints on the table, and you're likely going to be scratching
 your head on receipt of either the integrity error or the does not exist.

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

-- 
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] #11158: get_image_dimensions very slow after 1 call

[Django]

#11158: get_image_dimensions very slow after 1 call
-+--
  Reporter:  kua | Owner:  nobody   
  
Status:  new | Milestone:  1.2  
  
 Component:  Core framework  |   Version:  SVN  
  
Resolution:  |  Keywords:  get_image_dimensions, 
field, save, slow
 Stage:  Accepted| Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  1   |  
-+--
Comment (by SmileyChris):

 Simpler patch, same effect.

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

-- 
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] #11526: LDAP authentication backend

[Django]

#11526: LDAP authentication backend
-+--
  Reporter:  psagers | Owner:  dp_wiz
Status:  assigned| Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  ldap  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

  * milestone:  1.2 =>

Comment:

 Replying to [comment:27 psagers]:
 > Moving to 1.2 so it will get closed.

 Please don't do that. 1.2 is now in bug fix only mode, trying to garner
 attention for features by putting them in the milestone just takes away
 devs time from the work of actually trying to fix bugs and get 1.2 out.
 Per http://code.djangoproject.com/wiki/Version1.2Features#Lowpriority this
 is a low-priority 1.2 feature that didn't make the feature deadline; at
 this point it will have to wait for the next release.

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

-- 
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] #11994: save upload file with specify encode

[Django]

#11994: save upload file with specify encode
---+
  Reporter:  flyinfl...@gmail.com  | Owner:  flyinflash
Status:  closed| Milestone:
 Component:  File uploads/storage  |   Version:  1.2-alpha 
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 I suspect this is fixed by r12661, which restores old behavior of passing
 unicode file names to the OS for saving.

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

-- 
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] #11030: File uploads break on non english filesystem encoding

[Django]

#11030: File uploads break on non english filesystem encoding
---+
  Reporter:  Honza_Kral| Owner:  nobody
Status:  closed| Milestone:
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:  fixed |  Keywords:  file path encoding
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Whoops that was supposed to be fixed #12898 and refs this one. r12661
 likely re-breaks this one, but there is not enough detail here for me to
 recreate the problem so I cannot say what would be a better fix for this
 one.

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

-- 
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] r12662 - in django/branches/releases/1.1.X: . django/core/files tests/regressiontests/file_uploads

[noreply]

Author: kmtracey
Date: 2010-03-02 16:02:02 -0600 (Tue, 02 Mar 2010)
New Revision: 12662

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/core/files/storage.py
   django/branches/releases/1.1.X/tests/regressiontests/file_uploads/views.py
Log:
[1.1.X] Fixed #12898: Reverted a change that assumed the file system encoding 
was utf8, and changed a test to demonstrate how that assumption corrupted 
uploaded non-ASCII file names on systems that don't use utf8 as their file 
system encoding (Windows for one, specifically). Thanks for the report to 
vrehak. 

r12661 from trunk.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12398,12405,12408-12411,12419-12420,12423,12425-12426,12429,12434,12436,12439-12442,12448,12457,12461-12464,12467,12473,12475,12490,12492,12497-12498,12502,12513,12515-12516,12518,12523,12526,12528,12533,12535,12537,12539,12541,12548,12553,12556,12558-12560,12562,12567,12569-12570,12573,12576,12581,12584,12616,12621-12622,12631,12648,12650,12652,12659
   + 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12398,12405,12408-12411,12419-12420,12423,12425-12426,12429,12434,12436,12439-12442,12448,12457,12461-12464,12467,12473,12475,12490,12492,12497-12498,12502,12513,12515-12516,12518,12523,12526,12528,12533,12535,12537,12539,12541,12548,12553,12556,12558-12560,12562,12567,12569-12570,12573,12576,12581,12584,12616,12621-12622,12631,12648,12650,12652,12659,12661

Modified: django/branches/releases/1.1.X/django/core/files/storage.py
===
--- django/branches/releases/1.1.X/django/core/files/storage.py 2010-03-02 
21:58:49 UTC (rev 12661)
+++ django/branches/releases/1.1.X/django/core/files/storage.py 2010-03-02 
22:02:02 UTC (rev 12662)
@@ -6,7 +6,7 @@
 from django.core.exceptions import ImproperlyConfigured, SuspiciousOperation
 from django.core.files import locks, File
 from django.core.files.move import file_move_safe
-from django.utils.encoding import force_unicode, smart_str
+from django.utils.encoding import force_unicode
 from django.utils.functional import LazyObject
 from django.utils.importlib import import_module
 from django.utils.text import get_valid_filename
@@ -212,7 +212,7 @@
 path = safe_join(self.location, name)
 except ValueError:
 raise SuspiciousOperation("Attempted access to '%s' denied." % 
name)
-return smart_str(os.path.normpath(path))
+return os.path.normpath(path)
 
 def size(self, name):
 return os.path.getsize(self.path(name))

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/file_uploads/views.py
===
--- django/branches/releases/1.1.X/tests/regressiontests/file_uploads/views.py  
2010-03-02 21:58:49 UTC (rev 12661)
+++ django/branches/releases/1.1.X/tests/regressiontests/file_uploads/views.py  
2010-03-02 22:02:02 UTC (rev 12662)
@@ -2,7 +2,7 @@
 from django.core.files.uploadedfile import UploadedFile
 from django.http import HttpResponse, HttpResponseServerError
 from django.utils import simplejson
-from models import FileModel

[Changeset] r12661 - in django/trunk: django/core/files tests/regressiontests/file_uploads

[noreply]

Author: kmtracey
Date: 2010-03-02 15:58:49 -0600 (Tue, 02 Mar 2010)
New Revision: 12661

Modified:
   django/trunk/django/core/files/storage.py
   django/trunk/tests/regressiontests/file_uploads/views.py
Log:
Fixed #11030: Reverted a change that assumed the file system encoding was utf8, 
and changed a test to demonstrate how that assumption corrupted uploaded 
non-ASCII file names on systems that don't use utf8 as their file system 
encoding (Windows for one, specifically). Thanks for the report to vrehak.
 


Modified: django/trunk/django/core/files/storage.py
===
--- django/trunk/django/core/files/storage.py   2010-03-02 19:41:39 UTC (rev 
12660)
+++ django/trunk/django/core/files/storage.py   2010-03-02 21:58:49 UTC (rev 
12661)
@@ -7,7 +7,7 @@
 from django.core.exceptions import ImproperlyConfigured, SuspiciousOperation
 from django.core.files import locks, File
 from django.core.files.move import file_move_safe
-from django.utils.encoding import force_unicode, smart_str
+from django.utils.encoding import force_unicode
 from django.utils.functional import LazyObject
 from django.utils.importlib import import_module
 from django.utils.text import get_valid_filename
@@ -210,7 +210,7 @@
 path = safe_join(self.location, name)
 except ValueError:
 raise SuspiciousOperation("Attempted access to '%s' denied." % 
name)
-return smart_str(os.path.normpath(path))
+return os.path.normpath(path)
 
 def size(self, name):
 return os.path.getsize(self.path(name))

Modified: django/trunk/tests/regressiontests/file_uploads/views.py
===
--- django/trunk/tests/regressiontests/file_uploads/views.py2010-03-02 
19:41:39 UTC (rev 12660)
+++ django/trunk/tests/regressiontests/file_uploads/views.py2010-03-02 
21:58:49 UTC (rev 12661)
@@ -2,7 +2,7 @@
 from django.core.files.uploadedfile import UploadedFile
 from django.http import HttpResponse, HttpResponseServerError
 from django.utils import simplejson
-from models import FileModel
+from models import FileModel, UPLOAD_TO
 from uploadhandler import QuotaUploadHandler, ErroringUploadHandler
 from django.utils.hashcompat import sha_constructor
 from tests import UNICODE_FILENAME
@@ -18,7 +18,7 @@
 # If a file is posted, the dummy client should only post the file name,
 # not the full path.
 if os.path.dirname(form_data['file_field'].name) != '':
-return HttpResponseServerError()
+return HttpResponseServerError()
 return HttpResponse('')
 else:
 return HttpResponseServerError()
@@ -62,7 +62,8 @@
 # through file save.
 uni_named_file = request.FILES['file_unicode']
 obj = FileModel.objects.create(testfile=uni_named_file)
-if not obj.testfile.name.endswith(uni_named_file.name):
+full_name = u'%s/%s' % (UPLOAD_TO, uni_named_file.name)
+if not os.path.exists(full_name):
 response = HttpResponseServerError()
 
 # Cleanup the object with its exotic file name immediately.
@@ -82,14 +83,14 @@
 """
 r = dict([(k, f.name) for k, f in request.FILES.items()])
 return HttpResponse(simplejson.dumps(r))
-
+
 def file_upload_quota(request):
 """
 Dynamically add in an upload handler.
 """
 request.upload_handlers.insert(0, QuotaUploadHandler())
 return file_upload_echo(request)
-
+
 def file_upload_quota_broken(request):
 """
 You can't change handlers after reading FILES; this view shouldn't work.

-- 
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] #13013: Page missing {% csrf_token %}

[Django]

#13013: Page missing {% csrf_token %}
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The form at the bottom of the
 http://docs.djangoproject.com/en/dev/topics/i18n/internationalization/
 page is missing {% csrf_token %}.

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

-- 
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] #12999: update_all_contenttypes in contenttypes.management fails in django 1.2

[Django]

#12999: update_all_contenttypes in contenttypes.management fails in django 1.2
---+
  Reporter:  lsbardel  | Owner:  nobody  
Status:  new   | Milestone:  1.2 
 Component:  Contrib apps  |   Version:  SVN 
Resolution:|  Keywords:  contenttypes
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  1 |  
---+
Changes (by gabrielhurley):

  * component:  Uncategorized => Contrib apps

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

-- 
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] #13012: Model.objects.get_or_create() try/except is slightly yet insideously broken

[Django]

#13012: Model.objects.get_or_create() try/except is slightly yet insideously 
broken
--+-
  Reporter:  brantley (deadwis...@gmail.com)  | Owner:  nobody  
 
Status:  new  | Milestone:  
 
 Component:  Database layer (models, ORM) |   Version:  1.1 
 
Resolution:   |  Keywords:  
get_or_create
 Stage:  Unreviewed   | Has_patch:  1   
 
Needs_docs:  0|   Needs_tests:  0   
 
Needs_better_patch:  0|  
--+-
Changes (by brantley (deadwis...@gmail.com)):

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

Comment:

 No, I was all wrong on this.  The existing way is correct.

 But something feels terribly off here.  And now that I think about it,
 it's the second time I've been bitten by this non-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.

[Django] #13012: Model.objects.get_or_create() try/except is slightly yet insideously broken

[Django]

#13012: Model.objects.get_or_create() try/except is slightly yet insideously 
broken
-+--
 Reporter:  brantley (deadwis...@gmail.com)  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Database layer (models, ORM) | Version:  1.1   
 Keywords:  get_or_create|   Stage:  Unreviewed
Has_patch:  1|  
-+--
 What is wrong with this code:
 {{{
 except self.model.DoesNotExist:
 raise e
 }}}

 That's right, e is not defined.  But what if e is previously defined in a
 surrounding except block?  Then we will be raising the previous exception,
 not the current one.  That's exactly what is happening in
 {{{get_or_create()}}}, and caused me some consternation as I was getting a
 "PRIMARY_KEY must be unique" exception, even though the real exception was
 something else.

 Patch, in all its three character glory, is included.

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

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

[Django]

#11526: LDAP authentication backend
-+--
  Reporter:  psagers | Owner:  dp_wiz
Status:  assigned| Milestone:  1.2   
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  ldap  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by psagers):

  * milestone:  => 1.2

Comment:

 Moving to 1.2 so it will get closed.

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

-- 
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] #11526: LDAP authentication backend

[Django]

#11526: LDAP authentication backend
-+--
  Reporter:  psagers | Owner:  dp_wiz
Status:  assigned| Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:  ldap  
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by hejsan):

 * cc: hr.bjarni+dja...@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] #10975: Accessing derived block doesn't work within ifequal tag

[Django]

#10975: Accessing derived block doesn't work within ifequal tag
---+
  Reporter:  libwill...@gmail.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Uncategorized |   Version:  SVN   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by SmileyChris):

 Fixed in [12655], by the way.

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

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

[Django]

#8896: Routing according also to hostname
-+--
  Reporter:  veena   | Owner:  jshedd  
Status:  new | Milestone:  
 Component:  Core framework  |   Version:  1.0 
Resolution:  |  Keywords:  routing hostname
 Stage:  Someday/Maybe   | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by mikexstudios):

 * cc: mike.huynh+dja...@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.

[Changeset] r12660 - in django/branches/releases/1.1.X: . django/http tests/regressiontests/views tests/regressiontests/views/tests

[noreply]

Author: kmtracey
Date: 2010-03-02 13:41:39 -0600 (Tue, 02 Mar 2010)
New Revision: 12660

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/django/http/__init__.py
   django/branches/releases/1.1.X/tests/regressiontests/views/tests/specials.py
   django/branches/releases/1.1.X/tests/regressiontests/views/urls.py
Log:
[1.1.X] Fixed #11522: Restored ability of http redirect responses to correctly 
handle redirect locations with non-ASCII chars. 

r12659 from trunk.



Property changes on: django/branches/releases/1.1.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12398,12405,12408-12411,12419-12420,12423,12425-12426,12429,12434,12436,12439-12442,12448,12457,12461-12464,12467,12473,12475,12490,12492,12497-12498,12502,12513,12515-12516,12518,12523,12526,12528,12533,12535,12537,12539,12541,12548,12553,12556,12558-12560,12562,12567,12569-12570,12573,12576,12581,12584,12616,12621-12622,12631,12648,12650,12652
   + 
/django/trunk:1-11500,11523,11527-11528,11531-11552,11554,11577,11579-11581,11588-11589,11591-11592,11596-11599,11601-11617,11619-11626,11628-11635,11637-11638,11643-11644,11648-11653,11656,11670,11678,11681,11684,11686,11688,11691,11693,11695,11697,11699,11701,11703,11705,11707,11714,11719,11732,11734,11740,11748,11751,11753,11756,11760,11800,11802,11808,11815,11817,11820,11822,11824,11826,11828,11831,11833,11835,11837,11839,11841,11844,11857,11864,11874,11876,11878,11885,11898,11901,11905,11909,11912,11914,11917,11938,11953,11961,11977,11979,11984,11986,11988,11990,11992,11994,11996,11998,12001,12004,12006,12011,12022,12024,12044-12045,12048,12054-12056,12059,12064,12066,12068,12070,12079,12086,12088,12104,12118,12132,12137-12138,12140-12141,12144,12150-12152,12220-12221,12229,12249,12253,12276,12282,12284,12293,12313,12317-12324,12333,12341,12343,12346,12353,12362,12379,12384,12398,12405,12408-12411,12419-12420,12423,12425-12426,12429,12434,12436,12439-12442,12448,12457,12461-12464,12467,12473,12475,12490,12492,12497-12498,12502,12513,12515-12516,12518,12523,12526,12528,12533,12535,12537,12539,12541,12548,12553,12556,12558-12560,12562,12567,12569-12570,12573,12576,12581,12584,12616,12621-12622,12631,12648,12650,12652,12659

Modified: django/branches/releases/1.1.X/django/http/__init__.py
===
--- django/branches/releases/1.1.X/django/http/__init__.py  2010-03-02 
19:37:48 UTC (rev 12659)
+++ django/branches/releases/1.1.X/django/http/__init__.py  2010-03-02 
19:41:39 UTC (rev 12660)
@@ -434,14 +434,14 @@
 
 def __init__(self, redirect_to):
 HttpResponse.__init__(self)
-self['Location'] = redirect_to
+self['Location'] = iri_to_uri(redirect_to)
 
 class HttpResponsePermanentRedirect(HttpResponse):
 status_code = 301
 
 def __init__(self, redirect_to):
 HttpResponse.__init__(self)
-self['Location'] = redirect_to
+self['Location'] = iri_to_uri(redirect_to)
 
 class HttpResponseNotModified(HttpResponse):
 status_code = 304

Modified: 
django/branches/releases/1.1.X/tests/regressiontests/views/tests/specials.py
===
--- 
django/branches/releases/1.1.X/tests/regressiontests/views/tests/specials.py
2010-03-02 19:37:48 UTC (rev 12659)
+++ 
django/branches/releases/1.1.X/tests/regressiontests/views/tests/specials.py
2010-03-02 19:41:39 UTC (rev 12660)
@@ -5,11 +5,31 @@
 """
 Tests for URL handling in views and responses.
 """
-def test_iri_redirect(self):
+redirect_target = "/views/%E4%B8%AD%E6%96%87/target/"
+
+def test_combining_redirect(self):
 """
 Tests that redirecting to an IRI, requiring encoding before we use it
-in an HTTP response, is handled correctly.
+in an HTTP response, is handled correctly. In this case the arg to
+HttpRedirect is ASCII but the current request path contains non-ASCII
+characters so this test ensures the creation of the full path with a
+  

[Changeset] r12659 - in django/trunk: django/http tests/regressiontests/views tests/regressiontests/views/tests

[noreply]

Author: kmtracey
Date: 2010-03-02 13:37:48 -0600 (Tue, 02 Mar 2010)
New Revision: 12659

Modified:
   django/trunk/django/http/__init__.py
   django/trunk/tests/regressiontests/views/tests/specials.py
   django/trunk/tests/regressiontests/views/urls.py
Log:
Fixed #11522: Restored ability of http redirect responses to correctly handle 
redirect locations with non-ASCII chars.


Modified: django/trunk/django/http/__init__.py
===
--- django/trunk/django/http/__init__.py2010-03-02 17:11:02 UTC (rev 
12658)
+++ django/trunk/django/http/__init__.py2010-03-02 19:37:48 UTC (rev 
12659)
@@ -434,14 +434,14 @@
 
 def __init__(self, redirect_to):
 HttpResponse.__init__(self)
-self['Location'] = redirect_to
+self['Location'] = iri_to_uri(redirect_to)
 
 class HttpResponsePermanentRedirect(HttpResponse):
 status_code = 301
 
 def __init__(self, redirect_to):
 HttpResponse.__init__(self)
-self['Location'] = redirect_to
+self['Location'] = iri_to_uri(redirect_to)
 
 class HttpResponseNotModified(HttpResponse):
 status_code = 304

Modified: django/trunk/tests/regressiontests/views/tests/specials.py
===
--- django/trunk/tests/regressiontests/views/tests/specials.py  2010-03-02 
17:11:02 UTC (rev 12658)
+++ django/trunk/tests/regressiontests/views/tests/specials.py  2010-03-02 
19:37:48 UTC (rev 12659)
@@ -5,11 +5,31 @@
 """
 Tests for URL handling in views and responses.
 """
-def test_iri_redirect(self):
+redirect_target = "/views/%E4%B8%AD%E6%96%87/target/"
+
+def test_combining_redirect(self):
 """
 Tests that redirecting to an IRI, requiring encoding before we use it
-in an HTTP response, is handled correctly.
+in an HTTP response, is handled correctly. In this case the arg to
+HttpRedirect is ASCII but the current request path contains non-ASCII
+characters so this test ensures the creation of the full path with a
+base non-ASCII part is handled correctly.
 """
 response = self.client.get(u'/views/中文/')
-self.assertRedirects(response, "/views/%E4%B8%AD%E6%96%87/target/")
+self.assertRedirects(response, self.redirect_target)
 
+def test_nonascii_redirect(self):
+"""
+Tests that a non-ASCII argument to HttpRedirect is handled properly.
+"""
+response = self.client.get('/views/nonascii_redirect/')
+self.assertRedirects(response, self.redirect_target)
+
+def test_permanent_nonascii_redirect(self):
+"""
+Tests that a non-ASCII argument to HttpPermanentRedirect is handled
+properly.
+"""
+response = self.client.get('/views/permanent_nonascii_redirect/')
+self.assertRedirects(response, self.redirect_target, status_code=301)
+

Modified: django/trunk/tests/regressiontests/views/urls.py
===
--- django/trunk/tests/regressiontests/views/urls.py2010-03-02 17:11:02 UTC 
(rev 12658)
+++ django/trunk/tests/regressiontests/views/urls.py2010-03-02 19:37:48 UTC 
(rev 12659)
@@ -97,3 +97,12 @@
 urlpatterns += patterns('',
 (r'^raises/$', views.raises)
 )
+
+# rediriects, both temporary and permanent, with non-ASCII targets
+urlpatterns += patterns('django.views.generic.simple',
+('^nonascii_redirect/$', 'redirect_to',
+{'url': u'/views/中文/target/', 'permanent': False}),
+('^permanent_nonascii_redirect/$', 'redirect_to',
+{'url': u'/views/中文/target/', 'permanent': True}),
+)
+

-- 
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] #13011: Clear Cache tag for consideration

[Django]

#13011: Clear Cache tag for consideration
--+-
 Reporter:  redcoelho |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Cache system  | Version:  1.2-beta  
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Hi. Here is a template tag I wrote that might be worth adding.
 It clears the cache that was created with the cache tag. It uses similar
 syntax.

 http://www.djangosnippets.org/snippets/1801/

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

-- 
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] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
---+
  Reporter:  jacob | Owner:  dcramer 
Status:  assigned  | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  database
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by broderboy):

 * cc: broderboy (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] #6228: Common middleware does not respect urlconf override in request

[Django]

#6228: Common middleware does not respect urlconf override in request
-+--
  Reporter:  trey| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Core framework  |   Version:  1.2-beta  
Resolution:  |  Keywords:  middleware, common
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by mikexstudios):

 * cc: mike.huynh+dja...@gmail.com (added)

Comment:

 @skevy Wow, that's awesome. Thanks for making a new patch and creating
 tests.

 I reviewed skevy's patch and it is sound. The patch applies cleanly to
 django trunk (r12657) and middlware tests all pass.

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

-- 
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] #13010: ModelForm clean() is ignored

[Django]

#13010: ModelForm clean() is ignored
-+--
  Reporter:  patrys  | Owner:  nobody  
Status:  closed  | Milestone:  1.2 
 Component:  Forms   |   Version:  1.2-beta
Resolution:  duplicate   |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by jkocherhans):

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

Comment:

 Duplicate of #12960.

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

-- 
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] #13010: ModelForm clean() is ignored

[Django]

#13010: ModelForm clean() is ignored
+---
 Reporter:  patrys  |   Owner:  nobody
   Status:  new |   Milestone:  1.2   
Component:  Forms   | Version:  1.2-beta  
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 In 1.2 when you validate a form the logic is as follows:

  * {{{BaseForm}}}'s {{{full_clean()}}} is called
  * {{{ModelForm}}}'s {{{_clean_fields()}}} is called
* it calls each field's {{{clean_FOO()}}}
* it calls construct_instance and at this point assigns all values to
 the instance
  * {{{BaseForm}}}'s {{{_clean_form()}}} is called
* it calls {{{clean()}}}

 At this point clean() can update self.cleaned_data but the value is never
 used for anything. This breaks forms that rely on clean() being able to
 alter the data (useful for example when a field's value depends on other
 fields). The instance should at least be updated when calling save().

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

-- 
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] r12658 - django/branches/releases/1.1.X/django/conf

[noreply]

Author: jezdez
Date: 2010-03-02 11:11:02 -0600 (Tue, 02 Mar 2010)
New Revision: 12658

Modified:
   django/branches/releases/1.1.X/django/conf/global_settings.py
Log:
[1.1.X] Fixed Bosnian language code introduced in r12330.

Backport from r12657.

Modified: django/branches/releases/1.1.X/django/conf/global_settings.py
===
--- django/branches/releases/1.1.X/django/conf/global_settings.py   
2010-03-02 15:42:32 UTC (rev 12657)
+++ django/branches/releases/1.1.X/django/conf/global_settings.py   
2010-03-02 17:11:02 UTC (rev 12658)
@@ -44,7 +44,7 @@
 ('ar', gettext_noop('Arabic')),
 ('bg', gettext_noop('Bulgarian')),
 ('bn', gettext_noop('Bengali')),
-('bn', gettext_noop('Bosnian')),
+('bs', gettext_noop('Bosnian')),
 ('ca', gettext_noop('Catalan')),
 ('cs', gettext_noop('Czech')),
 ('cy', gettext_noop('Welsh')),

-- 
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] #7936: Add Last-Modified header to feeds

[Django]

#7936: Add Last-Modified header to feeds
+---
  Reporter:  julianb| Owner:  julianb  
Status:  assigned   | Milestone:   
 Component:  RSS framework  |   Version:  1.2-alpha
Resolution: |  Keywords:  syndication last-modified
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 This is a feature request, and so it cannot go on the 1.2 milestone; 1.2
 is feature frozen.

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

-- 
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] #7936: Add Last-Modified header to feeds

[Django]

#7936: Add Last-Modified header to feeds
+---
  Reporter:  julianb| Owner:  julianb  
Status:  assigned   | Milestone:  1.2  
 Component:  RSS framework  |   Version:  1.2-alpha
Resolution: |  Keywords:  syndication last-modified
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

  * milestone:  => 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] #7936: Add Last-Modified header to feeds

[Django]

#7936: Add Last-Modified header to feeds
+---
  Reporter:  julianb| Owner:  julianb  
Status:  assigned   | Milestone:   
 Component:  RSS framework  |   Version:  1.2-alpha
Resolution: |  Keywords:  syndication last-modified
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

  * version:  1.0 => 1.2-alpha

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

-- 
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] r12657 - django/trunk/django/conf

[noreply]

Author: jezdez
Date: 2010-03-02 09:42:32 -0600 (Tue, 02 Mar 2010)
New Revision: 12657

Modified:
   django/trunk/django/conf/global_settings.py
Log:
Fixed Bosnian language code introduced in r12322.

Modified: django/trunk/django/conf/global_settings.py
===
--- django/trunk/django/conf/global_settings.py 2010-03-02 08:44:42 UTC (rev 
12656)
+++ django/trunk/django/conf/global_settings.py 2010-03-02 15:42:32 UTC (rev 
12657)
@@ -44,7 +44,7 @@
 ('ar', gettext_noop('Arabic')),
 ('bg', gettext_noop('Bulgarian')),
 ('bn', gettext_noop('Bengali')),
-('bn', gettext_noop('Bosnian')),
+('bs', gettext_noop('Bosnian')),
 ('ca', gettext_noop('Catalan')),
 ('cs', gettext_noop('Czech')),
 ('cy', gettext_noop('Welsh')),

-- 
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] #13009: provide django.forms field type info for use in templates

[Django]

#13009: provide django.forms field type info for use in templates
---+
 Reporter:  tvon   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 My use case is that it would be useful to have access to this info from
 templates when generating forms, eg:

 {{{

 {% for field in form.fields %}
 {% if field.type == 'checkbox' %}
   {# render one way... #}
 {% else %}
   {# render another way #}
 {% endif %}
 {% endfor %}

 }}}

 FWIW, django.contrib.admin seems to get around this problem in AdminField
 by adding an is_checkbox attribute, but it seems to me that the type of
 field being rendered should be easily available in the template, in other
 words, IMHO this makes sense as a core feature of django.forms.

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

-- 
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] #13008: @never_cache decorator should add 'no-cache' & 'must-revalidate'

[Django]

#13008: @never_cache decorator should add  'no-cache' & 'must-revalidate'
--+-
 Reporter:  harm  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Cache system  | Version:  1.2-beta  
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I noticed that the never_cache {{{ django/views/decorators/cache.py }}}
 does not add all the proper http headers to prevent that a page is cached.
 It just adds a max-age=0.  This does _not_ prevent browsers to actually
 cache that page.
 For example when hitting back, firefox will happily show such a page if
 the connection to the server disappeared.

 proposal, let never_cache() act as advertised: '''never''' cache. Let it
 add 'no-cache, must-revalidate' to the http response.

 something like: {{{ }}}
 {{{
 #!python
 --- virtualenv/src/django/django/utils/cache.py 2010-03-02
 15:11:54.0 +0100
 +++ /tmp/cache.py   2010-03-02 15:11:48.0 +0100
 @@ -104,6 +104,8 @@
  cache_timeout = settings.CACHE_MIDDLEWARE_SECONDS
  if cache_timeout < 0:
  cache_timeout = 0 # Can't have max-age negative
 +patch_cache_control(response, no_cache=True)
 +patch_cache_control(response, must_revalidate=True)
  if not response.has_header('ETag'):
  response['ETag'] = '"%s"' %
 md5_constructor(response.content).hexdigest()
  if not response.has_header('Last-Modified'):

 }}}

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

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