[Django] #15497: BooleanField should work for ExtJS Checkboxes

[Django]

#15497: BooleanField should work for ExtJS Checkboxes
---+
 Reporter:  lsaffre|  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  SVN   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  1  |  
---+
 When using ExtJS as user interface for a Django application, one problem
 is that ExtJS Checkboxes submit a string "on" when they are checked.
 Django's `BooleanField.to_python` understands "t", "1", "true", but not
 "on". Here is a patch. I'd be glad to see this merged into Django.

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

-- 
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] #15424: readonly_fields in InlineModelAdmin looks up wrong callable

[Django]

#15424: readonly_fields in InlineModelAdmin looks up wrong callable
--+-
   Reporter:  kmike   | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.admin|   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-

Comment (by kmike):

 Callable `readonly_fields` for ModelAdmin are in django's test suite:
 
http://code.djangoproject.com/browser/django/trunk/tests/regressiontests/admin_views/models.py#L544

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

-- 
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] #15424: readonly_fields in InlineModelAdmin looks up wrong callable

[Django]

#15424: readonly_fields in InlineModelAdmin looks up wrong callable
--+-
   Reporter:  kmike   | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.admin|   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-

Comment (by kmike):

 Callable `readonly_fields` seems to work fine for ModelAdmin. The release
 notes for django 1.2 ( http://docs.djangoproject.com/en/1.2/releases/1.2
 /#readonly-fields-in-modeladmin ) say explicitly that both field values
 and calculated values can be displayed using `readonly_fields` option. So
 I think this feature is really intended to be supported and ticket
 describes a real bug, not a new feature or unfortunate wordings in the
 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-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] #15496: "Content-Transfer-Encoding: base64" not honored when uploading files

[Django]

#15496: "Content-Transfer-Encoding: base64" not honored when uploading files
+---
 Reporter:  gene@…  |  Owner:  nobody
   Status:  new |  Milestone:
Component:  HTTP handling   |Version:  1.2   
 Keywords:  base64 file upload  |   Triage Stage:  Unreviewed
Has patch:  1   |  
+---
 When the client POST-s a file in base64 encoding, Django does not decode
 the file correctly.

 == How to Repeat ==

 Upload a file to a Django view in an HTML form with method="POST" and
 enctype="multipart/form-data"; inside the MIME part for the file, encode
 the body in base64 and indicate the encoding in the Content-Transfer-
 Encoding: header.

 == Expected Result ==

 The uploaded file, when examined on disk, is decoded (by Django).

 == Actual Result ==

 The uploaded file, when examined on disk, is still base64-encoded.

 == Analysis ==

 In module {{{django.http.multipartparser}}}, {{{MultiPartParser.parse()}}}
 iterates over each part as returned by a {{{Parser}}} object.  The
 {{{Parser}}} object yields a header dictionary, which
 {{{MultiPartParser.parse()}}} captures in {{{meta_data}}}.  {{{parse()}}}
 then fetches the Content-Transfer-Encoding header from {{{meta_data}}}
 into {{{transfer_encoding}}}.

 {{{transfer_encoding}}}, as returned by {{{meta_data.get()}}}, is not
 simply a string such as {{{'base64'}}} but really a 2-tuple (value,
 params).  Also, the header value (the first element of the returned tuple)
 is not whitespace-trimmed.

 As a result, if the part contained {{{'Content-Transfer-Encoding:
 base64'}}}, {{{meta_data.get('Content-Transfer-Encoding')}}} does not
 return just {{{'base64'}}} but a 2-tuple {{{(' base64', {})}}}:

 * The header has no parameters, hence an empty parameter dictionary;
 * The value portion retains the leading space, right after the colon (:)
 in the raw header.

 {{{parse()}}} needs the whitespace-trimmed version of the first element of
 the tuple; the attached patch converts the returned tuple into the string.

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

-- 
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] #5673: [enhancement] Admin interface only sort by the first ordering field in Meta class (in models)

[Django]

#5673: [enhancement] Admin interface only sort by the first ordering field in 
Meta
class (in models)
+---
   Reporter:  DXpublica@…   | Owner:  nobody
 
 Status:  closed| Milestone:
 
  Component:  django.contrib.admin  |   Version:  SVN   
 
 Resolution:  wontfix   |  Keywords:  ordering 
Meta multiple-ordering
   Triage Stage:  Unreviewed| Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---

Comment (by samjacoby):

 Related to #4926, I think.

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

-- 
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] #14977: contrib.admin ordering by two or more fields

[Django]

#14977: contrib.admin ordering by two or more fields
+---
   Reporter:  ehc   | Owner:  nobody
  
 Status:  closed| Milestone:  1.3   
  
  Component:  django.contrib.admin  |   Version:  1.3-alpha 
  
 Resolution:  duplicate |  Keywords:  admin 
ordering order
   Triage Stage:  Unreviewed| Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  1 
  
Patch needs improvement:  0 |  
+---
Changes (by samjacoby):

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


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

-- 
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] #14977: contrib.admin ordering by two or more fields

