[Django] #15299: django.core.context_processors.PermWrapper should be moved to django.contrib.auth.context_processors

[Django]

#15299: django.core.context_processors.PermWrapper should be moved to
django.contrib.auth.context_processors
---+
 Reporter:  shailesh   |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 django.core.context_processors.PermWrapper specifically is meant for
 Permissions framework and doesn't really belong to django.core.

 It would be a good idea to shift it to
 django.contrib.auth.context_processors.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] #15284: CSRF/Ajax/jQuery example could break other site JS

[Django]

#15284: CSRF/Ajax/jQuery example could break other site JS
-+--
   Reporter:  LukeMaurer | Owner:  nobody
 Status:  closed | Milestone:  1.3   
  Component:  Documentation  |   Version:  1.2   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

Comment (by schinckel):

 The example code is broken: $.ajaxSend does not exist.

 I use instead:

  $(document).ajaxSetup(…)

-- 
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] #13510: Row level errors on ModelForms in the admin mess up colspans

[Django]

#13510: Row level errors on ModelForms in the admin mess up colspans
+---
   Reporter:  KyleMac   | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 In fact here the colspan should be 4, not 3 (there's an invisible cell
 containing a hidden field). The attached patch should fix this problem.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #12893: Pagination in admins changelist doesn't use queryset set by modeladmin

[Django]

#12893: Pagination in admins changelist doesn't use queryset set by modeladmin
+---
   Reporter:  Willian   | Owner:  nobody   
 Status:  new   | Milestone:   
  Component:  django.contrib.admin  |   Version:  1.2-alpha
 Resolution:|  Keywords:   
   Triage Stage:  Ready for checkin | Has patch:  1
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * stage:  Accepted => Ready for checkin


Comment:

 I confirm that everything works fine, but it doesn't hurt adding more
 regression tests so thank you mk for your patch. I've just updated it by
 explicitly using `list_per_page`, reducing the number of created objects
 (anything we can do to speed up the test suite :-) ), and writing tests
 for when the default queryset is used.

-- 
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] #15252: get_static_url in static templatetags

[Django]

#15252: get_static_url in static templatetags
--+-
   Reporter:  ohardy  | Owner:  nobody
 Status:  new | Milestone:
  Component:  django.contrib.staticfiles  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  0 
Needs documentation:  1   |   Needs tests:  1 
Patch needs improvement:  1   |  
--+-
Changes (by jezdez):

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


