[Django] #12820: for param in request.REQUEST fails with (a misleading) KeyError exception

[Django]

#12820: for param in request.REQUEST fails with (a misleading) KeyError 
exception
---+
 Reporter:  sztamas|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 If you do a "for param in" on request.POST or request.GET it works as
 expected, but if you do it on request.REQUEST it fails.

 The following simple code

 {{{
 for param in request.REQUEST:
 print param
 }}}

 will throw a KeyError exception! A few WTFs later I realized that the
 problem is in django.util.datastructures.MergeDict, that doesn't implement
 __iter__, but it does implement __getitem__ so the for calls into
 __getitem__ and passes in 0 (index of first element in a sequence).
 0 won't be a valid key in request.GET or request.POST so a KeyError is
 thrown by the MergeDict.__getitem__ implementation.

 I've attached a patch that adds the missing __iter__ method.

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

-- 
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] #12072: Literal strings containing [, =] break {% url %}.

[Django]

#12072: Literal strings containing [,=] break {% url %}.
--+-
  Reporter:  emulbreh | Owner:  nobody 
Status:  new  | Milestone:  1.2
 Component:  Template system  |   Version:  1.1
Resolution:   |  Keywords:  url tag
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by eculver):

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

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

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

Re: [Django] #12731: Manager.raw() doesn't work with Multi-table inheritance

[Django]

#12731: Manager.raw() doesn't work with Multi-table inheritance
---+
  Reporter:  eric.buck...@gmail.com| Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  raw   
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * 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] #12791: Setting encoding on EmailMessage does not produce intended result

[Django]

#12791: Setting encoding on EmailMessage does not produce intended result
---+
  Reporter:  oyvind| Owner:  oyvind 
   
Status:  reopened  | Milestone:  1.2
   
 Component:  django.core.mail  |   Version:  SVN
   
Resolution:|  Keywords:  iso-8859-1 utf-8 
smart_str mail header
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * status:  closed => reopened
  * resolution:  duplicate =>
  * stage:  Unreviewed => Accepted

Comment:

 Apologies - you are correct. This is a different issue to #11924.

 Given that the two issues are distinct, please keep the patches separate.

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

-- 
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] #11924: Email headers always use the default encoding

[Django]

#11924: Email headers always use the default encoding
---+
  Reporter:  IanLewis  | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.core.mail  |   Version:  1.1   
Resolution:  duplicate |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Duplicate of #6918

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

-- 
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] #10216: TEMPLATE_DEBUG / TemplateSyntaxError handling doesn't play nice with Jinja2

[Django]

#10216: TEMPLATE_DEBUG / TemplateSyntaxError handling doesn't play nice with 
Jinja2
--+-
  Reporter:  miracle2k| Owner:  nobody
Status:  reopened | 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 russellm):

  * status:  closed => reopened
  * stage:  Unreviewed => Accepted
  * resolution:  wontfix =>
  * milestone:  => 1.2

Comment:

 Reopening following [http://groups.google.com/group/django-
 developers/browse_thread/thread/c75a02836743830e this thread on django
 dev].

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

-- 
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] #12819: Problem with commit 12307 and null onetoone fields

[Django]

#12819: Problem with commit 12307 and null onetoone fields
---+
  Reporter:  s.an...@twidi.com | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
select_related onetoone null
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by gav):

 * cc: gav (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] #12819: Problem with commit 12307 and null onetoone fields

[Django]

#12819: Problem with commit 12307 and null onetoone fields
---+
  Reporter:  s.an...@twidi.com | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
select_related onetoone null
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Comment (by s.an...@twidi.com):

 Ok here is an example
 {{{
 #!python
 class Image(models.Model):
 path = models.CharField(max_length=50)

 class Product(models.Model):
 name  = models.CharField(max_length=50)
 image = models.OneToOneField('Image', blank=True, null=True)
 }}}

 {{{
 #!python
 from mytestapp.model import Image, Product

 image1 = Image(path='image1')
 image1.save()

 product1 = Product(name='product1', image=image1)
 product1.save()

 # add a product without image
 product2 = Product(name='product2')
 product2.save()

 print '%d products' % len(Product.objects.all().select_related('image'))

 => AttributeError: 'NoneType' object has no attribute '_product_cache'

 # now set an image for the second product
 image2 = Image(path='image2')
 image2.save()

 product2.image = image2
 product2.save()

 print '%d products' % len(Product.objects.all().select_related('image'))

 => 2 products
 }}}

 Traceback for the AttribueError:
 {{{
 #!python
 /usr/local/lib/python2.6/dist-packages/django/db/models/query.pyc in
 __len__(self)
  77 self._result_cache = list(self._iter)
  78 else:
 ---> 79 self._result_cache = list(self.iterator())
  80 elif self._iter:
  81 self._result_cache.extend(list(self._iter))

 /usr/local/lib/python2.6/dist-packages/django/db/models/query.pyc in
 iterator(self)
 270 index_start, max_depth,
 271 requested=requested,
 offset=len(aggregate_select),
 --> 272 only_load=only_load)
 273 else:
 274 if skip:

 /usr/local/lib/python2.6/dist-packages/django/db/models/query.pyc in
 get_cached_row(klass, row, index_start, max_depth, cur_depth, requested,
 offset, only_load)
1207 # If the field is unique, populate the

1208 # reverse descriptor cache on the related object

 -> 1209 setattr(rel_obj, f.related.get_cache_name(), obj)
1210
1211 # Now do the same, but for reverse related objects.

 AttributeError: 'NoneType' object has no attribute '_product_cache'
 }}}

 No problem if a gave an image to product2. In my previous message i said
 "the first" because nn my complex app with many select_related, in some
 case the error doesn't occur, when the first row retrieved has a non-null
 value for the related field. But i can't do it with this short example,
 the error occurs all the time (if at less one image is null)

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