[Django]

#14977: contrib.admin ordering by two or more fields
+---
   Reporter:  ehc   | Owner:  nobody
  
 Status:  reopened  | Milestone:  1.3   
  
  Component:  django.contrib.admin  |   Version:  1.3-alpha 
  
 Resolution:|  Keywords:  admin 
ordering order
   Triage Stage:  Unreviewed| Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  1 
  
Patch needs improvement:  0 |  
+---
Changes (by samjacoby):

  * status:  closed => reopened
  * resolution:  duplicate =>
  * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15424: readonly_fields in InlineModelAdmin looks up wrong callable

[Django]

#15424: readonly_fields in InlineModelAdmin looks up wrong callable
--+-
   Reporter:  kmike   | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.admin|   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Design decision needed  | Has patch:  0 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  0   |  
--+-
Changes (by ramiro):

  * stage:  Accepted => Design decision needed


Comment:

 I can reproduce what you describe if I also create an identical standalone
 app (but strangely enough I can't recreate the rendering of the Bar
 inlines when using test client).

 I'm pretty sure sure that although the documntation describes it as
 behavung nearly identical to the changelist view-related `'list_display'`
 option, `'readonly_fields'` doesn't support callables in
 `Modeladmin/{Stacked\Tabular}Inlines`, other two options related in the
 sense that they are relevant to the  add/change views like
 `'fieldsets.fields'` and `'fields'` don't support it either. If this is
 the case, what you are getting is behavior that seems to work partially
 but isn't really supported.

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

-- 
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] #15491: HTML syntax errors in contrib.comments templates

[Django]

#15491: HTML syntax errors in contrib.comments templates
---+
   Reporter:  jonathanslenders | Owner:  nobody
 Status:  new  | Milestone:  1.3   
  Component:  django.contrib.comments  |   Version:  SVN   
 Resolution:   |  Keywords:
   Triage Stage:  Ready for checkin| Has patch:  1 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by russellm):

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


Comment:

 A CDATA block is a better approach to fixing this, but point taken.

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

-- 
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] #15490: Some semicolons are missing in javascript code.

[Django]

#15490: Some semicolons are missing in javascript code.
+---
   Reporter:  jonathanslenders  | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by russellm):

 Thanks for the patch Jonathanl; for future reference, please generate
 diffs against the root of the source tree, so we don't have to go hunting
 to work out where the patch applies cleanly.

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

-- 
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] #15490: Some semicolons are missing in javascript code.

[Django]

#15490: Some semicolons are missing in javascript code.
+---
   Reporter:  jonathanslenders  | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #14087: django.core.management.get_commands only sees commands in the last package of a namespace package

[Django]

#14087: django.core.management.get_commands only sees commands in the last 
package
of a namespace package
--+-
   Reporter:  KyleMac | Owner:  nobody
 Status:  reopened| Milestone:
  Component:  Core framework  |   Version:  1.2   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by russellm):

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


Comment:

 When I looked at this patch 2 nights ago, I was afraid that there would be
 a problem (either with eggs, or with the namespace packaging usage), but I
 hadn't got as far as confirming the problem. Thanks to Lars for finding
 the case where it all falls apart.

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

-- 
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] #15469: CSRF/Ajax/JQuery - Token is set to be inserted on both GET and POST

[Django]

#15469: CSRF/Ajax/JQuery - Token is set to be inserted on both GET and POST
---+
   Reporter:  goran@…  | Owner:  nobody 
 
 Status:  new  | Milestone: 
 
  Component:  Contrib apps |   Version:  SVN
 
 Resolution:   |  Keywords:  
csrf,ajax,jquery
   Triage Stage:  Accepted | Has patch:  0  
 
Needs documentation:  0|   Needs tests:  0  
 
Patch needs improvement:  0|  
---+
Changes (by lukeplant):

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


Comment:

 We decided to leave this check out for simplicity, but adding it would
 probably be better, due to the overhead of cookie parsing.

 However, we would want to do `settings.type != 'GET'` instead of the
 above, for future compatibility with PUT and DELETE which will need the
 token. (Our CSRF protection doesn't handle them yet, but it should and
 hopefully will soon). I'd also like to find out whether case insensitive
 matching on the method name 'GET' might be required.

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

-- 
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] #15159: createsuperuser can't be interrupted or suspended

[Django]

#15159: createsuperuser can't be interrupted or suspended
---+
   Reporter:  slinkp   | Owner:  nobody
 Status:  closed   | Milestone:
  Component:  django-admin.py  |   Version:  1.2   
 Resolution:  wontfix  |  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+
Changes (by russellm):

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


Comment:

 Given that this is an upstream bug, and fixing it will be a non-trivial
 task, I'm going to mark this wontfix.

 Of course, if someone finds a trivial workaround, feel free to reopen and
 provide that patch.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15495: makemessages excludes all strings from Javascript after a comment (was: {{{makemessages}}} excludes all strings from Javascript after a comment)