Comment:

 Having given this a bit more thought, I'm convinced this is a useful.
 There are a few edge cases though:

 1. The docs need to carefully explain how the storage influences the
 result of this template tag, e.g. signed URLs, increased latency with
 remote storage backends etc. It's usually also a pretty advanced topic, so
 we need to make sure this won't confuse beginners.

 2. !FileFields and !ImageFields can be passed different storage backends,
 which is why the template tag doesn't completely apply to MEDIA_URL. It
 should probably check whether it's passed a file instance or a string,
 e.g.

 {{{
 @register.simple_tag()
 def get_media_url(file_or_path):
 if isinstance(file_or_path, UploadedFile):
 return file_or_path.url
 return storage.url(file_or_path)
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #15297: SQLiteCursorWrapper Regression with SVN verson of Django 1.3

[Django]

#15297: SQLiteCursorWrapper Regression with SVN verson of Django 1.3
+---
   Reporter:  leonov| Owner:  
nobody 
 Status:  closed| Milestone:  1.3   
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:  fixed |  Keywords:  
blocker
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---

Comment (by leonov):

 Replying to [comment:2 russellm]:
 > In [15527]:
 > {{{
 > #!CommitTicketReference repository="" revision="15527"
 > Fixed #15297 -- Corrected an attribute naming regressoin from fixing
 #9964. Thanks to leonov for the report.
 > }}}

 I can confirm the fix worked (as of SVN 15528)

 Awesome fast work Russell, thanks!  -- Leon Matthews

-- 
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] #15298: Nicer error message when TemplateResponseMixin not provided with a template_name

[Django]

#15298: Nicer error message when TemplateResponseMixin not provided with a
template_name
-+--
   Reporter:  rasca  | Owner:  nobody 
 Status:  new| Milestone:  1.3
  Component:  Generic views  |   Version:  SVN
 Resolution: |  Keywords:  blocker
   Triage Stage:  Accepted   | Has patch:  0  
Needs documentation:  0  |   Needs tests:  0  
Patch needs improvement:  0  |  
-+--
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 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.

[Django] #15298: Nicer error message when TemplateResponseMixin not provided with a template_name

[Django]

#15298: Nicer error message when TemplateResponseMixin not provided with a
template_name
---+
 Reporter:  rasca  |  Owner:  nobody
   Status:  new|  Milestone:  1.3   
Component:  Generic views  |Version:  SVN   
 Keywords:  blocker|   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 When I call a view that inherits TemplateResponseMixin without a
 `template_name` defined I get

 {{{
 TemplateDoesNotExist at ´whatever url we called´
 No exception supplied
 }}}

 We could improve this by explaining the error either in
 template.response.TemplateResponse or
 views.generic.base.TemplateResponseMixin

-- 
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] #15287: Error messages in generic views are partialy translated

[Django]

#15287: Error messages in generic views are partialy translated
-+--
   Reporter:  szczav | Owner:  nobody   
  
 Status:  new| Milestone:   
  
  Component:  Generic views  |   Version:  SVN  
  
 Resolution: |  Keywords:  generic views 
http404 translation error blocker
   Triage Stage:  Accepted   | Has patch:  1
  
Needs documentation:  0  |   Needs tests:  0
  
Patch needs improvement:  1  |  
-+--

Comment (by szczav):

 In second patch I translated all error messages in generic class views
 according to russellm's suggestion. I think that it would be good to do
 some additional tests for errors, but I don't have time to do it 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.

Re: [Django] #6507: [proposal] Create extension to Python Cookie module

[Django]

#6507: [proposal] Create extension to Python Cookie module
-+--
   Reporter:  dcramer| Owner:  nobody
 Status:  closed | Milestone:
  Component:  HTTP handling  |   Version:  SVN   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Someday/Maybe  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  1 
Patch needs improvement:  0  |  
-+--
Changes (by ramiro):

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


Comment:

 The issues described in this ticket ''Description'' field and comments
 were fixed in r14707 and r15523.

-- 
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] #10190: Charset should be customizable with HttpResponse

[Django]

#10190: Charset should be customizable with HttpResponse
-+--
   Reporter:  Wonlay | Owner:  ccahoon  
 
 Status:  new| Milestone:   
 
  Component:  HTTP handling  |   Version:  SVN  
 
 Resolution: |  Keywords:  HttpResponse, 
charset, runtime
   Triage Stage:  Fixed on a branch  | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--

Comment (by ramiro):

 #13391 was closed as duplicate of this and included a patch with an
 implementation for this 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] #13391: Detect charset from Content-type header in the HttpResponse

[Django]

#13391: Detect charset from Content-type header in the HttpResponse
-+--
   Reporter:  lucky  | Owner:  nobody  
 Status:  closed | Milestone:  
  Component:  HTTP handling  |   Version:  SVN 
 Resolution:  duplicate  |  Keywords:  HttpResponse
   Triage Stage:  Accepted   | Has patch:  1   
Needs documentation:  0  |   Needs tests:  0   
Patch needs improvement:  0  |  
-+--
Changes (by ramiro):

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


Comment:

 I'm going to close this as a duplicate of #10190 and add a link to it
 there.

-- 
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] #15297: SQLiteCursorWrapper Regression with SVN verson of Django 1.3

[Django]

#15297: SQLiteCursorWrapper Regression with SVN verson of Django 1.3
+---
   Reporter:  leonov| Owner:  
nobody 
 Status:  new   | Milestone:  1.3   
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:  
blocker
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Database layer (models, ORM)
  * needs_tests:  => 0
  * keywords:  => blocker
  * needs_docs:  => 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] #15293: django.db.backends.dummy.base.DatabaseWrapper has no attribute 'rollback_unless_managed'

[Django]

#15293: django.db.backends.dummy.base.DatabaseWrapper has no attribute
'rollback_unless_managed'
+---
   Reporter:  mp| Owner:  