-- 
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] #5335: Add an append method to ErrorDict

[Django]

#5335: Add an append method to ErrorDict
---+
  Reporter:  Thomas Güttler   | Owner:  
nobody 
Status:  reopened  | Milestone:  1.2

 Component:  Forms |   Version:  SVN

Resolution:|  Keywords:  append 
errodict
 Stage:  Design decision needed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: miracle2k (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] #12645: UnicodeEncodeError when validating forms with non-ascii field names

[Django]

#12645: UnicodeEncodeError when validating forms with non-ascii field names
---+
  Reporter:  alanjds   | Owner:  unbracketed
Status:  assigned  | Milestone:  1.2
 Component:  Forms |   Version:  1.1
Resolution:|  Keywords:  unicode
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Comment (by alanjds):

 Replying to [comment:3 unbracketed]:
 > Patch doesn't cover all cases. For example, printing a form created with
 the same conditions (dynamically added field with a non-ASCII name) will
 also generate an exception.
 >

 Isn't this because of console encoding issues?. My console is configured
 to UTF-8, as seen:

 {{{
 alan...@lgpill:~$ locale
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR: pt: en_US: en
 LC_CTYPE="pt_BR.UTF-8"
 (...)
 LC_ALL="pt_BR.UTF-8"
 }}}

 When locale config was set as LANG=C, printing from ipython or simple
 python console throws exceptions yet.

 Could you post an example? I would like to try to reproduce this 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] #11700: actions and list_editables in popups problematic

[Django]

#11700: actions and list_editables in popups problematic
-+--
  Reporter:  sehmasch...@gmail.com   | Owner:  nobody
Status:  reopened| Milestone:
 Component:  django.contrib.admin|   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * status:  closed => reopened
  * version:  1.1 =>
  * resolution:  invalid =>
  * stage:  Unreviewed => Design decision needed

Comment:

 In light of the recent discussions regarding the state of Django's design,
 I'm reopening and marking this DDN.

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

-- 
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] #12819: Problem with commit 12307 and null onetoone fields

[Django]

#12819: Problem with commit 12307 and null onetoone fields
---+
  Reporter:  s.an...@twidi.com | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  
select_related onetoone null
 Stage:  Unreviewed| Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 I'm having difficulty parsing the prose description. A failing test would
 be extremely helpful.

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

-- 
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] #12818: sqlite3 backend should use single quotes for string values passed as args to django_date_trunc and django_extract

[Django]

#12818: sqlite3 backend should use single quotes for string values passed as 
args
to django_date_trunc and django_extract
---+
  Reporter:  lakinwecker   | Owner:  SmileyChris
Status:  assigned  | Milestone:  1.2
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords: 
 Stage:  Ready for checkin | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

  * owner:  nobody => SmileyChris
  * status:  new => assigned
  * stage:  Accepted => Ready for checkin
  * needs_tests:  1 => 0
  * 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] #12337: save_m2m() does not honor save_instance's exclude argument

[Django]

#12337: save_m2m() does not honor save_instance's exclude argument
-+--
  Reporter:  margieroginski  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ubernostrum):

 As Russ pointed out, the problem here is the technique you're trying to
 use: changing `Meta` partway through the life cycle of the form isn't, and
 won't be, supported. If you need to change the behavior of the form
 dynamically, you'll need to use a different approach (and for help on that
 try the django-users mailing list rather than the ticket tracker).

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

-- 
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] #12819: Problem with commit 12307 and null onetoone fields

[Django]

#12819: Problem with commit 12307 and null onetoone fields
--+-
 Reporter:  s.an...@twidi.com |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  select_related onetoone null  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The commit [12307] has a bug. If i use select_related with a
 OneToOneField?  which can be null, if for the FIRST object, this relation
 is null, then it's give me an error.

 A path is attached

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

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

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  closed| Milestone:  1.2

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

Resolution:  fixed |  Keywords:  
select_related onetoone reverse performance
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 The original issue here was fixed, please open a new bug for the new
 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] #12818: sqlite3 backend should use single quotes for string values passed as args to django_date_trunc and django_extract

[Django]

#12818: sqlite3 backend should use single quotes for string values passed as 
args
to django_date_trunc and django_extract
---+
  Reporter:  lakinwecker   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by lakinwecker):

 * cc: la...@structuredabstraction.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] #12818: sqlite3 backend should use single quotes for string values passed as args to django_date_trunc and django_extract