[Django]

#15495: makemessages excludes all strings from Javascript after a comment
+---
   Reporter:  lrekucki  | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Internationalization  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by lrekucki):

  * needs_docs:  => 0
  * needs_better_patch:  => 0
  * needs_tests:  => 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-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] #15495: {{{makemessages}}} excludes all strings from Javascript after a comment

[Django]

#15495: {{{makemessages}}} excludes all strings from Javascript after a comment
--+-
 Reporter:  lrekucki  |  Owner:  nobody
   Status:  new   |  Milestone:
Component:  Internationalization  |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 A sample code (shortened as much as possible, the original comment was
 something like "get/set doesn't ...", so it's not synthetic):

 {{{
 #!js
 /* / ' */ gettext("TEXT");
 }}}

 {{{xgettext}}} doesn't find any translations after the shown comment.
 Removing either {{{/}}} or {{{'}}} fixes the problem. This is a bit
 related to #4695.

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

-- 
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] #15494: Using only('pk') in related set raises FieldDoesNotExist

[Django]

#15494: Using only('pk') in related set raises FieldDoesNotExist
+---
   Reporter:  anonymous | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---
Changes (by anonymous):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15494: Using only('pk') in related set raises FieldDoesNotExist

[Django]

#15494: Using only('pk') in related set raises FieldDoesNotExist
+---
   Reporter:  anonymous | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Database layer (models, ORM)  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Unreviewed| Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by symroe):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15494: Using only('pk') in related set raises FieldDoesNotExist

[Django]

#15494: Using only('pk') in related set raises FieldDoesNotExist
--+-
 Reporter:  anonymous |  Owner:  nobody
   Status:  new   |  Milestone:
Component:  Database layer (models, ORM)  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 This is my first ticket, apologies if this is known or I've missed
 something in my report.

 With model A and model B, where model B has a fk to A:

 >>> A().b_set.all().only('pk')

 Raises "FieldDoesNotExist: B has no field named 'pk'"

 In my example I'm instantiating a new object for brevity.  The behaviour
 is the same with a saved object.

 I've attached a simple patch, however I couldn't get the testrunner
 working, so I couldn't write a full patch.  Also, I expect this isn't the
 best method, but I don't know enough about the ORM to know of a better
 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.

[Django] #15493: extras/csrf_migration_helper.py parsing improvement

[Django]

#15493: extras/csrf_migration_helper.py parsing improvement
---+
 Reporter:  john   |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  1.2   
 Keywords:  CSRF   |   Triage Stage:  Unreviewed
Has patch:  1  |  
---+
 The extras/csrf_migration_helper.py script requires that the {% csrf_token
 %} template tag appear on the same line as the opening  tag.

 This patch reworks the parsing to find the token anywhere within the form.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #9318: "Virtual" behaviour for signal dispatcher and model inheritance

[Django]

#9318: "Virtual" behaviour for signal dispatcher and model inheritance
--+-
   Reporter:  svetlyak40wt| Owner:  jdunck  
 
 Status:  assigned| Milestone:  1.3 
 
  Component:  Core framework  |   Version:  1.0 
 
 Resolution:  |  Keywords:  model inheritance, 
signals, dispatch, proxy, subclass
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-
Changes (by jdunck):

  * 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] #9318: "Virtual" behaviour for signal dispatcher and model inheritance

[Django]

#9318: "Virtual" behaviour for signal dispatcher and model inheritance
--+-
   Reporter:  svetlyak40wt| Owner:  jdunck  
 
 Status:  new | Milestone:  1.3 
 
  Component:  Core framework  |   Version:  1.0 
 
 Resolution:  |  Keywords:  model inheritance, 
signals, dispatch, proxy, subclass
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-
Changes (by jdunck):

  * owner:  nobody => jdunck


Comment:

 I was somehow unaware of this problem but just tripped across it.  Will
 try to sprint on at PyCon.

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

-- 
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] #15492: Explain all error message keys for the SplitDateTimeField

[Django]

#15492: Explain all error message keys for the SplitDateTimeField
---+
 Reporter:  lode   |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Documentation  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 According to
 http://docs.djangoproject.com/en/dev/ref/forms/fields/#splitdatetimefield
 the SplitDateTimeField has the error message keys 'required' and
 'invalid'.

 Wanting to change the error message for an invalid time failed until I
 discovered (via this fix http://www.mail-archive.com/django-
 upda...@googlegroups.com/msg35926.html) that there are also error message
 keys 'invalid_time' and 'invalid_date'.

 It would be nice if these were added to the documentation.

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

-- 
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] #15159: createsuperuser can't be interrupted or suspended

[Django]

#15159: createsuperuser can't be interrupted or suspended
---+
   Reporter:  slinkp   | Owner:  nobody
 Status:  new  | Milestone:
  Component:  django-admin.py  |   Version:  1.2   
 Resolution:   |  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+