nobody   
 Status:  new   | Milestone:  1.3   
   
  Component:  Database layer (models, ORM)  |   Version:  SVN   
   
 Resolution:|  Keywords:  
DatabaseWrapper rollback_unless_managed dummy backend blocker
   Triage Stage:  Accepted  | Has patch:  1 
   
Needs documentation:  0 |   Needs tests:  0 
   
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * keywords:  DatabaseWrapper rollback_unless_managed dummy backend =>
   DatabaseWrapper rollback_unless_managed dummy
   backend blocker
  * 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] #15294: Use named urls instead of hard coded ones in admin views

[Django]

#15294: Use named urls instead of hard coded ones in admin views
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 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] #15296: Hi is very impossible

[Django]

#15296: Hi is very impossible
-+--
   Reporter:  Jeanphilippe| Owner:  
nobody
 Status:  closed | Milestone:   
 
  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 russellm):

  * status:  new => closed
  * needs_docs:  => 0
  * resolution:  => invalid
  * needs_tests:  => 0
  * needs_better_patch:  => 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] #15297: SQLiteCursorWrapper Regression with SVN verson of Django 1.3

[Django]

#15297: SQLiteCursorWrapper Regression with SVN verson of Django 1.3
---+
 Reporter:  leonov |  Owner:  nobody
   Status:  new|  Milestone:  1.3   
Component:  Uncategorized  |Version:  SVN   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 I've been periodically running our site against 1.3 SVN to check for
 problems, play with new features, etc...  This morning after running `svn
 update`, I ran into a regression:

 '''Summary'''

 * AttributeError while rendering: 'SQLiteCursorWrapper' object has no
 attribute 'db'
 * Problem under SVN revision 15525
 * Runs fine under Django 1.2.3
 * Runs fine under Django 1.3 beta 1
 * Full traceback:
   http://dpaste.com/413457/

 '''Details'''

 {{{
 Template error:
 In template /home/leonov/Projects/animal3/templates/layout/common.html,
 error at line 68
Caught AttributeError while rendering: 'SQLiteCursorWrapper' object has
 no attribute 'db'

 67 : {% block messagess %}
 68 :  {% for message in messages %}
 69 : {{ message }}
 70 : {% endfor %}
 71 : {% endblock messagess %}
 }}}

 (''nb. block misspelt, to rule-out name-collision problem'').

 Removing the message block completely causes the same Exception to be
 thrown, but this time in a Django Debug Toolbar template:

 {{{
 Template error:
 In template /home/leonov/Projects/animal3/env-1.3/lib/python2.6/site-
 packages/debug_toolbar/templates/debug_toolbar/base.html, error at line 49
Caught AttributeError while rendering: 'SQLiteCursorWrapper' object has
 no attribute 'db'

 40 :{% for panel in panels %}
 41 :{% if panel.has_content %}
 42 :
 43 :
 44 :{%
 trans "Close" %}
 45 :{{ panel.title|safe }}
 46 :
 47 :
 48 :
 49 : {{ panel.content|safe }}
 50 :
 51 :
 52 :
 53 :{% endif %}
 54 :{% endfor %}
 }}}

-- 
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] #15296: Hi is very impossible

[Django]

#15296: Hi is very impossible
---+
 Reporter:  Jeanphilippe|  Owner:  nobody
   Status:  new|  Milestone:
Component:  Uncategorized  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 Is very impossible instalation django on Mac do you have truk

-- 
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] #15272: Context object name is translated string

[Django]

#15272: Context object name is translated string
-+--
   Reporter:  szczav | Owner:  nobody   
 
 Status:  new| Milestone:  1.3  
 
  Component:  Generic views  |   Version:  SVN  
 
 Resolution: |  Keywords:  generic views 
context verbose_name blocker
   Triage Stage:  Ready for checkin  | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--
Changes (by adamnelson):

  * stage:  Accepted => Ready for checkin


Comment:

 All tests pass for me and the patch looks consistent.  I don't know what's
 up with the milestone though - up to somebody else.

-- 
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] #10476: Fix(?) model insert handling when autcommit=True for PostgreSQL <= 8.1

[Django]

#10476: Fix(?) model insert handling when autcommit=True for PostgreSQL <= 8.1
+---
   Reporter:  mtredinnick   | Owner:  
