Re: [Django] #15652: dictsort raises TemplateSyntaxError when not provided with a list of dictionaries

2011-03-21 Thread Django
#15652: dictsort raises TemplateSyntaxError when not provided with a list of
dictionaries
---+---
   Reporter:  notifications@…  |Owner:  nobody
 Status:  new  |Milestone:
  Component:  Template system  |  Version:  1.3-rc1
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by julien):

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



Re: [Django] #15653: minor errors in admin pagination custom tag

2011-03-21 Thread Django
#15653: minor errors in admin pagination custom tag
+--
   Reporter:  jcumbo@…  |Owner:  nobody
 Status:  new   |Milestone:
  Component:  django.contrib.admin  |  Version:  1.1
 Resolution:| Keywords:  pagination
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  1
Patch needs improvement:  0 |
+--
Changes (by julien):

 * has_patch:  0 => 1


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

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



Re: [Django] #15653: minor errors in admin pagination custom tag

2011-03-21 Thread Django
#15653: minor errors in admin pagination custom tag
+--
   Reporter:  jcumbo@…  |Owner:  nobody
 Status:  new   |Milestone:
  Component:  django.contrib.admin  |  Version:  1.1
 Resolution:| Keywords:  pagination
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  1
Patch needs improvement:  0 |
+--
Changes (by julien):

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


Comment:

 Tests need to be written to prove that the end result remains unchanged
 after this fix :-)

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

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



Re: [Django] #15640: New initial digit in Spain phone numbers

2011-03-21 Thread Django
#15640: New initial digit in Spain phone numbers
-+-
   Reporter:  fenikso|Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  1.3-rc1
  django.contrib.localflavor | Keywords:  phone digit
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by julien):

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


Comment:

 Accepting as per
 http://en.wikipedia.org/wiki/Telephone_numbers_in_Spain#Mobile_Phones

 Could you please post a diff patch instead of the whole modified file?
 Please also provide some tests.

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

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



Re: [Django] #6896: Add ability to store only relative paths in a FilePathField

2011-03-21 Thread Django
#6896: Add ability to store only relative paths in a FilePathField
-+-
   Reporter: |Owner:  nobody
  graham.carlyle@…   |Milestone:
 Status:  new|  Version:  SVN
  Component:  Database   | Keywords:
  layer (models, ORM)|Has patch:  1
 Resolution: |  Needs tests:  0
   Triage Stage:  Design |
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-

Comment (by FunkyBob):

 On top of all the above, using relative paths also makes it easier if you
 want to present a URL to the file ... you no longer need to strip the
 common prefix.

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

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



[Django] #15655: (pylibmc) cache.set() hangs

2011-03-21 Thread Django
#15655: (pylibmc) cache.set() hangs
--+---
 Reporter:  fahhem| Owner:  nobody
   Status:  new   | Milestone:
Component:  Cache system  |   Version:  1.3-rc1
 Keywords:  pylibmc   |  Triage Stage:  Unreviewed
Has patch:  0 |
--+---
 My setup is a localhost memcached server on the default port:

 {{{
 CACHES = {
 'default': {
 'BACKEND':'django.core.cache.backends.memcached.PyLibMCCache',
 'LOCATION':'127.0.0.1:11211',
 }
 }
 }}}

 When the backend changes to MemcachedCache, the problem goes away so this
 is definitely pylibmc. I did this exact setup on two different projects
 and two separate machines over the span of the last two weeks and I ran
 into this same problem both times:

 When using cache.set(key,value,timeout), some keys will hang the
 thread/process when served through Apache (v2.2.16-1ubuntu3.1). When using
 ./manage.py runserver or runserver_plus, cache.set() works and when I
 switch from runserver to apache it works fine because cache.get() gets the
 value and no cache.set() is called. When the timeout passes, apache again
 hangs at the same cache.set(). I used a ton of logging.error() calls to
 find where apache hangs.

 This machine is Ubuntu but the first machine with the problem was a Debian
 machine, both are running mostly stable, with a few non-critical packages
 from testing. Both run python2.6 and django 1.3, the first machine was
 1.3-beta-1, this one had the problem in both beta and rc.

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

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