Comment (by mmcnickle):

 There is a very recent upstream bug report for this:
 http://bugs.python.org/issue11236

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

-- 
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] #15159: createsuperuser can't be interrupted or suspended

[Django]

#15159: createsuperuser can't be interrupted or suspended
---+
   Reporter:  slinkp   | Owner:  nobody
 Status:  new  | Milestone:
  Component:  django-admin.py  |   Version:  1.2   
 Resolution:   |  Keywords:
   Triage Stage:  Accepted | Has patch:  0 
Needs documentation:  0|   Needs tests:  0 
Patch needs improvement:  0|  
---+

Comment (by mmcnickle):

 If it's a bug, it's an upstream python bug. The python UNIX implementation
 of getpass() seems to actively suppress SIGINTs
 
http://svn.python.org/view/python/trunk/Lib/getpass.py?revision=76000&view=markup#l65
 though the windows implementation seems to allow it
 
http://svn.python.org/view/python/trunk/Lib/getpass.py?revision=76000&view=markup#l101

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

-- 
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] #15491: HTML syntax errors in contrib.comments templates

[Django]

#15491: HTML syntax errors in contrib.comments templates
-+--
 Reporter:  jonathanslenders |  Owner:  nobody
   Status:  new  |  Milestone:  1.3   
Component:  django.contrib.comments  |Version:  SVN   
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  1|  
-+--
  should be terminated by a slash. (XHTML doctype.)

  should be placed around CSS when the CSS contains a less-than,
 greater-than or ampersand. (contains greater-than sign.)

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

-- 
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] #15040: Boolean fields return 0 and 1 when loaded through select_related

[Django]

#15040: Boolean fields return 0 and 1 when loaded through select_related
+---
   Reporter:  homm  | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  Database layer (models, ORM)  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by adamnelson):

 Change at #15169 may be related and address this

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

-- 
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] #15490: Some semicolons are missing in javascript code.

[Django]

#15490: Some semicolons are missing in javascript code.
--+-
 Reporter:  jonathanslenders  |  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  django.contrib.admin  |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 Several semicolons are missing in javascript code. (Statements need to be
 terminated by semicolons, even if browsers do not always require it.)

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

-- 
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] #14087: django.core.management.get_commands only sees commands in the last package of a namespace package

[Django]

#14087: django.core.management.get_commands only sees commands in the last 
package
of a namespace package
-+--
   Reporter:  KyleMac| Owner:  nobody
 Status:  reopened   | Milestone:
  Component:  Core framework |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by lnielsen@…):

 * cc: lnielsen@… (added)


Comment:

 Hi,

 I've tested out the namespaced_managment_commands.diff patch and it works
 for me when my namespace packages are installed in develop mode or as eggs
 (with either easy_install or a python setup.py install), however if
 install the package with pip then pip automatically removes the
 namespacepackage/__init__.py file and above method no longer works.

 Cheers,
 Lars

 Output from installing my package:


 {{{
 (virtualenv) $ pip install .
 Unpacking .../
   Running setup.py egg_info for package from file:///.../

 no previously-included directories found matching 'docs/build'
 warning: no files found matching '*.css' under directory 'src'
 warning: no files found matching '*.js' under directory 'src'
 Installing collected packages: 
   Running setup.py install for 

 no previously-included directories found matching 'docs/build'
 warning: no files found matching '*.css' under directory 'src'
 warning: no files found matching '*.js' under directory 'src'
 Skipping installation of ../virtualenv/lib/python2.7/site-
 packages//__init__.py (namespace package)   <---
 Installing ...virtualenv/lib/python2.7/site-
 packages/-0.1.0-py2.7-nspkg.pth
 Successfully installed 
 Cleaning up...
 }}}

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

-- 
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] #15489: add class attributes to checkboxes and radio buttons

[Django]

#15489: add class attributes to checkboxes and radio buttons
--+-
 Reporter:  wildfire@…|  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  Uncategorized |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 Hi,

 Attached is a short patch to add two class attributes to both checkboxes
 and radio buttons.

 We have found this necessary as CSS targetting does not work on some
 browsers (specifically IE).

 Regards,
 Anand

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

-- 
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] #15394: Confused comment for STATICFILES_DIR on settings.py

[Django]

#15394: Confused comment for STATICFILES_DIR on settings.py
-+--
   Reporter:  carlopires | Owner:  nobody
 Status:  closed | Milestone:
  Component:  Uncategorized  |   Version:  SVN   
 Resolution:  invalid|  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by carlopires):

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


Comment:

 Now I got it, each projects' app can have a static/ subdir which will be
 considered by staticfiles finder. Additional static files can be included
 in STATICFILES_DIR.

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

-- 
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] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
---+
   Reporter:  trigeek38| Owner:  anonymous  
 
 Status:  closed   | Milestone:  1.2
 
  Component:  Template system  |   Version:  SVN
 
 Resolution:  fixed|  Keywords:  
TemplateDoesNotExist
   Triage Stage:  Unreviewed   | Has patch:  1  
 