[Django]

#12818: sqlite3 backend should use single quotes for string values passed as 
args
to django_date_trunc and django_extract
---+
  Reporter:  lakinwecker   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by SmileyChris):

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

Comment:

 I can confirm the issue. It's pretty obvious what's going wrong (and well
 summarised in the title of this ticket)

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

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

[Django] #12818: sqlite3 backend should use single quotes for string values passed as args to django_date_trunc and django_extract

[Django]

#12818: sqlite3 backend should use single quotes for string values passed as 
args
to django_date_trunc and django_extract
--+-
 Reporter:  lakinwecker   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Test case models.py:
 {{{
 from django.db import models

 #--
 class SimpleModel(models.Model):
 month = models.PositiveIntegerField()
 some_date = models.DateTimeField()

 #--
 class SecondModel(models.Model):
 year = models.PositiveIntegerField()
 some_date = models.DateTimeField()

 }}}

 Test case admin.py:
 {{{
 from django.contrib import admin
 from datehierarchy.testbed.models import SimpleModel, SecondModel

 
#---
 class SimpleModelAdmin(admin.ModelAdmin):
 list_display = ('month', 'some_date',)
 date_hierarchy = 'some_date'

 admin.site.register(SimpleModel, SimpleModelAdmin)


 
#---
 class SecondModelAdmin(admin.ModelAdmin):
 list_display = ('year', 'some_date',)
 date_hierarchy = 'some_date'

 # Content Models
 admin.site.register(SecondModel, SecondModelAdmin)
 }}}

 Produces tracebacks like this even if valid dates are present:
 {{{
 Traceback:
 File "/home/lakin/Desktop/django/core/handlers/base.py" in get_response
   92. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/home/lakin/Desktop/django/contrib/admin/options.py" in wrapper
   226. return self.admin_site.admin_view(view)(*args,
 **kwargs)
 File "/home/lakin/Desktop/django/views/decorators/cache.py" in
 _wrapped_view_func
   44. response = view_func(request, *args, **kwargs)
 File "/home/lakin/Desktop/django/contrib/admin/sites.py" in inner
   186. return view(request, *args, **kwargs)
 File "/home/lakin/Desktop/django/contrib/admin/options.py" in
 changelist_view
   986. ], context, context_instance=context_instance)
 File "/home/lakin/Desktop/django/shortcuts/__init__.py" in
 render_to_response
   20. return HttpResponse(loader.render_to_string(*args, **kwargs),
 **httpresponse_kwargs)
 File "/home/lakin/Desktop/django/template/loader.py" in render_to_string
   108. return t.render(context_instance)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   178. return self.nodelist.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   779. bits.append(self.render_node(node, context))
 File "/home/lakin/Desktop/django/template/debug.py" in render_node
   71. result = node.render(context)
 File "/home/lakin/Desktop/django/template/loader_tags.py" in render
   97. return compiled_parent.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   178. return self.nodelist.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   779. bits.append(self.render_node(node, context))
 File "/home/lakin/Desktop/django/template/debug.py" in render_node
   71. result = node.render(context)
 File "/home/lakin/Desktop/django/template/loader_tags.py" in render
   97. return compiled_parent.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   178. return self.nodelist.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   779. bits.append(self.render_node(node, context))
 File "/home/lakin/Desktop/django/template/debug.py" in render_node
   71. result = node.render(context)
 File "/home/lakin/Desktop/django/template/loader_tags.py" in render
   24. result = self.nodelist.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   779. bits.append(self.render_node(node, context))
 File "/home/lakin/Desktop/django/template/debug.py" in render_node
   71. result = node.render(context)
 File "/home/lakin/Desktop/django/template/loader_tags.py" in render
   24. result = self.nodelist.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" in render
   779. bits.append(self.render_node(node, context))
 File "/home/lakin/Desktop/django/template/debug.py" in render_node
   71. result = node.render(context)
 File "/home/lakin/Desktop/django/template/__init__.py" i

Re: [Django] #5054: Calendar in admin interface doesn't display over dropdowns correctly in IE6

[Django]

#5054: Calendar in admin interface doesn't display over dropdowns correctly in 
IE6
---+
  Reporter:  Esaj  | Owner:  xian   
   
Status:  new   | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  calendar, internet 
explorer, dropdowns
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by yedpodtrzitko):

 What about jQuery bgiframe plugin, when there's implemented jQuery? (see
 ie6_bgiframe.diff)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12475: Confusion between list_display and list_display_link for 'id' field

[Django]

#12475: Confusion between list_display and list_display_link for 'id' field
---+
  Reporter:  master| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by szczav):

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

Comment:

 I presume that this strange behaviour is caused by the fact that you have
 used "list_display_link" instead of "list_display_links" ('s' at the end).
 It is no bug, but small oversight :)

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

-- 
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] #12815: Add a lazy TemplateResponse

[Django]

#12815: Add a lazy TemplateResponse
-+--
  Reporter:  russellm| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by carljm):

 * cc: carljm (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] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  reopened  | Milestone:  1.2

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

Resolution:|  Keywords:  
select_related onetoone reverse performance
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: s.an...@twidi.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] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  reopened  | Milestone:  1.2

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