[Django] #15654: qs.delete() fails if a model isn't in INSTALED_APPS and the related objects cache is already filled.

2011-03-21 Thread Django
#15654: qs.delete() fails if a model isn't in INSTALED_APPS and the related 
objects
cache is already filled.
--+---
 Reporter:  apollo13  | Owner:  nobody
   Status:  new   | Milestone:
Component:  Database layer (models, ORM)  |   Version:  SVN
 Keywords:|  Triage Stage:  Unreviewed
Has patch:  0 |
--+---
 ContentType.objects.delete() fails for use since 1.3 (on_delete support to
 be exact) since it tries to delete all related objects pointing to that
 contenttype. If one of the related models is not in INSTALLED_APPS (in our
 case django.contrib.auth), this can fail if the model got imported (which
 registers it etc…; in our case django.contrib.contenttypes.generic
 imported auth.models -- via contrib.admin). Attached is a testcase
 showcasing the issue.

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

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



Re: [Django] #12635: Process HTTP PUT into request.FILES and request.PUT as done for POST

2011-03-21 Thread Django
#12635: Process HTTP PUT into request.FILES and request.PUT as done for POST
--+--
   Reporter:  boxm|Owner:  nobody
 Status:  new |Milestone:  1.4
  Component:  HTTP handling   |  Version:  SVN
 Resolution:  | Keywords:  PUT
   Triage Stage:  Design decision needed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--
Changes (by julien):

 * stage:  Accepted => Design decision needed


Comment:

 In this thread, Malcolm Tredinnick explains why the current behaviour is
 by design: http://groups.google.com/group/django-
 developers/browse_thread/thread/771238a95ceb058e/

 He argues that `request.raw_post_data` should be used for handling any
 data coming through REST calls.

 Moving as DDN for now.

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

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



[Django] #15653: minor errors in admin pagination custom tag

2011-03-21 Thread Django
#15653: minor errors in admin pagination custom tag
--+---
 Reporter:  jcumbo@…  | Owner:  nobody
   Status:  new   | Milestone:
Component:  django.contrib.admin  |   Version:  1.1
 Keywords:  pagination|  Triage Stage:  Unreviewed
Has patch:  0 |
--+---
 in django.contrib.admin.templates.admin.templatetags.admin_list.py line
 48, which currently reads
 {{{
 "page_range.extend(range(0, ON_EACH_SIDE - 1))"
 }}}
  should read[[BR]]

 {{{
 "page_range.extend(range(0, ON_ENDS))"
 }}}
  instead. [[BR]]
 Problem is noticeable if you change ON_EACH_SIDE to a value to 2.

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

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



[Django] #15652: dictsort raises TemplateSyntaxError when not provided with a list of dictionaries

2011-03-21 Thread Django
#15652: dictsort raises TemplateSyntaxError when not provided with a list of
dictionaries
-+---
 Reporter:  notifications@…  | Owner:  nobody
   Status:  new  | Milestone:
Component:  Template system  |   Version:  1.3-rc1
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  0|
-+---
 For example, if one puts {{ "Hello"|dictsort:"a" }} into a template and
 render it, it will raise TemplateSyntaxError with Caught
 VariableDoesNotExist while rendering: Failed lookup for key [a] in u'H'.
 It should fail silently.

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

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



Re: [Django] #15496: "Content-Transfer-Encoding: base64" not honored when uploading files

2011-03-21 Thread Django
#15496: "Content-Transfer-Encoding: base64" not honored when uploading files
-+-
   Reporter:  gene@… |Owner:  nobody
 Status:  new|Milestone:
  Component:  HTTP   |  Version:  1.2
  handling   | Keywords:  base64 file upload
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by tomchristie):

 * cc: tomchristie (added)


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

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