mtredinnick
 Status:  new   | Milestone:  1.3   
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:|  Keywords:
 
   Triage Stage:  Accepted  | Has patch:  1 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---

Comment (by adamnelson):

 Looks like this won't make it into milestone:1.3 either?

-- 
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] #15295: GeoDjango model creation fails for MySQL during tests

[Django]

#15295: GeoDjango model creation fails for MySQL during tests
+---
 Reporter:  adamnelson  |  Owner:  nobody
   Status:  new |  Milestone:
Component:  GIS |Version:  SVN   
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  
+---
 When running runtests.py:

 {{{
 Failed to install index for geoapp.Country model: (1464, "The used table
 type doesn't support SPATIAL indexes")
 Failed to install index for geoapp.City model: (1464, "The used table type
 doesn't support SPATIAL indexes")
 Failed to install index for geoapp.State model: (1464, "The used table
 type doesn't support SPATIAL indexes")
 Failed to install index for geoapp.Track model: (1464, "The used table
 type doesn't support SPATIAL indexes")
 Failed to install index for geoapp.Feature model: (1464, "The used table
 type doesn't support SPATIAL indexes")
 Failed to install index for geoapp.MinusOneSRID model: (1464, "The used
 table type doesn't support SPATIAL indexes")
 Failed to install index for relatedapp.Location model: (1464, "The used
 table type doesn't support SPATIAL indexes")
 Failed to install index for relatedapp.Parcel model: (1464, "The used
 table type doesn't support SPATIAL indexes")
 Failed to install index for layermap.County model: (1464, "The used table
 type doesn't support SPATIAL indexes")
 Failed to install index for layermap.CountyFeat model: (1464, "The used
 table type doesn't support SPATIAL indexes")
 Failed to install index for layermap.City model: (1464, "The used table
 type doesn't support SPATIAL indexes")
 Failed to install index for layermap.Interstate model: (1464, "The used
 table type doesn't support SPATIAL indexes")
 Failed to install index for layermap.CityBase model: (1464, "The used
 table type doesn't support SPATIAL indexes")
 }}}

 This is because MySQL InnoDB does not support SPATIAL indexes.  Options:

  1. create a new variable for spatial_index that is set to true if using
 the MySQL backend with InnoDB
  1. or wrap table creation around a try...except that inserts
 spatial_index=False
  1. or do one of these for GeoDjango generally (not just the 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] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
--+-
   Reporter:  ungenio | Owner:  nobody  
  
 Status:  reopened| Milestone:  
  
  Component:  Core framework  |   Version:  1.2-beta
  
 Resolution:  |  Keywords:  urlresolvers 
reverse namespace
   Triage Stage:  Accepted| Has patch:  0   
  
Needs documentation:  0   |   Needs tests:  0   
  
Patch needs improvement:  0   |  
--+-
Changes (by SmileyChris):

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


Comment:

 Perhaps you misread my example code. I didn't include anything after a
 '$'.

 And I understand how quantifiers work. The issue here is that a namespaced
 app isn't processing the regular expression question mark as expected.

 I haven't actually retested my code, but your reasoning for closing
 doesn't show that you did either so I'll reopen.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #11513: Admin Change Page Redirects to Permission Denied

[Django]

#11513: Admin Change Page Redirects to Permission Denied
+---
   Reporter:  rlaager   | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by julien):

 Good point about the hard coded urls. There are still lots of occurrences
 like this, and perhaps it's best to tackle them all at once. See #15294.

-- 
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] #15294: Use named urls instead of hard coded ones in admin views

[Django]

#15294: Use named urls instead of hard coded ones in admin views
--+-
 Reporter:  julien|  Owner:  nobody
   Status:  new   |  Milestone:
Component:  django.contrib.admin  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 There are still a lot of hard coded urls in the admin views, generally
 used for redirection. To allow for more flexibility and robustness, those
 should be replaced by named urls. Where it might get tricky is with the
 urls that are provided in the view signatures (for example
 `post_url_continue` in `response_add()`).

-- 
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] #15293: django.db.backends.dummy.base.DatabaseWrapper has no attribute 'rollback_unless_managed'

[Django]

#15293: django.db.backends.dummy.base.DatabaseWrapper has no attribute
'rollback_unless_managed'
---+
 Reporter:  mp |  
Owner:  nobody
   Status:  new|  
Milestone:  1.3   
Component:  Database layer (models, ORM)   |
Version:  SVN   
 Keywords:  DatabaseWrapper rollback_unless_managed dummy backend  |   Triage 
Stage:  Unreviewed
Has patch:  1  |  
---+
 This issue is related to #15230. Latest version from trunk breaks sites
 without a database again.

 {{{
 Index: db/backends/dummy/base.py
 ===
 --- db/backends/dummy/base.py   (revision 15525)
 +++ db/backends/dummy/base.py   (working copy)
 @@ -58,3 +58,6 @@

  def close(self):
  pass
 +
 +def rollback_unless_managed(self):
 +pass
 }}}

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

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

[Django]

#13618: prepopulated_fields crashes with get_readonly_fields
+---
   Reporter:  tonnzor   | Owner:  tobias
 Status:  assigned  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  1 |  
+---

Comment (by tonnzor):

 Replying to [comment:13 v_peter]:
 > Would you consider #11639 then instead? That one will allow the
 developer to work out the best solution for avoiding the error based on
 their exact needs.

 That patch is good for avoiding conflict of `prepopulated` and `readonly`
 and seems a fine solution. Having this conflict resolved (or making
 `prepopulated` implementation bullet-proof) would be '''great'''.

-- 
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] #12950: urlresolvers.reverse returns '/$' when including namespaced '^$' pattern at root '^$'

[Django]

#12950: urlresolvers.reverse returns '/$' when including namespaced '^$' 
pattern at
root '^$'
--+-
   Reporter:  ungenio | Owner:  nobody  
  
 Status:  closed  | Milestone:  
  
  Component:  Core framework  |   Version:  1.2-beta
  
 Resolution:  invalid |  Keywords:  urlresolvers 
reverse namespace
   Triage Stage:  Accepted| Has patch:  0   
  
Needs documentation:  0   |   Needs tests:  0   
  
Patch needs improvement:  0   |  
--+-
Changes (by v1v3kn):

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


Comment:

 @SmileyChris

 This is not really a bug, this is due to the way the '?' quantifier works.

 '?' matches the character preceding it zero or one time(s).
 Eg: the regex pattern 'cows' matches both 'cow' and 'cows'.

 And as Alex said earlier, you can't include anything after a '$'.

-- 
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] #15292: Useless piece of code in admin_list.py

[Django]

#15292: Useless piece of code in admin_list.py
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   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 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] #15291: Alignment issue in changelist

[Django]

#15291: Alignment issue in changelist
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * 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] #15290: Border style issue in changelist

[Django]

#15290: Border style issue in changelist
+---
   Reporter:  julien| Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   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 russellm):

  * needs_better_patch:  => 0
  * needs_docs:  => 0
  * needs_tests:  => 0
  * stage:  Unreviewed => 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] #15287: Error messages in generic views are partialy translated

[Django]

#15287: Error messages in generic views are partialy translated
-+--
   Reporter:  szczav | Owner:  nobody   
  
 Status:  new| Milestone:   
  
  Component:  Generic views  |   Version:  SVN  
  
 Resolution: |  Keywords:  generic views 
http404 translation error blocker
   Triage Stage:  Accepted   | Has patch:  1
  
Needs documentation:  0  |   Needs tests:  0
  
Patch needs improvement:  1  |  
-+--
Changes (by russellm):

  * keywords:  generic views http404 translation error => generic views
   http404 translation error blocker
  * needs_better_patch:  0 => 1
  * stage:  Unreviewed => Accepted


Comment:

 Accepting the issue, but I lean towards the other proposed solution --
 taking contrib.admin as an example, 404 messages should be translated.

 Also marking this as a blocker because we should get translation strings
 sorted in the initial public version.

-- 
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] #11513: Admin Change Page Redirects to Permission Denied

[Django]

#11513: Admin Change Page Redirects to Permission Denied
+---
   Reporter:  rlaager   | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by russellm):

  * stage:  Accepted => Ready for checkin


Comment:

 Looks good; my only suggested improvement would be to use named URL lookup
 instead of ../ and ../../../. However, that's easy enough to pick up on
 commit, so if you don't get around to updating the patch, I'll do it when
 I commit.

-- 
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] #14705: Model Field Order not influenced by MRO of superclasses

[Django]

#14705: Model Field Order not influenced by MRO of superclasses
--+-
   Reporter:  vanschelven | Owner:  nobody
 Status:  new | Milestone:  1.3   
  Component:  Core framework  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by russellm):

  * owner:  russellm => nobody