Resolution:|  Keywords:  
select_related onetoone reverse performance
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by s.an...@twidi.com):

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

Comment:

 The commit [12307] has a bug. If i use select_related with a OneToOneField
 which can be null, if for the FIRST object, this relation is null, then
 it's give me an error

 A path is joined

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

-- 
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] #12810: ManyToManyField.db_table

[Django]

#12810: ManyToManyField.db_table
+---
  Reporter:  strelnikovdmitrij  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords:  ManyToManyField
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by strelnikovdmitrij):

 don't know how to edit :/

 running syncdb. after ...

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

-- 
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] #12651: AutoSlugField, that can recreate unique slugs during saving.

[Django]

#12651: AutoSlugField, that can recreate unique slugs during saving.
+---
  Reporter:  Ciantic| Owner:  nobody   
Status:  new| Milestone:  1.2  
 Component:  Uncategorized  |   Version:  1.2-alpha
Resolution: |  Keywords:   
 Stage:  Unreviewed | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Comment (by Ciantic):

 There is also one in [http://github.com/django-extensions/django-
 extensions/blob/master/django_extensions/db/fields/__init__.py django-
 extensions] but these utility libraries has been weak in past as the
 maintainers tend to loose interest.

 One idea would perhaps to officially support/maintain some extension
 library, a bit in same way as WPF (Windows Presentation Foundation) has
 put up a WPF Toolkit where features trickles down after maturing to real
 .NET.

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

-- 
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] #12817: email validator is maybe too stingy (u...@hostname fails)

[Django]

#12817: email validator is maybe too stingy (u...@hostname fails)
+---
 Reporter:  tvon|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.1   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I realize people don't tend to have email addresses without TLDs these
 days, but all the same it's legal and potentially useful for development.
 For example, if u...@localhost is allowed, you don't need anything more
 than local delivery.

 A brief mention on IRC indicated there probably isn't any real interest in
 a change like this, but I thought I'd toss it out there anyway.

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

-- 
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] #12337: save_m2m() does not honor save_instance's exclude argument

[Django]

#12337: save_m2m() does not honor save_instance's exclude argument
-+--
  Reporter:  margieroginski  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by margieroginski):

 Are you sure it even works to specify an m2m field in the exclude list?
 Since exclude is not even used in save_m2m, it seems it would not honor
 exclude even if specified statically.

 In any case, I don't see why you wouldn't want to honor exclude on an m2m
 field when specified dynamically as I described in my example above.   It
 seems like very inconsistent behavior to not honor exclude for an m2m
 field and it seems that a simple and backward compatible fix like the one
 I suggested to could be added to solve the problem.

 I don't agree this should be closed, I hope you will reconsider it.

 Thanks,
 Margie

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

-- 
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] #11463: Vietnamese translation

[Django]

#11463: Vietnamese translation
+---
  Reporter:  Erik Unger   | Owner: 
Status:  new| Milestone: 
 Component:  Translations   |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by clouserw):

  * owner:  clouserw =>
  * needs_better_patch:  1 => 0
  * 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] #11463: Vietnamese translation

[Django]

#11463: Vietnamese translation
+---
  Reporter:  Erik Unger   | Owner:  clouserw
Status:  assigned   | Milestone:  
 Component:  Translations   |   Version:  SVN 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  1  |  
+---
Changes (by clouserw):

 * cc: clous...@gmail.com (added)
  * owner:  nobody => clouserw
  * version:  1.0 => SVN
  * status:  new => assigned

Comment:

 I'm attaching a patch against trunk incorporating the original patch,
 fixing some syntax errors, and rolling in some additional changes from
 Nguyễn Mạnh Hùng.

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

-- 
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] #12815: Add a lazy TemplateResponse

[Django]

#12815: Add a lazy TemplateResponse
-+--
  Reporter:  russellm| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by jezdez):

  * needs_tests:  0 => 1

Comment:

 For the record I'm +1 on that, really like the idiom.

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

-- 
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] #12363: Add add() method to ErrorDict class

[Django]

#12363: Add add() method to ErrorDict class
+---
  Reporter:  miracle2k  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Forms  |   Version:
Resolution:  duplicate  |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 Dupe of #5335.

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

-- 
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] #12382: Deleting an inline can delete the whole inlined model instance recursively

[Django]

#12382: Deleting an inline can delete the whole inlined model instance 
recursively
---+
  Reporter:  deschler  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.1  
Resolution:|  Keywords:  admin inlines
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 The deletion itself is a case of working as designed. #7539 exists to
 address the control of delete cascading behavior.

 This leaves the UI problem - if deleting an inline leads to deleting the
 base object, you shouldn't get a 404. We track the objects that are going
 to be deleted; that could be used as a basis for redirection (i.e., if
 self on list, redirect to the "model" page in the admin)

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

-- 
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] #12375: updating QueryDict in another dict gives unexpected results.

[Django]

#12375: updating QueryDict in another dict gives unexpected results.
+---
  Reporter:  hvdklauw   | Owner:  nobody   