Re: [Django] #12635: Process HTTP PUT into request.FILES and request.PUT as done for POST

2011-03-21 Thread Django
#12635: Process HTTP PUT into request.FILES and request.PUT as done for POST
-+--
   Reporter:  boxm   |Owner:  nobody
 Status:  new|Milestone:  1.4
  Component:  HTTP handling  |  Version:  SVN
 Resolution: | Keywords:  PUT
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by tomchristie):

 * cc: tomchristie (added)
 * milestone:  1.3 => 1.4


Comment:

 Presumably this ought to be Milestone 1.4 now, right?

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

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



Re: [Django] #5423: "dumpdata" should stream output one row at a time

2011-03-21 Thread Django
#5423: "dumpdata" should stream output one row at a time
-+-
   Reporter:  adrian |Owner:  ramiro
 Status:  assigned   |Milestone:
  Component: |  Version:  SVN
  Serialization  | Keywords:  dumpdata fixtures
 Resolution: |  memory
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by tomchristie):

 * cc: tomchristie (added)


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

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



Re: [Django] #4656: Allow In-depth serialization by specifying depth to follow relationship

2011-03-21 Thread Django
#4656: Allow In-depth serialization by specifying depth to follow relationship
--+---
   Reporter:  jay.m.martin@…  |Owner:  nobody
 Status:  new |Milestone:
  Component:  Serialization   |  Version:
 Resolution:  | Keywords:  feature
   Triage Stage:  Accepted|Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+---
Changes (by tomchristie):

 * cc: tomchristie (added)


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

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



Re: [Django] #12747: Custom HTTP status reason phrases are not supported

2011-03-21 Thread Django
#12747: Custom HTTP status reason phrases are not supported
-+-
   Reporter:  Gustavo|Owner:  gisle
 Status:  new|Milestone:
  Component:  HTTP   |  Version:  1.1
  handling   | Keywords:  http status, http
 Resolution: |  status reason, http status reason
   Triage Stage:  Accepted   |  phrase
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  0  |  Needs tests:  0
-+-
Changes (by akvadrako):

 * cc: akvadrako (added)


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

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



Re: [Django] #15288: ManyToManyField doesn't highlight currently selected items in Admin where target is a proxy object.

2011-03-21 Thread Django
#15288: ManyToManyField doesn't highlight currently selected items in Admin 
where
target is a proxy object.
--+--
   Reporter:  anonymous   |Owner:  nobody
 Status:  closed  |Milestone:
  Component:  Forms   |  Version:  1.2
 Resolution:  worksforme  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--
Changes (by julien):

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


Comment:

 I tried to follow your instructions and wrote the following test case, but
 everything seems to work as expected (i.e. the saved options are
 highlighted in the M2M widget):

 Models:
 {{{
 #!python
 from django.db import models
 from django.contrib.auth.models import User

 class Place(models.Model):
 name = models.CharField(max_length=100, blank=True)
 type = models.CharField(max_length=100, choices=(('r', 'Restaurant'),
 ('s', 'Shop')), blank=True)

 def __unicode__(self):
 return self.name

 class RestaurantManager(models.Manager):
 def get_query_set(self):
 return super(RestaurantManager,
 self).get_query_set().filter(type='r')

 class ShopManager(models.Manager):
 def get_query_set(self):
 return super(ShopManager, self).get_query_set().filter(type='s')

 class Restaurant(Place):
 objects = RestaurantManager()

 class Meta:
 proxy = True

 class Shop(Place):
 objects = ShopManager()

 class Meta:
 proxy = True

 class FavoriteRestaurants(models.Model):
 user = models.ForeignKey(User)
 restaurants = models.ManyToManyField(Restaurant)
 }}}

 Admin:
 {{{
 #!python
 from django.contrib import admin

 from models import Restaurant, Shop, FavoriteRestaurants

 admin.site.register(Restaurant)
 admin.site.register(Shop)
 admin.site.register(FavoriteRestaurants)
 }}}

 If I've missed something, then please reopen this ticket and please also
 provide a detailed test case.

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

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