Needs documentation:  0|   Needs tests:  1  
 
Patch needs improvement:  1|  
---+
Changes (by kmtracey):

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


Comment:

 The problem identified in this ticket was fixed, really. The fix includes
 tests, which failed before the code change and are still passing on
 current trunk:

 {{{
 ~/django/trunk/tests
 --> ./runtests.py --settings=testdb.sqlite -v2
 templates.Templates.test_extends_include_missing_baseloader
 templates.Templates.test_extends_include_missing_cachedloader
 Importing application templates
 Creating test database for alias 'default' (':memory:')...
 Creating tables ...
 Creating table django_content_type
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table auth_message
 Creating table django_site
 Creating table django_flatpage_sites
 Creating table django_flatpage
 Creating table django_redirect
 Creating table django_session
 Creating table django_comments
 Creating table django_comment_flags
 Creating table django_admin_log
 Installing custom SQL ...
 Installing indexes ...
 No fixtures found.
 Creating test database for alias 'other' ('other_db')...
 Destroying old test database 'other'...
 Creating tables ...
 Creating table django_content_type
 Creating table auth_permission
 Creating table auth_group_permissions
 Creating table auth_group
 Creating table auth_user_user_permissions
 Creating table auth_user_groups
 Creating table auth_user
 Creating table auth_message
 Creating table django_site
 Creating table django_flatpage_sites
 Creating table django_flatpage
 Creating table django_redirect
 Creating table django_session
 Creating table django_comments
 Creating table django_comment_flags
 Creating table django_admin_log
 Installing custom SQL ...
 Installing indexes ...
 No fixtures found.
 test_extends_include_missing_baseloader
 (regressiontests.templates.tests.Templates) ... ok
 test_extends_include_missing_cachedloader
 (regressiontests.templates.tests.Templates) ... ok

 --
 Ran 2 tests in 0.004s

 OK
 Destroying test database for alias 'default' (':memory:')...
 Destroying test database for alias 'other' ('other_db')...
 }}}

 Further, if you doubt the tests, if I change one of my current projects to
 have the problem noted in the original description -- one existing
 template including a 2nd existing template that in turn attempts to
 include a 3rd template that does not exist, the debug page I get correctly
 identifies the template that is missing.

 You may be seeing a bug, but it is not this exact bug. Better than trying
 to show how the code change made here is wrong would be a test case that
 shows the case you are running into where a problem exists. And that
 should go into its own new ticket (that perhaps references this one),
 because this specific one is fixed.

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

-- 
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] #15394: Confused comment for STATICFILES_DIR on settings.py

[Django]

#15394: Confused comment for STATICFILES_DIR on settings.py
-+--
   Reporter:  carlopires | Owner:  nobody
 Status:  reopened   | Milestone:
  Component:  Uncategorized  |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by carlopires):

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


Comment:

 So I'm missing something here. Where would be my app static files if I
 dont put anything in STATICFILES_DIR ?

 Using django version 1.3 beta 1 SVN-15634, and following
 http://docs.djangoproject.com/en/dev/howto/static-files/, my static files
 on
 SITE_ROOT/static dir are not served when using runserver and adding
 staticfiles_urlpatterns to URLconf.

 I had to put SITE_ROOT/static on STATICFILES_DIR to make
 staticfiles_urlpatterns to find 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-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] #15488: Behaviour natural keys differ between json and xml serializers

[Django]

#15488: Behaviour natural keys differ between json and xml serializers
--+-
   Reporter:  sueastside@…| Owner:  nobody  
 
 Status:  closed  | Milestone:  
 
  Component:  Serialization   |   Version:  SVN 
 
 Resolution:  invalid |  Keywords:  
serialization, natural key, xml, json
   Triage Stage:  Unreviewed  | Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-
Changes (by kmtracey):

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


Comment:

 natural_key should always return a tuple, this is documented:
 http://docs.djangoproject.com/en/1.2/topics/serialization/#serialization-
 of-natural-keys

 The bug here is that the model's natural_key method is not returning the
 proper type. The fix is to fix that, not add quiet "fixing up" of the
 value into Djano.

 (What's annoying about the json produced when natural_key returns the
 right type?)

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

-- 
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] #15361: QuerySet.get() should use LIMIT 2

[Django]

#15361: QuerySet.get() should use LIMIT 2
+---
   Reporter:  mbertheau | Owner:  
mmcnickle 
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  
QuerySet get limit MultipleObjectsReturned
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by mmcnickle):

  * owner:  nobody => mmcnickle