Status:  new| Milestone:   
 Component:  HTTP handling  |   Version:  1.1  
Resolution: |  Keywords:  QueryDict
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This is an interesting discrepancy.

 I'm inclined to agree with your analysis - my_dict.update(request.POST)
 should only update values - but it's out of our hands. The python
 internals dictate the behavior in this case.

 Your workaround seems reasonable - i.e., add a dict() method to QueryDict
 (strictly, to MultiValueDict) that provides a dictionary of key-value
 pairs, rather than key-list pairs.

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

-- 
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] #12369: cStringIO portability

[Django]

#12369: cStringIO portability
+---
  Reporter:  rubic  | Owner:  nobody   
Status:  new| Milestone:   
 Component:  Documentation  |   Version:  1.1  
Resolution: |  Keywords:  cStringIO portability
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #12363: Add add() method to ErrorDict class

[Django]

#12363: Add add() method to ErrorDict class
+---
  Reporter:  miracle2k  | Owner:  nobody
Status:  new| Milestone:
 Component:  Forms  |   Version:
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Broadly accepting the idea that the interface to dealing with ErrorDict
 can be improved, but I'm not sold on the specific API that has been
 proposed.

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

-- 
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] #12359: db/models/fields/related.py hardcodes m2m help_text for select widget

[Django]

#12359: db/models/fields/related.py hardcodes m2m help_text for select widget
+---
  Reporter:  olau   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #12346: Docs should cover validaton of model inline formsets

[Django]

#12346: Docs should cover validaton of model inline formsets
+---
  Reporter:  johnsmith  | Owner:  nobody
 
Status:  new| Milestone:
 
 Component:  Documentation  |   Version:  1.1   
 
Resolution: |  Keywords:  inlineformset_factory, 
BaseInlineFormSet validation
 Stage:  Accepted   | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 Good idea, wrong place. The first line of the InlineFormSet docs say that
 InlineFormSets are "a small abstraction layer on top of model formsets",
 so the right place to document this is in ModelFormSets. There currently
 isn't any mention of the fact that ModelFormSets call the clean method on
 constituent 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.

Re: [Django] #12343: manage.py dbshell fails to launch mysql for unix socket

[Django]

#12343: manage.py dbshell fails to launch mysql for unix socket
-+--
  Reporter:  elyon...@gmail.com  | Owner:  nobody   
Status:  new | Milestone:  1.2  
 Component:  Uncategorized   |   Version:  1.1  
Resolution:  |  Keywords:  dbshell mysql
 Stage:  Accepted| Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted
  * 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] #12337: save_m2m() does not honor save_instance's exclude argument

[Django]

#12337: save_m2m() does not honor save_instance's exclude argument
-+--
  Reporter:  margieroginski  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 Your suspicion is correct - you can't dynamically change the Meta class
 and expect those changes to be reflected in the model.

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

-- 
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] #11058: list_display_links doesn't allow callables not defined in the model

[Django]

#11058: list_display_links doesn't allow callables not defined in the model
---+
  Reporter:  dvine | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by philomat):

 Even more strangely, but a workaround: In your model, define a method
 'change_list_status' that does nothing at all. Now you can add
 'change_list_status', which is a callable of the admin class, to
 list_display_links and it works as.

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

-- 
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] #12333: CheckboxInput don't work with 0 and 1 value (considerd as Booleans)

[Django]

#12333: CheckboxInput don't work with 0 and 1 value (considerd as Booleans)
-+--
  Reporter:  alexis_m| Owner:  nobody   
Status:  closed  | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  invalid |  Keywords:  CheckboxInput Boolean
 Stage:  Unreviewed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 Marking invalid because I'm completely confused as to the problem here.
  * The original report doesn't give the use case that causes this to be an
 issue
  * The patch isn't generated against the root of the source tree
  * There's no test case to validate the new behavior (or explain the
 problem)
  * I can't see the connection between the problem report and the first
 comment.

 Feel free to reopen if you can provide 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] #12302: Exception with utf8 message leads to DjangoUnicodeDecodeError

[Django]

#12302: Exception with utf8 message leads to DjangoUnicodeDecodeError
+---
  Reporter:  bjourne| Owner:  nobody
Status:  reopened   | 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 kmtracey):

  * stage:  Unreviewed => Accepted
  * 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] #12302: Exception with utf8 message leads to DjangoUnicodeDecodeError

[Django]

#12302: Exception with utf8 message leads to DjangoUnicodeDecodeError
+---
  Reporter:  bjourne| Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 I think I know what this is.  It's a recurrence of the problem fixed by
 r8588 that happens when running under Python 2.6.  Prior to 2.6 (or with
 2.5 at any rate), Exceptions did not have unicode methods, with 2.6 they
 do. The r8588 special-casing for Exceptions was made only in the path that
 applies to objects without unicode methods, thus it is no longer working
 under 2.6.  (Having a unicode method under 2.6 is also why the original
 traceback is now completely absent in !TemplateSyntaxErrors that wrap
 other exceptiosn -- the code to include the original traceback in the
 exception value is in an `__str__` method, and 2.6 no longer calls that.
 But that's a different problem than this one, and there's also another
 ticket open for that.)

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

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