Re: [Django] #15642: Dead code in http.__init__.py

2011-03-21 Thread Django
#15642: Dead code in http.__init__.py
-+--
   Reporter:  jammon |Owner:  nobody
 Status:  new|Milestone:
  Component:  HTTP handling  |  Version:  SVN
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by julien):

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


Comment:

 Indeed, `django.conf.settings` is already imported at the module level on
 line 124, so those other imports and comments should be safely removable.

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

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



Re: [Django] #15386: Fix PYTHONSTARTUP support in manage.py shell

2011-03-21 Thread Django
#15386: Fix PYTHONSTARTUP support in manage.py shell
-+-
   Reporter: |Owner:  nobody
  DirkWallenstein|Milestone:
 Status:  closed |  Version:  SVN
  Component:  django-| Keywords:  management shell
  admin.py   |  startup
 Resolution:  duplicate  |Has patch:  1
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

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


Comment:

 I'm going to close this as a dupe of #6682. I advise you to look into
 `shell_plus` which I think already caters for this: https://github.com
 /django-extensions/django-
 extensions/blob/master/django_extensions/management/commands/shell_plus.py

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

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



Re: [Django] #15651: Add option to forms.FilePathField to sort choices

2011-03-21 Thread Django
#15651: Add option to forms.FilePathField to sort choices
--+--
   Reporter:  FunkyBob|Owner:  nobody
 Status:  new |Milestone:
  Component:  Forms   |  Version:  SVN
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  1   |  Needs tests:  1
Patch needs improvement:  0   |
--+--
Changes (by ramiro):

 * needs_tests:  0 => 1
 * milestone:  1.3 =>


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

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



Re: [Django] #14543: ContentTypes tests fails if auth app is not installed

2011-03-21 Thread Django
#14543: ContentTypes tests fails if auth app is not installed
-+---
   Reporter:  sayane |Owner:  crayz_train
 Status:  new|Milestone:  1.3
  Component:  Contrib apps   |  Version:  SVN
 Resolution: | Keywords:
   Triage Stage:  Ready for checkin  |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+---
Changes (by andrewgodwin):

 * owner:  dmoisset => crayz_train
 * status:  reopened => new
 * stage:  Accepted => Ready for checkin


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

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



Re: [Django] #15250: Cannot fill parent model instance in cache

2011-03-21 Thread Django
#15250: Cannot fill parent model instance in cache
-+-
   Reporter:  vzima  |Owner:  marekw2143
 Status:  assigned   |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by marekw2143):

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


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

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



Re: [Django] #15648: [Feature request] NamedTupleQuerySet

2011-03-21 Thread Django
#15648: [Feature request] NamedTupleQuerySet
-+-
   Reporter:  pbagwl |Owner:  nobody
 Status:  new|Milestone:  1.4
  Component:  Database   |  Version:  SVN
  layer (models, ORM)| Keywords:  namedtuple, tuple,
 Resolution: |  queryset
   Triage Stage: |Has patch:  1
  Unreviewed |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by pbagwl):

 Replying to [comment:2 me@…]:
 > Why not
 > {{{
 > Item.objects.all().only(*names_list)
 > }}}
 > ?

 1. repr(). values / values lists etc. are much easier to debug.
 2. deferred objects (only creates them) are not iterables

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

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



Re: [Django] #15626: Cache middleware doesnt work with pages contain google analytics script

2011-03-21 Thread Django
#15626: Cache middleware doesnt work with pages contain google analytics script
+--
   Reporter:  homeip127@…   |Owner:  nobody
 Status:  new   |Milestone:
  Component:  Cache system  |  Version:  1.2
 Resolution:| Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  1
Patch needs improvement:  0 |
+--

Comment (by anonymous):

 I think this issue is related with another ticket:
 http://code.djangoproject.com/ticket/15538

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

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