Comment:

 The concern that this change may make the get() slower may be valid, but
 one thing is for sure, that benchmark is inadequate for anything but huge
 performance regressions. I'm able to produce "Significant" slower results
 by running 2 identical versions of django:


 {{{
 Running all benchmarks
 Control: Django 1.3 beta 1 (in django-control)
 Experiment: Django 1.3 beta 1 (in django-experiment)

 Running 'query_get' benchmark ...
 Min: 0.02 -> 0.02: no change
 Avg: 0.022400 -> 0.024800: 1.1071x slower
 Significant (t=-2.556039)
 Stddev: 0.00431 -> 0.00505: 1.1698x larger (N = 50)
 }}}

 The telling fact is that these "significant" results are transient,
 differing from run to run.

 I'll write a benchmark that will properly stress the query.get() and see
 if:

 a) There is a performance regression for pk (or other fields with unique
 constraints) lookups[[BR]]
 b) There is a performance increase for non-indexed, large match lookups.

 If (b) and not (a), it's a +1.[[BR]]
 If (a) and (b), it's probably a -1, given the more usual case in (a)[[BR]]
 If (a) and not (b), -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.

[Django] #15486: yodICpvWVoGmoocOhnd

[Django]

#15486: yodICpvWVoGmoocOhnd
---+
 Reporter:  yqoralnzl  |  Owner:  WDXTxwStJyQMaD
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  sLYXGHxh   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 dBt3Jy  http://vnvwnpvdcgid.com/";>vnvwnpvdcgid,
 [url=http://hbxaukurahlz.com/]hbxaukurahlz[/url],
 [link=http://knydjhukybnz.com/]knydjhukybnz[/link],
 http://ijihlgbsajfr.com/

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

-- 
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] #15488: Behaviour natural keys differ between json and xml serializers

[Django]

#15488: Behaviour natural keys differ between json and xml serializers
---+
 Reporter:  sueastside@…   |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Serialization  |Version:  SVN   
 Keywords:  serialization, natural key, xml, json  |   Triage Stage:  Unreviewed
Has patch:  1  |  
---+
 Behaviour natural keys differ between json and xml serializers

 Using a single value for the natural key.

 Consider the following code:
 {{{
 #!div style="font-size: 80%"
 Code highlighting:
   {{{#!python
   class A(models.Model):
 name = models.CharField(unique=True)
 def natural_key(self):
   return self.name

   class B(models.Model):
 a = models.ForeignKey(A)
   }}}
 }}}

 Which results in some nice json:
 {{{
 "pk": 1,
 "model": "models.b",
 "fields": {
   "a": "hello"
  }
 }}}

 but goes wrong in XML:
 {{{
   
 
   h
   e
   l
   l
   o
 
   
 }}}


 Ofcourse a tuple can be returned from natural_key(), but that results in:
 {{{
 "pk": 1,
 "model": "models.b",
 "fields": {
   "a": ["hello"]
  }
 }}}

 Which is kind of annoying.

 Attached is a small patch draft.


 Thank you for your time.

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

-- 
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] #15487: yodICpvWVoGmoocOhnd

[Django]

#15487: yodICpvWVoGmoocOhnd
---+
 Reporter:  yqoralnzl  |  Owner:  WDXTxwStJyQMaD
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  sLYXGHxh   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 dBt3Jy  http://vnvwnpvdcgid.com/";>vnvwnpvdcgid,
 [url=http://hbxaukurahlz.com/]hbxaukurahlz[/url],
 [link=http://knydjhukybnz.com/]knydjhukybnz[/link],
 http://ijihlgbsajfr.com/

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

-- 
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] #15485: yodICpvWVoGmoocOhnd

[Django]

#15485: yodICpvWVoGmoocOhnd
---+
 Reporter:  yqoralnzl  |  Owner:  WDXTxwStJyQMaD
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  sLYXGHxh   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 dBt3Jy  http://vnvwnpvdcgid.com/";>vnvwnpvdcgid,
 [url=http://hbxaukurahlz.com/]hbxaukurahlz[/url],
 [link=http://knydjhukybnz.com/]knydjhukybnz[/link],
 http://ijihlgbsajfr.com/

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

-- 
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] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
---+
   Reporter:  trigeek38| Owner:  anonymous  
 
 Status:  reopened | Milestone:  1.2
 
  Component:  Template system  |   Version:  SVN
 
 Resolution:   |  Keywords:  
TemplateDoesNotExist
   Triage Stage:  Unreviewed   | Has patch:  1  
 
Needs documentation:  0|   Needs tests:  1  
 
Patch needs improvement:  1|  
---+
Changes (by liorsion):

 * cc: liorsion (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] #12787: TemplateDoesNotExist exception does not report the correct template_name

[Django]

#12787: TemplateDoesNotExist exception does not report the correct template_name
---+
   Reporter:  trigeek38| Owner:  anonymous  
 
 Status:  reopened | Milestone:  1.2
 
  Component:  Template system  |   Version:  SVN
 
 Resolution:   |  Keywords:  
TemplateDoesNotExist
   Triage Stage:  Unreviewed   | Has patch:  1  
 
Needs documentation:  0|   Needs tests:  1  
 
Patch needs improvement:  1|  
---+
Changes (by liorsion):

  * status:  closed => reopened
  * needs_better_patch:  0 => 1
  * resolution:  fixed =>
  * stage:  Accepted => Unreviewed


Comment:

 This fix doesn't work - the original problem remains.

 The original exception (found in loader.py, also in changeset:12792):

 {{{
 raise TemplateDoesNotExist(name)
 }}}

 that's the correct line of code, however, at the same file (and same
 changeset:12792):

 {{{
 except TemplateDoesNotExist:
 # If compiling the template we found raises
 TemplateDoesNotExist, back off to
 # returning the source and display name for the template we
 were asked to load.
 # This allows for correct identification (later) of the actual
 template that does
 # not exist.
 return source, display_name
 }}}

 the exception is caught but value is not used, and so we "loose" the
 exception. However, since we try to render it again, it's thrown again at
 the same place. This time, it's caught, but there's an error there:

 the original call look like this:

 {{{
 def select_template(template_name_list):
 "Given a list of template names, returns the first that can be
 loaded."
 for template_name in template_name_list:
 try:
 return get_template(template_name)
 except TemplateDoesNotExist:
 continue
 # If we get here, none of the templates could be loaded
 raise TemplateDoesNotExist(', '.join(template_name_list))
 }}}

 and so the exception caught there is not because the original template was
 not found, but because templateB was not found, but it's never recorded
 and identified.

 A possible solution:

 {{{

 def select_template(template_name_list):
 "Given a list of template names, returns the first that can be
 loaded."
 error_list = []
 for template_name in template_name_list:
 try:
 return get_template(template_name)
 except TemplateDoesNotExist, e:
 if e.message not in template_name_list:
 error_list.append(e.message)
 continue
 # If we get here, none of the templates could be loaded
 template_name_list += error_list
 raise TemplateDoesNotExist(', '.join(template_name_list))
 }}}

 we need to make sure the reason for the TemplateDoesNotExist exception is
 not "just" looking for TemplateA in a wrong directory (the external loop).

 A different approach would be to create SubTemplateDoesNotExist exception
 type.

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

-- 
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] #3148: Add getters and setters to model fields