[Django]

#12813: Invalid documentation link.
+---
  Reporter:  subhranath | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Those links are auto-generated. They don't work when a particular page of
 doc does not exist in a different version, as is the case here. To find
 current doc on validation, use the doc search feature.

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

-- 
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] #12816: Add a render() shortcut

[Django]

#12816: Add a render() shortcut
-+--
  Reporter:  russellm| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * component:  Uncategorized => Core framework
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 [http://groups.google.com/group/django-
 developers/browse_thread/thread/ec6a62f6827b428c  Jacob, Simon, and others
 are on the record as being in favor]. The only hesitation is the
 relationship with #12815; we should resolve that decision before
 committing anything for this ticket.

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

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

[Django] #12816: Add a render() shortcut

[Django]

#12816: Add a render() shortcut
---+
 Reporter:  russellm   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 render_to_response(template, view,
 context_instance=RequestContext(request)) is such a common idiom that it
 deserves a shortcut of it's own.

 Related: #12815 If we're going to introduce a new TemplateResponse, it
 might be appropriate for a new render() shortcut to return that class.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12332: {% blocktrans with value as variable %} syntax cannot parse literal values passed through filters

[Django]

#12332: {% blocktrans with value as variable %} syntax cannot parse literal 
values
passed through filters
--+-
  Reporter:  Alun Bestor  | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Template system  |   Version:  SVN
Resolution:   |  Keywords:  blocktrans i18n
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

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

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

Re: [Django] #12329: "template" view decorator, allows to completely isolate views from templates

[Django]

#12329: "template" view decorator, allows to completely isolate views from
templates
+---
  Reporter:  gurunars   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 This has been requested several times, and rejected. I (and others in the
 core) simply don't see that using decorators in this way makes anything
 clearer.

 The current contract for a view is that it accepts a request, returns a
 response. If you use a decorator to modify templates, this contract
 becomes "returns a response, or a response holder, or a dictionary". This
 isn't an improvement.

 An alternate proposal that *does* have some support in the core is the
 idea of a TemplateResponse - that is, that you can return a response whose
 template will be lazily evaluated, allowing decorators, middlewares, or
 view wrappers to modify the template that is used. This means a view can
 return a template and a context, but the actual template that is used can
 be modified by something higher up in the chain. For details, see ticket
 #12815.

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

-- 
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] #12815: Add a lazy TemplateResponse

[Django]

#12815: Add a lazy TemplateResponse
-+--
  Reporter:  russellm| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

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

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

[Django] #12815: Add a lazy TemplateResponse

[Django]

#12815: Add a lazy TemplateResponse
+---
 Reporter:  russellm|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Proposal from Simon Willison:

 Summary: Add a TemplateResponse class - a response that contains a
 template and context, but doesn't evaluate the template until it is
 required (or explicitly 'baked'). This allows middlewares, decorators, or
 view wrappers to change the template.
 
 The original proposal comes from [http://groups.google.com/group/django-
 developers/msg/b1b3f8854b9ae2b1 this django-users thread], in the context
 of making CSRF easier to use. Simon said:

 I've been experimenting recently with  a TemplateResponse class which lets
 you do this:
 {{{
 def view(request):
 return TemplateResponse(request, 'my_template.html', {'foo': 'bar'})
 }}}

 It's an HttpResponse class that's designed to be lazily evaluated.  This
 makes it really useful for subclassing - you can do things like  this:
 {{{
 class MyGenericView(object):
def view(self, request):
# Do something complicated
return TemplateResponse(request, 'my_template.html', {'foo':
 'bar'})
 class MyCustomisedView(object):
def view(self, request):
response = super(MyCustomisedView, self).view(request)
response.context['foo'] = 'baz'
if is_mobile_phone(request):
response.template = 'my_mobile_template.html'
return response
 }}}
 This pattern would be particularly valuable for customising the admin,
 which currently uses nasty extra_context argument hacks to achieve
 something that isn't nearly as useful.

 My current implementation of TemplateResponse is [http://github.com/simonw
 /django-openid/blob/master/django_openid/response.py here] - there's a
 SimpleTemplateResponse as well which doesn't use RequestContext (but has a
 more verbose name to discourage its use).

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

-- 
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] #12328: subqueries in django 1.1 behave oddly

[Django]

#12328: subqueries in django 1.1 behave oddly
---+
  Reporter:  wdoekes   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 #12814 is a duplicate, albeit with a different presentation.

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

-- 
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] #12814: Missing ORDER BY in subselect

[Django]

#12814: Missing ORDER BY in subselect
---+
  Reporter:  EsOsO | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 This is effectively the same problem as #12328.

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

-- 
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] #12327: Internationalization documentation specifies common middleware after session middleware

[Django]

#12327: Internationalization documentation specifies common middleware after
session middleware
+---
  Reporter:  portante   | Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Documentation  |   Version:  1.1   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 There's no reason that CommonMiddleware should go first or last. Like most
 middlewares, it has no dependencies, which is why the middleware
 documentation doesn't mention any. There are only a couple of middlewares
 that are order specific - LocaleMiddleware being one of them.

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