Comment:

 If we were talking about a critical component of Django, I might agree to
 taking a "fix the problem, then fix the fix" approach. In fact, I did just
 that with #9964 only days ago. However, I don't think this problem falls
 into that category. Django has had model inheritance for a while, and this
 is the first time this problem has been reported. It requires a complex
 model inheritance structure and a reliance on automated form ordering
 before it becomes a problem.

 I'm sorry that deferring this will be inconvenient to you, but I'd ask you
 to also consider *my* inconvenience -- the fact that landing a suboptimal
 bugfix *increases* my work as a framework maintainer in the long run,
 because at some point, I'll have to reconcile two disparate
 representations of base classes.

 Two issues of protocol:

  * Backwards compatibility isn't strictly an issue here, because _meta
 isn't stable API. There are certain aspects of _meta that I'd be very
 pained to change (like the basic field management stuff that has been that
 way since the beginning), but I don't think parents falls into that list.

  * Please don't assign bugs to other people without their permission.

-- 
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] #15292: Useless piece of code in admin_list.py

[Django]

#15292: Useless piece of code in admin_list.py
--+-
 Reporter:  julien|  Owner:  nobody
   Status:  new   |  Milestone:
Component:  django.contrib.admin  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 While I was in the neighbourhood I noticed a small useless piece of code.
 The case where `value` is `None` is already handled in
 `display_for_field()`.