[Django]

#3148: Add getters and setters to model fields
+---
   Reporter:  jerf@…| Owner: 
 Status:  new   | Milestone: 
  Component:  Database layer (models, ORM)  |   Version:  SVN
 Resolution:|  Keywords: 
   Triage Stage:  Accepted  | Has patch:  1  
Needs documentation:  1 |   Needs tests:  0  
Patch needs improvement:  1 |  
+---
Changes (by EnTeQuAk):

 * cc: EnTeQuAk (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.

[Django] #15483: hhxMFkHZsbSjLcpybc

[Django]

#15483: hhxMFkHZsbSjLcpybc
---+
 Reporter:  nbieuqfkh  |  Owner:  qIMOpaHn  
   Status:  new|  Milestone:  1.4   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  MxXoofVnYEx|   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 F7oesg  http://djiytnsiubls.com/";>djiytnsiubls,
 [url=http://ydauoloedyhw.com/]ydauoloedyhw[/url],
 [link=http://elpenayntvzs.com/]elpenayntvzs[/link],
 http://sgfqpmuypqcp.com/

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

-- 
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] #15484: hhxMFkHZsbSjLcpybc

[Django]

#15484: hhxMFkHZsbSjLcpybc
---+
 Reporter:  nbieuqfkh  |  Owner:  qIMOpaHn  
   Status:  new|  Milestone:  1.4   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  MxXoofVnYEx|   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 F7oesg  http://djiytnsiubls.com/";>djiytnsiubls,
 [url=http://ydauoloedyhw.com/]ydauoloedyhw[/url],
 [link=http://elpenayntvzs.com/]elpenayntvzs[/link],
 http://sgfqpmuypqcp.com/

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

-- 
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] #15482: hhxMFkHZsbSjLcpybc

[Django]

#15482: hhxMFkHZsbSjLcpybc
---+
 Reporter:  nbieuqfkh  |  Owner:  qIMOpaHn  
   Status:  new|  Milestone:  1.4   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  MxXoofVnYEx|   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 F7oesg  http://djiytnsiubls.com/";>djiytnsiubls,
 [url=http://ydauoloedyhw.com/]ydauoloedyhw[/url],
 [link=http://elpenayntvzs.com/]elpenayntvzs[/link],
 http://sgfqpmuypqcp.com/

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

-- 
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] #15481: yUoXyHHelRBkOdtuLT

[Django]

#15481: yUoXyHHelRBkOdtuLT
---+
 Reporter:  zlmslmxyvz |  Owner:  dELsqhuYcNmreS
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  aYFQmHfl   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 ZnoNRG  http://fohbcyxzdovc.com/";>fohbcyxzdovc,
 [url=http://yekcsedstgrh.com/]yekcsedstgrh[/url],
 [link=http://njnqykjnnnxn.com/]njnqykjnnnxn[/link],
 http://lutncagjaszv.com/

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

-- 
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] #15480: yUoXyHHelRBkOdtuLT

[Django]

#15480: yUoXyHHelRBkOdtuLT
---+
 Reporter:  zlmslmxyvz |  Owner:  dELsqhuYcNmreS
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  aYFQmHfl   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 ZnoNRG  http://fohbcyxzdovc.com/";>fohbcyxzdovc,
 [url=http://yekcsedstgrh.com/]yekcsedstgrh[/url],
 [link=http://njnqykjnnnxn.com/]njnqykjnnnxn[/link],
 http://lutncagjaszv.com/

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

-- 
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] #15479: yUoXyHHelRBkOdtuLT

[Django]

#15479: yUoXyHHelRBkOdtuLT
---+
 Reporter:  zlmslmxyvz |  Owner:  dELsqhuYcNmreS
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  aYFQmHfl   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 ZnoNRG  http://fohbcyxzdovc.com/";>fohbcyxzdovc,
 [url=http://yekcsedstgrh.com/]yekcsedstgrh[/url],
 [link=http://njnqykjnnnxn.com/]njnqykjnnnxn[/link],
 http://lutncagjaszv.com/

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

-- 
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] #3566: Proposal: ORM aggregation support

[Django]

#3566: Proposal: ORM aggregation support
-+--
   Reporter:  Honza Král   | Owner:  
russellm
 Status:  closed | Milestone:  
1.4 
  Component:  Database layer (models, ORM)   |   Version:  
SVN 
 Resolution:  fixed  |  Keywords:  
orm aggregation group by
   Triage Stage:  Someday/Maybe  | Has patch:  
1   
Needs documentation:  0  |   Needs tests:  
0   
Patch needs improvement:  0  |  
-+--
Changes (by ogzgqtgjqgm):

  * milestone:  => 1.4


Comment:

 jagqyQ  http://kieverobhvpt.com/";>kieverobhvpt,
 [url=http://ipmsghmcjwwe.com/]ipmsghmcjwwe[/url],
 [link=http://gjowxjjsnyoy.com/]gjowxjjsnyoy[/link],
 http://raoupchrpjci.com/

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

-- 
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] #15361: QuerySet.get() should use LIMIT 2

[Django]

#15361: QuerySet.get() should use LIMIT 2
+---
   Reporter:  mbertheau | Owner:  
nobody
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  
QuerySet get limit MultipleObjectsReturned
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---

Comment (by mbertheau):

 I concur. It was indeed in the context of a database design flaw that I
 noticed the unneeded row number counting of `get()`.

 However, I don't believe that the negative effects of this patch are so
 significant that it's worth sacrificing its positive effects, regardless
 of their low likelihood of occurring in well designed databases.

 lukeplant, do the results of the other benchmark tests differ
 significantly?

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

-- 
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] #15361: QuerySet.get() should use LIMIT 2

[Django]

#15361: QuerySet.get() should use LIMIT 2
+---
   Reporter:  mbertheau | Owner:  
nobody
 Status:  new   | Milestone:

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

 Resolution:|  Keywords:  
QuerySet get limit MultipleObjectsReturned
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---

Comment (by Alex):

 I'm not sure it does, the majority of `get()` calls (in my experience) are
 on fields such as `pk` or `slug`, which have database level uniqueness
 constraints, and thus the database has no need to be told that there is a
 limit on the number of results.  Indeed the only case where this should
 make a large difference is if you're doing a `get()` from which the
 database will return a large number of results and then become a
 `MultipleObjectsReturned` exception, a case which I contend is unlikely.

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

-- 
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] #15478: DBHWzRUcYfDGViAFIa

[Django]

#15478: DBHWzRUcYfDGViAFIa
---+
 Reporter:  cokotxmeynk|  Owner:  aMbKlFTnyqrSsn
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  1.2   
 Keywords:  btYnfAbnlYeB   |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 NZZZhL  http://jleovakkjjpx.com/";>jleovakkjjpx,
 [url=http://ezloxckcfdom.com/]ezloxckcfdom[/url],
 [link=http://argiexfvculr.com/]argiexfvculr[/link],
 http://rdfqhpktorbi.com/

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

-- 
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] #15475: mstYwBeZDgRwExnwUPL

[Django]

#15475: mstYwBeZDgRwExnwUPL
-+--
   Reporter:  yslbkkgxrj | Owner:  bzJbWFbDaPyrkj
 Status:  closed | Milestone:  1.3   
  Component:  Uncategorized  |   Version:  1.2   
 Resolution:  invalid|  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by PaulM):

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


Comment:

 spam.

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

-- 
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] #15477: mstYwBeZDgRwExnwUPL

[Django]

#15477: mstYwBeZDgRwExnwUPL
-+--
   Reporter:  yslbkkgxrj | Owner:  bzJbWFbDaPyrkj
 Status:  closed | Milestone:  1.3   
  Component:  Uncategorized  |   Version:  1.2   
 Resolution:  invalid|  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by PaulM):

  * keywords:  AnYoSCShOeap =>


Comment:

 removing the spammy keyword too.

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

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