-- 
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] #6483: Support European date format for JavaScript

[Django]

#6483: Support European date format for JavaScript
-+--
  Reporter:  Bastian Kleineidam   | Owner:  
garcia_marc
Status:  closed  | Milestone:   
  
 Component:  Internationalization|   Version:  
SVN
Resolution:  fixed   |  Keywords:  
i18n-rf
 Stage:  Accepted| Has_patch:  
1  
Needs_docs:  0   |   Needs_tests:  
0  
Needs_better_patch:  1   |  
-+--
Changes (by yedpodtrzitko):

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

Comment:

 fixed in [11964]

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

-- 
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] #12325: [PATCH]Allow zero moderate_after time

[Django]

#12325: [PATCH]Allow zero moderate_after time
--+-
  Reporter:  zhigang  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.comments  |   Version:  1.1   
Resolution:   |  Keywords:  moderation
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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] #12321: CharField default is a str and not unicode

[Django]

#12321: CharField default is a str and not unicode
---+
  Reporter:  bjourne   | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * 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] #12318: Non existent link on Django weblog

[Django]

#12318: Non existent link on Django weblog
--+-
  Reporter:  venkitaswaran| Owner:  nobody
Status:  closed   | Milestone:
 Component:  Django Web site  |   Version:
Resolution:  fixed|  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Blog entry has been corrected.

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

-- 
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] #12315: DateField incorrectly handled by administration site

[Django]

#12315: DateField incorrectly handled by administration site
---+
  Reporter:  toplex| Owner:  nobody 

Status:  closed| Milestone: 

 Component:  django.contrib.admin  |   Version:  1.1

Resolution:  invalid   |  Keywords:  date DateField 
admin date_hierarchy
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 I strongly suspect that there is a timezone configuration issue here. The
 giveaway is that when you're on the 'today' filtering page, it's showing
 articles created on the 13th, even when the system clock says the 14th.

 Django's default configuration file sets the timezone to America/Chicago,
 and this will affect the data stored in the database. If you're in a
 timezone ahead of Chicago (which is to say, most of them) your system
 clock will say it's the 14th, but Django and the database stack will say
 it's the 13th. If you're in a timezone behind Chicago, the opposite will
 happen.

 If you set your settings.TIME_ZONE setting to your local timezone, the
 problem should go away.

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

-- 
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] #12313: Mention some cautions in section overriding delete()

[Django]

#12313: Mention some cautions in section overriding delete()
+---
  Reporter:  FunkyELF   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.1 
Resolution: |  Keywords:  delete admin signals
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 A note to this effect already exists in the queryset.delete()
 documentation (which you can get to if you follow the links from the
 "overriding model methods" page), but I agree it's worth repeating -- or
 at least drawing attention to the existing docs.

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

-- 
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] #12320: Translations hints in HTML are lost in PO file

[Django]

#12320: Translations hints in HTML are lost in PO file
---+
  Reporter:  bronger   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Internationalization  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12312: MultiLineString OGRGeometry dimensions change on transform

[Django]

#12312: MultiLineString OGRGeometry dimensions change on transform
---+
  Reporter:  yourcelf  | Owner:  jbronn 
Status:  assigned  | Milestone: 
 Component:  GIS   |   Version:  SVN
Resolution:|  Keywords:  gdal OGRGeometry 3D
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12308: Adding tablespace support to postgres backends

[Django]

#12308: Adding tablespace support to postgres backends
---+
  Reporter:  tclineks  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by russellm):

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

Comment:

 Accepted for the same reason #6148 was accepted.

 Patch needs improvement, though. If we're going to allow tablespaces, it
 shouldn't be just as a default value. You should be able to override on a
 per-model basis.

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

-- 
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] #12307: GeoDjango test suite fails for SpatialRefSys model objects

[Django]

#12307: GeoDjango test suite fails for SpatialRefSys model objects
---+
  Reporter:  tylere| Owner:  nobody   
Status:  new   | Milestone:   
 Component:  GIS   |   Version:  SVN  
Resolution:|  Keywords:  SpatialRefSys TOWGS84
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

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

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

Re: [Django] #12306: Checkbox (label, field) ordering

[Django]

#12306: Checkbox (label, field) ordering
-+--
  Reporter:  EoghanM | Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  Forms   |   Version:  1.1  
  
Resolution:  |  Keywords:  label checkbox 
BooleanField
 Stage:  Design decision needed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 I acknowledge the problem, but I'm not sure what the solution should be.

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

-- 
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] #12302: Exception with utf8 message leads to DjangoUnicodeDecodeError

[Django]

#12302: Exception with utf8 message leads to DjangoUnicodeDecodeError
+---
  Reporter:  bjourne| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I can't reproduce this problem. I don't deny that the problem exists
 (since at least one person has been able to reproduce it), but the stack
 trace and comment doesn't give enough detail to explain how to reproduce
 the problem. If you can provide instructions on how to reproduce the
 problem, please reopen.

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

-- 
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] #12293: mysql backend raises Warning exceptions for ignorable info notices

[Django]

#12293: mysql backend raises Warning exceptions for ignorable info notices
---+
  Reporter:  wdoekes   | Owner:  nobody 