-- 
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] #12475: Confusion between list_display and list_display_links for 'id' field

[Django]

#12475: Confusion between list_display and list_display_links for 'id' field
+---
   Reporter:  master| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  1.1   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 Thanks Karen and master for narrowing down the test case. In fact the
 issue is that if there is a form (i.e. `list_editable` is activated) and
 the form contains some hidden fields (in this case 'id') and those fields
 are not in `list_editable` or in `list_display_links`, then the hidden
 fields are displayed in the table cell instead of its human-readable
 value. The attached patch fixes this problem by never showing hidden
 fields in the table, since those fields are already taken care of
 separately in `` anyway.

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

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

[Django]

#15291: Alignment issue in changelist
--+-
 Reporter:  julien|  Owner:  nobody
   Status:  new   |  Milestone:
Component:  django.contrib.admin  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 This is a different issue than #15290 so I preferred to create a new
 ticket. This one is quite minor though.

 Try this example:
 {{{
 #!python
 from django.db import models

 class MyModel(models.Model):
 name = models.CharField(max_length=100, blank=True)
 title = models.CharField(max_length=100, blank=True)
 content = models.CharField(max_length=100, blank=True)
 }}}

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

 from .models import MyModel

 class MyModelAdmin(admin.ModelAdmin):
 list_display = ('name', 'title', 'content')
 actions = None
 list_display_links = ('title',)

 admin.site.register(MyModel, MyModelAdmin)
 }}}

 The content of the first column is centered and not left-aligned like all
 the other columns are. This is dictated by the CSS, presumably because
 generally the action checkbox is in the first column, and that needs to be
 centered.

 The attached patch fixes this (minor) issue, though there might be other,
 more general, approaches to this - perhaps by allowing a callable to
 provide its own classes? For example, in `ModelAdmin.action_checkbox`:

 {{{
 #!python
 def action_checkbox(self, obj):
 """
 A list_display column containing a checkbox widget.
 """
 return helpers.checkbox.render(helpers.ACTION_CHECKBOX_NAME,
 force_unicode(obj.pk))
 action_checkbox.short_description = mark_safe('')
 action_checkbox.allow_tags = True
 action_checkbox.css_classes = ['action-checkbox']
 }}}

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