Status:  closed| Milestone: 

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

Resolution:  wontfix   |  Keywords:  mysql 
warnings note
 Stage:  Unreviewed| Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

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

Comment:

 I disagree that Django should be throwing away data returned by the
 cursor. If you don't want notes to be reported by the cursor, might I
 suggest the use of the [http://dev.mysql.com/doc/refman/5.1/en/server-
 session-variables.html#sysvar_sql_notes sql_notes variable].

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

-- 
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] #12291: Order of app_store items should mirror INSTALLED_APPS

[Django]

#12291: Order of app_store items should mirror INSTALLED_APPS
---+
  Reporter:  phuihock  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 While we *could* do this, I'm not convinced it's desirable to do so. It
 suggests that the primary key values of auth_permission and
 django_content_type should be predicable. In the broader 'reusable app'
 context, this will *never* be true, so any code that is dependent on
 predictable ordering like this should be considered in error. Hiding the
 problem by making the order predictable in certain contexts would only
 serve to hide errors from the early phases of development that will emerge
 later on.

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

-- 
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] #12290: Give an example for a default ordering of built-in Django middleware

[Django]

#12290: Give an example for a default ordering of built-in Django middleware
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  wontfix|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 There are only a couple of middlewares that are order dependent (e.g.,
 GzipMiddleware, TransactionMiddleware), and their documentation describes
 that order dependence. Otherwise, the order is either unimportant, or
 entirely dependent on what you are trying to achieve.

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

-- 
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] #12286: Table for Model that has been proxied may not be created

[Django]

#12286: Table for Model that has been proxied may not be created
---+
  Reporter:  telenieko | Owner:  nobody
Status:  new   | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * 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] #12283: Inclusion tags should handle arguments not present in the context gracefully

[Django]

#12283: Inclusion tags should handle arguments not present in the context
gracefully
--+-
  Reporter:  kuon | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  1.1   
Resolution:  duplicate|  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Duplciate of #12212

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

-- 
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] #12280: working with forms example should include editing an existing instance

[Django]

#12280: working with forms example should include editing an existing instance
+---
  Reporter:  johnsmith  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 The suggested location is wrong as the docs referenced are talking about
 forms, not modelforms. However, the
 [http://docs.djangoproject.com/en/dev/topics/forms/modelforms/#a-full-
 example full example of modelforms] could do with such an example.

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

-- 
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] #12814: Missing ORDER BY in subselect

[Django]

#12814: Missing ORDER BY in subselect
--+-
 Reporter:  EsOsO |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Python 2.6.4 (r264:75706, Dec  7 2009, 18:45:15)
 {{{
 >>> from django.db import connection
 >>> from pokertour.models import Session, Entry
 >>> s = Session.objects.all()[:4]
 >>> s
 [, , ,
 ]
 >>> e = Entry.objects.filter(session__in=s)
 >>> e
 [, , ,
 , , ,
 , , ,
 , , ,
 , , ,
 , , ,
 , , '...(remaining elements
 truncated)...']
 >>> connection.queries
 [{'time': '0.005', 'sql': 'SELECT "pokertour_session"."id",
 "pokertour_session"."name", "pokertour_session"."slug",
 "pokertour_session"."date", "pokertour_session"."location_id" FROM
 "pokertour_session" ORDER BY "pokertour_session"."date" DESC LIMIT 4'},
 {'time': '0.004', 'sql': 'SELECT "pokertour_entry"."id",
 "pokertour_entry"."player_id", "pokertour_entry"."session_id",
 "pokertour_entry"."cash_in", "pokertour_entry"."cash_out",
 "pokertour_entry"."bank_in", "pokertour_entry"."stack" FROM
 "pokertour_entry" WHERE "pokertour_entry"."session_id" IN (SELECT U0."id"
 FROM "pokertour_session" U0 LIMIT 4) LIMIT 21'}]
 >>>
 }}}


 The subquery should return the same records as the first, instead it loses
 the order by clause:[[BR]]
 ...FROM "pokertour_session" ORDER BY "pokertour_session"."date" DESC LIMIT
 4[[BR]]

 ...FROM "pokertour_session" U0 LIMIT 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.

Re: [Django] #7609: PositiveIntegerField and co have a misleading name

[Django]

#7609: PositiveIntegerField and co have a misleading name
-+--
  Reporter:  Gergely Kontra   |  
   Owner:  nobody 
Status:  new | 
Milestone: 
 Component:  Forms   |  
 Version:  SVN
Resolution:  |  
Keywords:  name convention, rename
 Stage:  Design decision needed  | 
Has_patch:  0  
Needs_docs:  0   |   
Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by programmerq):

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

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

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

Re: [Django] #12804: decorating admin views doesn't work

[Django]

#12804: decorating admin views doesn't work
+---
  Reporter:  apollo13   | Owner:  nobody
Status:  reopened   | Milestone:  1.2   
 Component:  Uncategorized  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by apollo13):

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

Comment:

 Reopening after discussion on the ml: http://groups.google.com/group
 /django-developers/browse_thread/thread/3024b14a47f5404d

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

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