Re: [Django] #2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql)

[Django]

#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in
mysql)
---+
  Reporter:  scan...@nominum.com   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Database layer (models, ORM)  |   Version:
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by bronger):

 * cc: bron...@physik.rwth-aachen.de (added)

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

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

Re: [Django] #9170: Write real documentation for custom management commands

[Django]

#9170: Write real documentation for custom management commands
+---
  Reporter:  ubernostrum| Owner:  davidfischer
Status:  assigned   | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by davidfischer):

 * cc: djfis...@gmail.com (added)
  * owner:  nobody => davidfischer
  * has_patch:  0 => 1
  * version:  1.0 => SVN
  * 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11684: dismissAddAnotherPopup fails with XHTML

[Django]

#11684: dismissAddAnotherPopup fails with XHTML
---+
  Reporter:  rlaa...@wiktel.com| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 This is part of the larger issue of dealing with varying output formats,
 and so is probably best dealt with in a general fashion by a future
 release, rather than piecemeal in 1.2.

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

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

Re: [Django] #11683: response_add assumes DEFAULT_CONTENT_TYPE is text/html for dismissAddAnotherPopup

[Django]

#11683: response_add assumes DEFAULT_CONTENT_TYPE is text/html for
dismissAddAnotherPopup
---+
  Reporter:  rlaa...@wiktel.com| Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 This is part of the larger issue of dealing with varying output formats,
 and so is probably best dealt with in a general fashion by a future
 release, rather than piecemeal in 1.2.

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

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

Re: [Django] #9847: hardcoded string in core/handlers/base.py

[Django]

#9847: hardcoded string in core/handlers/base.py
-+--
  Reporter:  drakkan | Owner: 
Status:  new | Milestone:  1.3
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 Also, this is a minor enough issue that it really ought to happen on 1.3
 or a 1.2.X bugfix release.

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

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

Re: [Django] #12725: Combining Q objects with | is inefficient; lots of deep cloning

[Django]

#12725: Combining Q objects with | is inefficient; lots of deep cloning
---+
  Reporter:  jbalogh   | Owner:  nobody   
Status:  new   | Milestone:  1.3  
 Component:  Database layer (models, ORM)  |   Version:  1.2-alpha
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  1 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 Since this isn't an actual bug but rather a possible optimization (and
 since we can't seem to agree on exactly how to apply it), I'm punting it
 from 1.2.

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

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

Re: [Django] #12280: working with forms example should include editing an existing instance

[Django]

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

  * milestone:  1.2 =>

Comment:

 Punting from 1.2; we can always add this later when there's 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12224: psycopg2 raises "can't adapt" when use gettext extensions on model meta permissions field.

[Django]

#12224: psycopg2 raises "can't adapt" when use gettext extensions on model meta
permissions field.
---+
  Reporter:  chronos   | Owner:  chronos

Status:  closed| Milestone: 

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

Resolution:  duplicate |  Keywords:  psycopg2, 
permissions, i18n, gettext, "can't adapt", syncdb
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  1  

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

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

Comment:

 This is a specific case of trying to have a field value stored in the
 database and marked for translation, which has been debated and, for the
 moment, wontfix'd. See #9601 for pointers to discussion.

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

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

Re: [Django] #12056: update to Apache/mod_wsgi documentation

[Django]

#12056: update to Apache/mod_wsgi documentation
-+--
  Reporter:  mgbelisle   | Owner:  nobody   
  
Status:  new | Milestone:   
  
 Component:  Documentation   |   Version:  1.1  
  
Resolution:  |  Keywords:  mod_wsgi, 
setup_environ
 Stage:  Design decision needed  | Has_patch:  0
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 The current recommendation is one that's known to work and consists of the
 minimum amount of configuration necessary to make Django work in the
 common case, so that's what should be in the documentation. And the
 refactoring suggested by Graham would be out of scope for 1.2 at this
 point, so this ticket doesn't belong on the milestone.

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

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

Re: [Django] #12068: The {% url %} parser can fail with StopIteration

[Django]

#12068: The {% url %} parser can fail with StopIteration
-+--
  Reporter:  emulbreh| Owner:  smoluf 
Status:  new | Milestone:  1.3
 Component:  Template system |   Version:  1.1
Resolution:  |  Keywords:  url tag
 Stage:  Design decision needed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 This is enough of an edge case that I'm comfortable punting it from 1.2.

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

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

Re: [Django] #11155: Buffer size in get_image_dimensions too small

[Django]

#11155: Buffer size in get_image_dimensions too small
-+--
  Reporter:  seph| Owner:  nobody   
   
Status:  closed  | Milestone:  1.2  
   
 Component:  File uploads/storage|   Version:  SVN  
   
Resolution:  duplicate   |  Keywords:  ImageField, 
get_image_dimensions, buffer
 Stage:  Design decision needed  | Has_patch:  1
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

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

Comment:

 This certainly looks like a duplicate of #11158; closing in favor of that
 ticket since it has a more recent 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12962: Broken Admin Delete Action With Confirmation

[Django]

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

 @blinkylights

 does this patch cause this error? or was the error already there before
 the patch is applied?

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

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

Re: [Django] #6362: Remove blank spaces with strip when validating the data

[Django]

#6362: Remove blank spaces with strip when validating the data
-+--
  Reporter:  marinho | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  |  Keywords:  blank space strip
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by net147):

 * cc: net...@gmail.com (added)

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

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

[Django] #13023: Don't show "+ Add another " in admin inlines

[Django]

#13023: Don't show "+ Add another " in admin inlines
--+-
 Reporter:  rasca |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Up to 1.1 when dealing with inlines in the admin one could set extra=0 to
 prevent a user to add a new related model.
 With the new dynamic inlines, this can't be prevented.

 I'm not sure if this is a Bug or not, but certainly we've lost a
 functionality we had in 1.1, and the code works differently

 The 'extra' doc says:
 "This controls the number of extra forms the formset will display in
 addition to the initial forms."
 and
 "Extra forms for inlines will be hidden and replaced with a link to
 dynamically add any number of new inlines for users with Javascript
 enabled."
 It isn't clear if extra refers to the amount of extra inlines in the
 initial display or the extra amount of dynamic additions permitted.

 I can think of 2 alternatives, changing the behavior of "+ Add another"
 when extra = 0 (will allow the user the same functionality as when
 javascript disabled), or allowing a extra = None.
 I support the first alternative, so we don't to have to change our code,
 and it maintains the same usability with or without js.

 Use case:
 I have models A and B. Model B has a fk to model A, and it's shown as
 inline in the A's change_form.
 Model B is too complex to be created in an inline (or has inline's
 itself).
 For usability's sake I often show B as inlines in A, so the user can see
 the list of B while editing A and allow them to delete a certain B from A
 (I only show a few readonly fields of B).
 Another use is to allow easy drag and drop ordering for a set of B.

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

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

Re: [Django] #12960: return value (cleaned_data) from clean() method is ignored

[Django]

#12960: return value (cleaned_data) from clean() method is ignored
---+
  Reporter:  krejcik   | Owner:  jkocherhans
Status:  assigned  | Milestone:  1.2
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Changes (by jkocherhans):

  * status:  new => assigned

Comment:

 Replying to [comment:6 patrys]:
 > I think self.instance existing at the point when `clean()` is called is
 an implementation detail and is not guaranteed by the API documentation.
 Modifying the instance directly inside `clean()` should be discouraged.

 I don't think we can discourage modifying the instance inside
 `Model.clean()`, but for `ModelForm.clean()` you're absolutely right. I
 think my latest patch hits the mark. Instance creation is postponed until
 after the form validation has completed, then the model validation is run,
 then unique_validation is run as long as `ModelForm.clean()` wasn't
 overridden without calling super.

 Short version:

  * clean form fields
  * run `form.clean()`
  * create or update `form.instance` with `form.cleaned_data`
  * clean model fields
  * run `instance.clean()`
  * optionally run `form.validate_unique()`

 This seems a lot easier to reason about to me. I'd still like Honza to
 check this out, but I feel pretty good about it at this point. Hopefully
 I'm not missing some corner case.

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

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

[Changeset] r12678 - django/branches/releases/1.1.X/django/contrib/auth/tests

[noreply]

Author: kmtracey
Date: 2010-03-03 19:11:37 -0600 (Wed, 03 Mar 2010)
New Revision: 12678

Modified:
   django/branches/releases/1.1.X/django/contrib/auth/tests/views.py
Log:
[1.1.X] Made Python 2.3 compatibility fixes for some recent test additions.


Modified: django/branches/releases/1.1.X/django/contrib/auth/tests/views.py
===
--- django/branches/releases/1.1.X/django/contrib/auth/tests/views.py   
2010-03-03 13:46:40 UTC (rev 12677)
+++ django/branches/releases/1.1.X/django/contrib/auth/tests/views.py   
2010-03-04 01:11:37 UTC (rev 12678)
@@ -182,7 +182,7 @@
 site = Site.objects.get_current()
 self.assertEquals(response.context['site'], site)
 self.assertEquals(response.context['site_name'], site.name)
-self.assert_(isinstance(response.context['form'], AuthenticationForm), 
+self.assert_(isinstance(response.context['form'], AuthenticationForm),
  'Login form is not an AuthenticationForm')
 
 def test_security_check(self, password='password'):
@@ -205,7 +205,7 @@
 }
 )
 self.assertEquals(response.status_code, 302)
-self.assertFalse(bad_url in response['Location'], "%s should be 
blocked" % bad_url)
+self.failIf(bad_url in response['Location'], "%s should be 
blocked" % bad_url)
 
 # Now, these URLs have an other URL as a GET parameter and therefore
 # should be allowed
@@ -222,9 +222,9 @@
 }
 )
 self.assertEquals(response.status_code, 302)
-self.assertTrue('/view/?param=%s' % url_ in response['Location'], 
"/view/?param=%s should be allowed" % url_)
+self.failUnless('/view/?param=%s' % url_ in response['Location'], 
"/view/?param=%s should be allowed" % url_)
 
-
+
 class LogoutTest(AuthViewsTestCase):
 urls = 'django.contrib.auth.tests.urls'
 
@@ -249,7 +249,7 @@
 self.assert_('Logged out' in response.content)
 self.confirm_logged_out()
 
-def test_logout_with_next_page_specified(self): 
+def test_logout_with_next_page_specified(self):
 "Logout with next_page option given redirects to specified resource"
 self.login()
 response = self.client.get('/logout/next_page/')

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

Re: [Django] #3400: Support for lookup separator with list_filter admin option

[Django]

#3400: Support for lookup separator with list_filter admin option
---+
  Reporter:  n...@intv.com.au  | Owner:  jakub_vysoky   
 
Status:  new   | Milestone:  1.3
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edc nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Comment (by brentp):

 current patch does not respect limit_choices_to when specified for a
 ForeignKey.

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

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

Re: [Django] #12404: Improve max_length validation

[Django]

#12404: Improve max_length validation
---+
  Reporter:  tiliv | Owner:  josh   
   
Status:  assigned  | Milestone:  1.2
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:|  Keywords:  
max_length, validation
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by Leo):

 * cc: Leo (added)
  * needs_tests:  1 => 0

Comment:

 Updated patch with tests. I added a check for wrong type argument as well
 as invalid int.

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

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

Re: [Django] #12972: flatpages chokes if the url doesn't begin and end with a slash (but doesn't validate for it)

[Django]

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

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

Comment:

 Django's testing tools have all sorts of utils for checking form
 validation. Tests aren't optional here.

 Also - PEP8: Constants (url_regex) should be in CAPITALS.

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

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

Re: [Django] #12974: Admin docs omits several methods for a Model

[Django]

#12974: Admin docs omits several methods for a Model
---+
  Reporter:  jabapyth  | Owner:  jabapyth   
   
Status:  reopened  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  SVN
   
Resolution:|  Keywords:  admin, docs, 
method, admindocs
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * component:  Documentation => django.contrib.admin
  * needs_tests:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 Ok - problem now confirmed. For future reference: While I was eventually
 able to piece together an example that broke, it took some work. The best
 test case isn't a longer, more verbose verbal explanation -- it's a
 working sample of code that demonstrates the breakage, along with a short
 set of instructions for how to cause the breakage. For example:

 Sample model:
 {{{
 class Thing(models.Model):
 name = models.CharField(max_length=100)

 @models.permalink
 def get_absolute_url(self):
 "Get the URL"
 return ('blog_detail', None, {})

 def button(self):
 "Push the button"
 pass
 }}}
 If you inspect {{{/admin/doc/models/myapp.thing/}}} (the admin docs for
 the Thing model), button will be displayed, but get_absolute_url will not.

 The best part is that this programatic test case can form the start of the
 test for your patch. Your patch doesn't have a test case, so the 'needs
 test case' flag still applies. The fact that this particularly feature
 doesn't have any tests at the moment doesn't give you a pass to not
 include tests -- it's an opportunity to add tests to make sure the feature
 will continue to work.

 I've also turned on patch needs improvement -- At this point, the check
 for function arguments is redundant, since you can't have a function with
 a negative argument count.

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

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

Re: [Django] #12416: Improve KML Serialization

[Django]

#12416: Improve KML Serialization
---+
  Reporter:  jbronn| Owner:  jbronn  
Status:  new   | Milestone:  1.3 
 Component:  GIS   |   Version:  SVN 
Resolution:|  Keywords:  gis kml 3d style rhr
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 This doesn't seem to be an actual bug, so I'm punting it off the
 milestone.

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

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

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

[Django]

#11313: list_editable fields don't support 'save' in multiuser environment
---+
  Reporter:  margieroginski| Owner:  nobody
Status:  reopened  | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 With no further action -- not even a patch -- there's no way this makes
 1.2.

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

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

Re: [Django] #11156: Unnecessary savepoints with Oracle

[Django]

#11156: Unnecessary savepoints with Oracle
---+
  Reporter:  Richard Davies   |
 Owner:  nobody   
Status:  new   | 
Milestone:  1.3  
 Component:  Database layer (models, ORM)  |   
Version:  SVN  
Resolution:|  
Keywords:  oracle savepoints
 Stage:  Accepted  | 
Has_patch:  1
Needs_docs:  0 |   
Needs_tests:  1
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 So long as this isn't actually a bug (e.g., we're not ending up with an
 exception), this needs to be punted off 1.2.

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

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

Re: [Django] #10650: Clarify use of MEDIA_ROOT in default settings.py

[Django]

#10650: Clarify use of MEDIA_ROOT in default settings.py
-+--
  Reporter:  tvon| Owner:  nobody
Status:  new | Milestone:  1.2   
 Component:  Documentation   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * component:  File uploads/storage => Documentation

Comment:

 This is really a documentation issue masquerading as something 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10557: FormWizard should not output raw HTML for previous_fields

[Django]

#10557: FormWizard should not output raw HTML for previous_fields
+---
  Reporter:  Matthew Flanagan   | 
Owner:  nobody
Status:  new| 
Milestone:  1.3   
 Component:  django.contrib.formtools   |   
Version:  SVN   
Resolution: |  
Keywords:  wizard
 Stage:  Accepted   | 
Has_patch:  1 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 If it's not backwards-compatible it can't land in 1.2; luckily, you get
 another release cycle to get it into shape :)

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

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

Re: [Django] #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: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 Patch hasn't been updated since before 1.1, so I'd be wary of checking it
 in now for 1.2. Also, the comments above indicate this is more a feature
 addition, and unfortunately 1.2's feature-frozen.

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

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

Re: [Django] #10436: Application names i18n in the admin app broken

[Django]

#10436: Application names i18n in the admin app broken
---+
  Reporter:  ramiro| Owner:  ramiro 
  
Status:  new   | Milestone:  1.3
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  blocktrans trans 
app_label breadcrumbs capfirst title
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 I know Adrian put that bit into the template, but other than that we've
 never officially supported translation of app names, and that's really a
 much larger problem which should be dealt with all in one go rather than
 piecemeal in tickets like this one. So I'm going to punt it to 1.3.

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

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

Re: [Django] #10414: select_related ignores unrecognized fields

[Django]

#10414: select_related ignores unrecognized fields
---+
  Reporter:  trebor74hr| Owner:  nobody 
   
Status:  new   | Milestone:  1.3
   
 Component:  Database layer (models, ORM)  |   Version: 
   
Resolution:|  Keywords:  
select_related
 Stage:  Design decision needed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 While I agree it'd be nice to have error reporting when you mistype a
 field name there, I don't see it as critical for 1.2 to get out the door.

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

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

Re: [Django] #10004: Enable -c switch in xgettext call to collect translator comments

[Django]

#10004: Enable -c switch in xgettext call to collect translator comments
---+
  Reporter:  claudep   | Owner:  
Status:  new   | Milestone:  1.3 
 Component:  Internationalization  |   Version:  1.0 
Resolution:|  Keywords:  makemessages
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 This feels too much like a feature request to be on the 1.2 milestone at
 this point.

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

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

Re: [Django] #9784: Django admin: prepopulated_fields does not update on javascript (calendar) change

[Django]

#9784: Django admin: prepopulated_fields does not update on javascript 
(calendar)
change
---+
  Reporter:  x00...@gmail.com  | Owner:  dgouldin
Status:  new   | Milestone:  1.3 
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 I'm going to bump this off the 1.2 milestone, for a couple reasons:

  1. There are several tickets (this one, #9110, #9264 and #9983) all
 exposing cases where the event handling for `prepopulated_fields` falls
 over in specific edge cases, so the real solution is not to fix any of
 these individually but rather to make `prepopulate_from` more robust.
  2. I suspect the admin-ui work will be coming up for discussion in the
 1.3 timeframe, and that's a more solid place to talk about dealing with
 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9264: ModelAdmin: multipe items in prepopulated_fields breaks the auto-fillin

[Django]

#9264: ModelAdmin: multipe items in prepopulated_fields breaks the auto-fillin
---+
  Reporter:  pickel...@gmail.com   | Owner:  nobody
Status:  reopened  | Milestone:  1.3   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 I'm going to bump this off the 1.2 milestone, for a couple reasons:

  1. There are several tickets (this one, #9110, #9784 and #9983) all
 exposing cases where the event handling for `prepopulated_fields` falls
 over in specific edge cases, so the real solution is not to fix any of
 these individually but rather to make `prepopulate_from` more robust.
  2. I suspect the admin-ui work will be coming up for discussion in the
 1.3 timeframe, and that's a more solid place to talk about dealing with
 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9983: Javascript issue on admin interface with prepopulated_fields

[Django]

#9983: Javascript issue on admin interface with prepopulated_fields
---+
  Reporter:  msurdi| Owner:  kkubasik
Status:  new   | Milestone:  1.3 
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 I'm going to bump this off the 1.2 milestone, for a couple reasons:

  1. There are several tickets (this one, #9110, #9264 and #9784) all
 exposing cases where the event handling for `prepopulated_fields` falls
 over in specific edge cases, so the real solution is not to fix any of
 these individually but rather to make `prepopulate_from` more robust.
  2. I suspect the admin-ui work will be coming up for discussion in the
 1.3 timeframe, and that's a more solid place to talk about dealing with
 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #9964: Transaction middleware closes the transaction only when it's marked as dirty

[Django]

#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---+
  Reporter:  ishirav   | Owner:  
mtredinnick 
Status:  assigned  | Milestone:  1.3
 
 Component:  Database layer (models, ORM)  |   Version:  1.0-beta-1 
 
Resolution:|  Keywords:  
transactions
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 A patch which wasn't ready for 1.1 and hasn't been updated since probably
 isn't ready for 1.2.

 (also, a better solution might just be to document that if you're doing
 things in raw SQL you should manually inform the transaction middleware by
 setting the transaction to dirty)

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

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

Re: [Django] #9847: hardcoded string in core/handlers/base.py

[Django]

#9847: hardcoded string in core/handlers/base.py
-+--
  Reporter:  drakkan | Owner: 
Status:  new | Milestone:  1.2
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by ubernostrum):

 I think there should be content in the response, since otherwise you'd
 show a completely blank page to an end user, requiring them to know about
 HTTP status codes and how to find out what status code we sent back.

 I can see a couple options for doing this:

  1. Don't bother trying to translate the response content, and just use
 the language in the HTTP spec (so just "403 Forbidden").
  2. Set a default `content` value for `HttpResponseForbidden`, and mark it
 for translation. I think we can do that safely since it's over in
 `django.http` and settings will already be set up by the time it gets
 imported.

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

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

Re: [Django] #6073: compile-messages.py parse error for utf-8 files with signature

[Django]

#6073: compile-messages.py parse error for utf-8 files with signature
-+--
  Reporter:  Wonlay  | Owner:  ramiro 
Status:  new | Milestone:  1.3
 Component:  Internationalization|   Version:  SVN
Resolution:  |  Keywords:  msgfmt, BOM
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 UTF-8 with a BOM is, as far as I know, so rare that there's probably no
 urgent need to deal with it in 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13022: when saving a model with m2m field in the admin, 'clear' and 'add' m2m_changed signals are fired even when there is no change.

[Django]

#13022: when saving a model with m2m field in the admin, 'clear' and 'add'
m2m_changed signals are fired even when there is no change.
---+
  Reporter:  benc  | Owner:  nobody 
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  signals, 
m2m_changed
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Old description:

> I've built a simple test project with one app and two models, Model1 and
> Model2.
> Model2 has a ManyToManyField to Model1.
> I've created one Model1 instance and one Model2 instance with a relation
> to the Model1 instance.
>
> When saving the Model2 instance in the admin, even without a change,
> m2m_changed fires twice.
> I think it shouldn't fire at all when the admin form is saved without a
> change:
>
> sender  
> instance  Model2 object
> action  clear
> model  
> sender  
> instance  Model2 object
> action  add
> model  

New description:

 I've built a simple test project with one app and two models, Model1 and
 Model2.
 Model2 has a ManyToManyField to Model1.
 I've created one Model1 instance and one Model2 instance with a relation
 to the Model1 instance.

 When saving the Model2 instance in the admin, even without a change,
 m2m_changed fires twice.
 I think it shouldn't fire at all when the admin form is saved without a
 change:

 {{{
 sender  
 instance  Model2 object
 action  clear
 model  
 sender  
 instance  Model2 object
 action  add
 model  
 }}}

Comment:

 reformatted description.

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

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

Re: [Django] #12962: Broken Admin Delete Action With Confirmation

[Django]

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

  * needs_better_patch:  0 => 1

Comment:

 With the patch applied, deleting is working. However, we still have a few
 issues:

  1. If you hit 'Go' while an action is selected and no list_editable
 changes are made, the action is applied but no, "# items have changed"
 message is sent.
  2. If you hit 'Go' while an action is selected, and list_editable changes
 have been made, both changes are applied (not what we want)
  3. If you hit the list_editable save button with items selected and an
 action chosen, you get the, "No action selected" message.

 I'm working on an additional 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #13022: when saving a model with m2m field in the admin, 'clear' and 'add' m2m_changed signals are fired even when there is no change.

[Django]

#13022: when saving a model with m2m field in the admin, 'clear' and 'add'
m2m_changed signals are fired even when there is no change.
--+-
 Reporter:  benc  |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:  signals, m2m_changed  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I've built a simple test project with one app and two models, Model1 and
 Model2.
 Model2 has a ManyToManyField to Model1.
 I've created one Model1 instance and one Model2 instance with a relation
 to the Model1 instance.

 When saving the Model2 instance in the admin, even without a change,
 m2m_changed fires twice.
 I think it shouldn't fire at all when the admin form is saved without a
 change:

 sender  
 instance  Model2 object
 action  clear
 model  
 sender  
 instance  Model2 object
 action  add
 model  

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

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

Re: [Django] #9264: ModelAdmin: multipe items in prepopulated_fields breaks the auto-fillin

[Django]

#9264: ModelAdmin: multipe items in prepopulated_fields breaks the auto-fillin
---+
  Reporter:  pickel...@gmail.com   | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

  * stage:  Accepted => Ready for checkin

Comment:

 This really should be updated to use jQuery now, but it's not a big deal.
 We can commit it and clean it up later if needed.

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

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

Re: [Django] #8918: FileField upload_to should not be required for custom backends

[Django]

#8918: FileField upload_to should not be required for custom backends
---+
  Reporter:  leahculver| Owner:  nobody 

Status:  new   | Milestone:  1.2

 Component:  File uploads/storage  |   Version:  SVN

Resolution:|  Keywords:  FileField, files, 
upload, S3, upload_to
 Stage:  Ready for checkin | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * stage:  Accepted => Ready for checkin

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

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

Re: [Django] #8874: problem with URLs on FastCGI after update to 1.0

[Django]

#8874: problem with URLs on FastCGI after update to 1.0
-+--
  Reporter:  kyprizel| Owner:  kyprizel
Status:  closed  | Milestone:  1.2 
 Component:  Core framework  |   Version:  SVN 
Resolution:  invalid |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

Comment:

 This isn't a bug, so I'm closing it. Feel free to open a new ticket with a
 documentation patch if you like.

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

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

Re: [Django] #13020: Django session documentation is wrong

[Django]

#13020: Django session documentation is wrong
+---
  Reporter:  bryan  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by donspaulding):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Documentation
  * needs_tests:  => 0
  * needs_docs:  => 0

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

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

Re: [Django] #8171: Invalid formset when form is missing from POST data

[Django]

#8171: Invalid formset when form is missing from POST data
---+
  Reporter:  James Chua   | Owner:  
brosner 
Status:  closed| Milestone:  1.2
 
 Component:  Forms |   Version:  SVN
 
Resolution:  wontfix   |  Keywords:  
formsets
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Again, don't do this. See #8649.

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

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

Re: [Django] #11801: Should be able to get deleted_forms on a formset even if it contains a deleted form that would have been invalid

[Django]

#11801: Should be able to get deleted_forms on a formset even if it contains a
deleted form that would have been invalid
+---
  Reporter:  dantallis  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Forms  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Re: [Django] #8165: When using can_order=True on formset, ordered_forms is not avaible when formset.is_valid() is false

[Django]

#8165: When using can_order=True on formset, ordered_forms is not avaible when
formset.is_valid() is false
---+
  Reporter:  James Chua   | Owner:  zain   
 
Status:  closed| Milestone:  1.2
 
 Component:  Forms |   Version:  SVN
 
Resolution:  duplicate |  Keywords:  
formsets
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by jacob):

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

Comment:

 Dup of #11801.

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

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

Re: [Django] #7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse objects.

[Django]

#7581: Middleware accessing HttpResponse.content breaks streaming HttpResponse
objects.
-+--
  Reporter:  mrmachine   | Owner:  ccahoon  
 
Status:  new | Milestone:   
 
 Component:  Core framework  |   Version:  SVN  
 
Resolution:  |  Keywords:  stream 
HttpResponse Content-Length
 Stage:  Design decision needed  | Has_patch:  1
 
Needs_docs:  0   |   Needs_tests:  0
 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * milestone:  1.2 =>

Comment:

 Bumping from 1.2: there's still no agreement about the correct approach
 here.

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

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

Re: [Django] #12978: Support in syndication framework for CSS stylesheet links

[Django]

#12978: Support in syndication framework for CSS stylesheet links
+---
  Reporter:  intrepidweb| Owner:  nobody
 
Status:  reopened   | Milestone:
 
 Component:  RSS framework  |   Version:  1.1   
 
Resolution: |  Keywords:  syndication css 
stylesheets
 Stage:  Someday/Maybe  | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

  * stage:  Unreviewed => Someday/Maybe

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

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

Re: [Django] #12978: Support in syndication framework for CSS stylesheet links

[Django]

#12978: Support in syndication framework for CSS stylesheet links
+---
  Reporter:  intrepidweb| Owner:  nobody
 
Status:  reopened   | Milestone:
 
 Component:  RSS framework  |   Version:  1.1   
 
Resolution: |  Keywords:  syndication css 
stylesheets
 Stage:  Unreviewed | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by intrepidweb):

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

Comment:

 RSS feeds contain CSS and/or XSL stylesheets all the time. Here's a link
 on how to add an RSS stylesheet:

 http://www.oreillynet.com/pub/a/network/2005/07/01/rss.html

 I tried to include a list of major websites that use stylesheets in their
 RSS feeds, but the spam filter blocked it. However, if you check the feeds
 of CNN, CBS News, Reuters, Newsweek, Time and many more, you'll see XSL
 and/or CSS stylesheets linked in the source.

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

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

Re: [Django] #12972: flatpages chokes if the url doesn't begin and end with a slash (but doesn't validate for it)

[Django]

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

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

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

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

Re: [Django] #12974: Admin docs omits several methods for a Model

[Django]

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

Status:  reopened   | Milestone:

 Component:  Documentation  |   Version:  SVN   

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

Needs_docs:  0  |   Needs_tests:  0 

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

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

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

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

Re: [Django] #9616: bdist_rpm fails in 1.0.1 - version names with hyphens are not compatible with rpm specs

[Django]

#9616: bdist_rpm fails in 1.0.1 - version names with hyphens are not compatible
with rpm specs
+---
  Reporter:  tome   | Owner:  mtredinnick  
Status:  closed | Milestone:  1.2  
 Component:  Uncategorized  |   Version:  1.0  
Resolution:  wontfix|  Keywords:  rpm, bdist_rpm, setup
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 I'm going to make a release-manager pronouncement here and say we're not
 going to fix this. Changing our version info to work around one specific
 packaging system's limitations, especially when those limitations only
 exist in older versions of Python that we'll be deprecating anyway, is not
 a productive use of our time; people who are interested in using
 `bdist_rpm` to build Django packages can correct this manually as needed.

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

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

Re: [Django] #9063: Feature request: Advanced search in Admin

[Django]

#9063: Feature request: Advanced search in Admin
-+--
  Reporter:  Guilherme M. Gondim   | 
Owner:  nobody   
Status:  closed  | 
Milestone:   
 Component:  django.contrib.admin|   
Version:  SVN  
Resolution:  wontfix |  
Keywords:  search, admin
 Stage:  Unreviewed  | 
Has_patch:  0
Needs_docs:  0   |   
Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

 * cc: a...@andybak.net (added)

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

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

Re: [Django] #12803: Provide styling for warning and error messages

[Django]

#12803: Provide styling for warning and error messages
---+
  Reporter:  bbolli| Owner:  nobody 
 
Status:  new   | Milestone:  1.3
 
 Component:  django.contrib.admin  |   Version:  1.2-beta   
 
Resolution:|  Keywords:  admin messages 
icons
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 This is really a feature request, and so can't go on 1.2.

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

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

Re: [Django] #12810: ManyToManyField.db_table

[Django]

#12810: ManyToManyField.db_table
+---
  Reporter:  strelnikovdmitrij  | Owner:  nobody 
Status:  new| Milestone:  1.3
 Component:  django-admin.py|   Version:  SVN
Resolution: |  Keywords:  ManyToManyField
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 If this is a bug it's a validation bug -- since the problem is we're not
 warning that you've set up two things which each want the same table name
 -- but it's enough of an edge case that I don't think it needs to be in
 1.2.

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

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

Re: [Django] #11905: modelform_factory returns a broken form when given wrong value for fields

[Django]

#11905: modelform_factory returns a broken form when given wrong value for 
fields
---+
  Reporter:  ben   | Owner:  nobody 
 
Status:  new   | Milestone:  1.3
 
 Component:  Forms |   Version:  1.1
 
Resolution:|  Keywords:  modelform_factory, modelform, 
fields
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 While better error reporting is always nice, it's not release-critical and
 can be bumped to 1.3.

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

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

Re: [Django] #3349: If an ImportError occurs within some loaders a rather confusing exception is raised.

[Django]

#3349: If an ImportError occurs within some loaders a rather confusing exception
is raised.
+---
  Reporter:  Chris Wagner   | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Template system|   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  1 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

  * milestone:  1.2 => 1.3

Comment:

 Given that this is really more of a minor annoyance than a bug, and that
 we've survived with it thus far, I think it's safe to say it's non-
 critical for 1.2 and can be handled on the 1.3 cycle.

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

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

Re: [Django] #6533: Syndication Framework: Item titles and descriptions double-escaped

[Django]

#6533: Syndication Framework: Item titles and descriptions double-escaped
+---
  Reporter:  miracle2k  | Owner:  jacob
Status:  closed | Milestone:  1.2  
 Component:  RSS framework  |   Version:  SVN  
Resolution:  fixed  |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  1  |  
+---
Changes (by ubernostrum):

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

Comment:

 As Jacob points out, the RSS-specific behavior is correct as of [8632].
 Supporting additional features of Atom is a separate issue, and there's
 already a long-standing ticket open for general improvements to our Atom
 support.

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

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

Re: [Django] #8968: No way to utilize `next` parameter to redirect after comment deletion

[Django]

#8968: No way to utilize `next` parameter to redirect after comment deletion
--+-
  Reporter:  Dzhus| Owner:  kkubasik
Status:  reopened | Milestone:  
 Component:  django.contrib.comments  |   Version:  1.0 
Resolution:   |  Keywords:  comments
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  1|   Needs_tests:  1   
Needs_better_patch:  1|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 This isn't critical enough to get developer time before the 1.2 release;
 with luck we'll hit it in a 1.2.x bugfix release, or if not then in 1.3.

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

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

Re: [Django] #12894: Not-so-nice anchor for section titles in docs.djangoproject.com

[Django]

#12894: Not-so-nice anchor for section titles in docs.djangoproject.com
--+-
  Reporter:  anonymous| Owner:  nobody  
Status:  reopened | Milestone:  
 Component:  Django Web site  |   Version:  SVN 
Resolution:   |  Keywords:  model validation
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 If upgrading djangoproject.com's Sphinx fixes this, then it's not a
 problem in Django itself and shouldn't be on a milestone.

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

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

Re: [Django] #13018: Raw request data should be exposed via request object.

[Django]

#13018: Raw request data should be exposed via request object.
+---
  Reporter:  Damon  | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  HTTP handling  |   Version:  1.1 
Resolution:  wontfix|  Keywords:  raw request data
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 The raw request data is exposed; in the WSGI adapter it's on the `environ`
 property of `WSGIRequest` (this is the original, unmodified WSGI environ
 passed to Django), and on mod_python it's the `_req` property of
 `ModPythonRequest` (this is the original mod_python request object passed
 to Django).

 At the moment I don't think these need to be documented, though, because
 they're internal implementation details of the specific gateway protocols
 and so don't constitute a consistent Django-level API (since they vary
 according to the gateway in use), and are easy enough to find if you just
 go look at the code Django implements to handle those protocols.

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

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

Re: [Django] #12974: Admin docs omits several methods for a Model

[Django]

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

Status:  reopened   | Milestone:

 Component:  Documentation  |   Version:  SVN   

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

Needs_docs:  0  |   Needs_tests:  1 

Needs_better_patch:  1  |  
+---
Changes (by jabapyth):

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

Comment:

 When admindocs displays methods for a model, it only displays ones w/ no
 arguments, or rather with only the (self) argument. The reason for this is
 no doubt to display only those methods which are valid for use in a
 template.

 '''This patch is trying to solve the following problem:'''[[BR]]
 Occasionally a model can have a method with ''no arguments'', due to
 preprocessing @decorators or the use of the django.utils.curry function.
 These methods are then overlooked by admindocs, which checks for ''exactly
 one'' argument.[[BR]]
 With this patch, it will check for ''fewer than or equal to'' one required
 argument.

 The 'test' case that brought this problem to my attention was using that
 [http://github.com/nathanborror/django-basic-apps django-basic-apps] blog
 app, whose Post model defines a [http://github.com/nathanborror/django-
 basic-apps/blob/master/basic/blog/models.py#L64 get_absolute_url] method.
 This method has a @permalink decorator before it, which results in
 Post.get_absolute_url having zero arguments. Given that the current code
 checks for ''exactly one'' argument, this method (which is totally valid
 for use in a template) is not displayed on the docs page.

 Looking deeper into the code, I found that any get_absolute_url (even
 without a @permalink) gets ''curry''d by the
 
[http://code.djangoproject.com/browser/django/trunk/django/db/models/base.py#L235
 base model], and would therefore never be displayed by admindocs.

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

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

Re: [Django] #13021: Allowing models to influence QuerySet.update

[Django]

#13021: Allowing models to influence QuerySet.update
---+
  Reporter:  seveas| Owner:  seveas
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:  update
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by seveas):

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

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

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

[Django] #13021: Allowing models to influence QuerySet.update

[Django]

#13021: Allowing models to influence QuerySet.update
--+-
 Reporter:  seveas|   Owner:  seveas
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  update|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 I'd like to have a bit more control over what update() does, e.g. for
 auditing purposes. I know that I can simply write a few lines of code near
 every update() call to do what I want, but that violates DRY.

 Attached patch adds a few new features:

 * pre_update and post_update signals
 * a pre_update method for Field that does nothing
 * a pre_update method for DateField for auto_now magic
 * an update() method for Model that calls pre_update for all fields. This
 method is a classmethod
 * a patched QuerySet.update() that
   - Sends the pre_update and post_update signals
   - Calls the models update method to update the kwargs dict

 The patch is untested, but should give a good idea of what I want to
 achieve. Is this approach suitable for inclusion in django ? If so, I will
 complete the patch, add tests and documentation and will submit it for
 inclusion at the appropriate 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-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #12972: flatpages chokes if the url doesn't begin and end with a slash (but doesn't validate for it)

[Django]

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

 As far as testing goes, it seems to be a UI change, and therefore hard to
 unittest -- unless you would like me to write some cases for the
 regex[[BR]]
 to manually examine:

 enable APPEND_SLASH (well it is by default), and enable CommonMiddleware
 (default again)[[BR]]
 - on the admin page, create a new flatpage, but omit the trailing slash in
 the URL[[BR]]
 - (should fail to validate)

 disable APPEND_SLASH[[BR]]
 - create a flatpage, omit the slash[[BR]]
 - (should accept)

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

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

Re: [Django] #12382: Deleting an inline can delete the whole inlined model instance recursively

[Django]

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

 * cc: esch...@gmail.com (added)

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

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

Re: [Django] #7539: Add ON DELETE and ON UPDATE support to Django

[Django]

#7539: Add ON DELETE and ON UPDATE support to Django
---+
  Reporter:  glassfordm| Owner: 
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  SVN
Resolution:|  Keywords:  feature
 Stage:  Design decision needed| Has_patch:  1  
Needs_docs:  1 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: esch...@gmail.com (added)

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

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

[Django] #13020: Django session documentation is wrong

[Django]

#13020: Django session documentation is wrong
---+
 Reporter:  bryan  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://docs.djangoproject.com/en/1.1/topics/http/sessions/#using-sessions-
 out-of-views

 You shouldn't pass a session_key into SessionStore, that gets generated
 automatically when you save() it.


 {{{
 >>> from django.contrib.sessions.backends.db import SessionStore
 >>> s = SessionStore()
 >>> s['last_login'] = datetime.datetime(2005, 8, 20, 13, 35, 10)
 >>> s['last_login']
 datetime.datetime(2005, 8, 20, 13, 35, 0)
 >>> s.save()
 >>> s.session_key
 '2b1189a188b44ad18c35e113ac6ceead
 }}}




 {{{
 >>> from django.contrib.sessions.models import Session
 >>> s = Session.objects.get(pk='2b1189a188b44ad18c35e113ac6ceead')
 >>> s.expire_date
 datetime.datetime(2005, 8, 20, 13, 35, 12)
 }}}

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

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

Re: [Django] #12955: Large file (bigger than 2GB) upload

[Django]

#12955: Large file (bigger than 2GB) upload
---+
  Reporter:  iscarface | Owner:  isagalaev
Status:  new   | Milestone:   
 Component:  File uploads/storage  |   Version:  1.1  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by isagalaev):

  * owner:  nobody => isagalaev

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

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

Re: [Django] #12955: Large file (bigger than 2GB) upload

[Django]

#12955: Large file (bigger than 2GB) upload
---+
  Reporter:  iscarface | Owner:  nobody
Status:  new   | Milestone:
 Component:  File uploads/storage  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by isagalaev):

 The problem is caused by using {{{len(self.file)}}} because len() tries to
 typecast the result of {{__len__()}} to an actual int. Which on 32-bit
 machines is < 2G. I think the fix might be as simple as using directly
 {{.size}} instead of {{len()}} everywhere...

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

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

Re: [Django] #12960: return value (cleaned_data) from clean() method is ignored

[Django]

#12960: return value (cleaned_data) from clean() method is ignored
---+
  Reporter:  krejcik   | Owner:  jkocherhans
Status:  new   | Milestone:  1.2
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Comment (by patrys):

 Replying to [comment:5 jkocherhans]:
 > That's ''part'' of a possible solution, but it isn't enough on its own.
 `Model.clean_fields()` and `Model.clean()` can modify the model instance
 in place, so applying all of `form.cleaned_data` to the model after that
 happens could cause different problems.

 It shouldn't be possible to do the same thing by either:

  * touching `self.instance`
  * or touching `self.cleaned_data`
  * or returning a modified copy of `self.cleaned_data`

 I think self.instance existing at the point when `clean()` is called is an
 implementation detail and is not guaranteed by the API documentation.
 Modifying the instance directly inside `clean()` should be discouraged.

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

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

Re: [Django] #13019: create_update: proxy object displayed instead of model verbose name

[Django]

#13019: create_update: proxy object displayed instead of model verbose name
+---
  Reporter:  Beuc   | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Beuc):

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

Comment:

 However the change apparently requires all verbose_name /
 verbose_name_plural to be explicitely declared as u"".

 Previously I could use:
 {{{
 # -*- coding: utf-8 -*-
 ...
   verbose_name="établissement"
 }}}

 Now it's necessary to also mark the string as unicode:
 {{{
 # -*- coding: utf-8 -*-
 ...
   verbose_name=u"établissement"
 }}}

 otherwise I now get:
 {{{
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 0:
 ordinal not in range(128)
 }}}

 This is inconvenient.

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

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

[Django] #13019: create_update: proxy object displayed instead of model verbose name

[Django]

#13019: create_update: proxy object displayed instead of model verbose name
---+
 Reporter:  Beuc   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 I get this kind of error at http://localhost:8000/users/10/
 {{{
 No  found for
 {'username__exact': u'10'}
 }}}

 Apparently this is due to its non-unicode expansion:
 {{{
 # Note: User.Meta.verbose_name == _('user')
 raise Http404("No %s found for %s"
   % (model._meta.verbose_name, lookup_kwargs))
 }}}

 It's fixed by using a Unicode string:
 {{{
 u"No %s found for %s"
 }}}

 Patch attached.

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

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

Re: [Django] #12960: return value (cleaned_data) from clean() method is ignored

[Django]

#12960: return value (cleaned_data) from clean() method is ignored
---+
  Reporter:  krejcik   | Owner:  jkocherhans
Status:  new   | Milestone:  1.2
 Component:  Forms |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  1 |  
---+
Changes (by jkocherhans):

  * owner:  nobody => jkocherhans
  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1
  * status:  reopened => new

Comment:

 Replying to [comment:4 patrys]:
 > Could we fix it by (re)constructing the instance at the end of
 full_clean()?

 That's ''part'' of a possible solution, but it isn't enough on its own.
 `Model.clean_fields()` and `Model.clean()` can modify the model instance
 in place, so applying all of `form.cleaned_data` to the model after that
 happens could cause different problems.

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

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

Re: [Django] #12997: Add Metadata Targets to QuerySet API Reference

[Django]

#12997: Add Metadata Targets to QuerySet API Reference
+---
  Reporter:  dwillis| Owner:  dwillis
Status:  assigned   | Milestone:  1.3
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #9453: Can't reset djangoproject account password

[Django]

#9453: Can't reset djangoproject account password
---+
  Reporter:  Matias   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Django Web site   |   Version:  1.0
  
Resolution:  duplicate |  Keywords:  django 
password reset
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 Marking as a duplicate of #11539

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

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

Re: [Django] #12994: error in Register (for logon to this site)

[Django]

#12994: error in Register (for logon to this site)
--+-
  Reporter:  djazel   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Uncategorized|   Version:  1.1   
Resolution:  duplicate|  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 Effectively a duplicate of #9453

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

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

Re: [Django] #12988: Add support of IDN domains for URLField validator.

[Django]

#12988: Add support of IDN domains for URLField validator.
---+
  Reporter:  niksite   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:  IDN   
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

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

Re: [Django] #12985: Add a download link for the current file with the current file name to FileInput

[Django]

#12985: Add a download link for the current file with the current file name to
FileInput
-+--
  Reporter:  jpic| Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 I agree with @AndrewIngram. Exact rendering of widgets is a user choice;
 links to existing file content aren't hard to add, either in your own
 template, or in a custom widget.

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

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

Re: [Django] #12979: TestCase disables savepoint_commit, savepoint_rollback

[Django]

#12979: TestCase disables savepoint_commit, savepoint_rollback
+---
  Reporter:  forest | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

  * stage:  Unreviewed => Accepted

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

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

[Changeset] r12677 - in django/branches/releases/1.1.X: . tests/modeltests/files

[noreply]

Author: kmtracey
Date: 2010-03-03 07:46:40 -0600 (Wed, 03 Mar 2010)
New Revision: 12677

Modified:
   django/branches/releases/1.1.X/
   django/branches/releases/1.1.X/tests/modeltests/files/models.py
Log:
[1.1.X] Fixed the files test to not care whether the names are reported as 
bytestrings or unicode. Refs #12898. 

r12676 from trunk.



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

Modified: django/branches/releases/1.1.X/tests/modeltests/files/models.py
===
--- django/branches/releases/1.1.X/tests/modeltests/files/models.py 
2010-03-03 13:40:52 UTC (rev 12676)
+++ django/branches/releases/1.1.X/tests/modeltests/files/models.py 
2010-03-03 13:46:40 UTC (rev 12677)
@@ -69,14 +69,14 @@
 >>> dirs
 []
 >>> files.sort()
->>> files
-['default.txt', 'django_test.txt']
+>>> files == ['default.txt', 'django_test.txt']
+True
 
 >>> obj1.save()
 >>> dirs, files = temp_storage.listdir('tests')
 >>> files.sort()
->>> files
-['assignment.txt', 'default.txt', 'django_test.txt']
+>>> files == ['assignment.txt', 'default.txt', 'django_test.txt']
+True
 
 # Files can be read in a little at a time, if necessary.
 

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

Re: [Django] #12978: Support in syndication framework for CSS stylesheet links

[Django]

#12978: Support in syndication framework for CSS stylesheet links
+---
  Reporter:  intrepidweb| Owner:  nobody
 
Status:  closed | Milestone:
 
 Component:  RSS framework  |   Version:  1.1   
 
Resolution:  wontfix|  Keywords:  syndication css 
stylesheets
 Stage:  Unreviewed | Has_patch:  0 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I'm not aware of any CSS technique that works reliably for RSS or Atom
 feeds. This is largely because RSS is intended to be machine readable, not
 human readable.

 If I'm mistaken, I'm open to suggestions on what technique we should be
 supporting.

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

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

[Changeset] r12676 - django/trunk/tests/modeltests/files

[noreply]

Author: kmtracey
Date: 2010-03-03 07:40:52 -0600 (Wed, 03 Mar 2010)
New Revision: 12676

Modified:
   django/trunk/tests/modeltests/files/models.py
Log:
Fixed the files test to not care whether the names are reported as bytestrings 
or unicode. Refs #12898.


Modified: django/trunk/tests/modeltests/files/models.py
===
--- django/trunk/tests/modeltests/files/models.py   2010-03-03 09:07:36 UTC 
(rev 12675)
+++ django/trunk/tests/modeltests/files/models.py   2010-03-03 13:40:52 UTC 
(rev 12676)
@@ -67,14 +67,14 @@
 >>> dirs
 []
 >>> files.sort()
->>> files
-['default.txt', 'django_test.txt']
+>>> files == ['default.txt', 'django_test.txt']
+True
 
 >>> obj1.save()
 >>> dirs, files = temp_storage.listdir('tests')
 >>> files.sort()
->>> files
-['assignment.txt', 'default.txt', 'django_test.txt']
+>>> files == ['assignment.txt', 'default.txt', 'django_test.txt']
+True
 
 # Files can be read in a little at a time, if necessary.
 
@@ -113,13 +113,13 @@
 
 # Multiple files with the same name get _N appended to them.
 
->>> objs = [Storage() for i in range(3)] 
->>> for o in objs:  
-... o.normal.save('multiple_files.txt', ContentFile('Same Content')) 
+>>> objs = [Storage() for i in range(3)]
+>>> for o in objs:
+... o.normal.save('multiple_files.txt', ContentFile('Same Content'))
 >>> [o.normal for o in objs]
 [, , ]
->>> for o in objs: 
-... o.delete() 
+>>> for o in objs:
+... o.delete()
 
 # Default values allow an object to access a single file.
 

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

Re: [Django] #12977: Index length errors running tests on MySQL

[Django]

#12977: Index length errors running tests on MySQL
---+
  Reporter:  carljm| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * component:  Testing framework => Database layer (models, ORM)

Comment:

 Actually, the problem isn't just the testing framework; Character limits
 should be enforced for index creation generally.

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

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

Re: [Django] #12977: Index length errors running tests on MySQL

[Django]

#12977: Index length errors running tests on MySQL
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #12975: Docs for contrib.admindocs?

[Django]

#12975: Docs for contrib.admindocs?
+---
  Reporter:  jabapyth   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.1 
Resolution: |  Keywords:  docs, admindocs, api
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

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

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

Re: [Django] #12974: Admin docs omits several methods for a Model

[Django]

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

Status:  closed | Milestone:

 Component:  Documentation  |   Version:  SVN   

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

Needs_docs:  0  |   Needs_tests:  1 

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

  * status:  new => closed
  * needs_better_patch:  0 => 1
  * resolution:  => worksforme

Comment:

 Firstly - please generate patches against the root of the source tree.

 Secondly, due to the absence of a concrete test case (either in code, or
 in the problem description), I can't work out what problem it is that this
 patch is trying to solve.

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

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

Re: [Django] #13014: Cache templatetag is not locale aware

[Django]

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

 You'd also want to mention that they'd have to pass request in the
 context, or use the request context processor & a requestcontext.

 But sure, if that's enough then someone can just write some nice docs :)

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

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

Re: [Django] #12972: flatpages chokes if the url doesn't begin and end with a slash (but doesn't validate for it)

[Django]

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

  * needs_better_patch:  0 => 1

Comment:

 Also - please generate patches against the root of the tree.

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

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

Re: [Django] #13018: Raw request data should be exposed via request object.

[Django]

#13018: Raw request data should be exposed via request object.
+---
  Reporter:  Damon  | Owner:  nobody  
Status:  new| Milestone:  
 Component:  HTTP handling  |   Version:  1.1 
Resolution: |  Keywords:  raw request data
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Please don't put new feature requests in the milestone for a feature-
 frozen release.

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

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

Re: [Django] #12972: flatpages chokes if the url doesn't begin and end with a slash (but doesn't validate for it)

[Django]

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

  * component:  Forms => Contrib apps
  * stage:  Unreviewed => Accepted

Comment:

 Checking for the trailing slash isn't necessarily a given -- you only need
 the trailing slash if APPEND_SLASH is enabled.

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

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

Re: [Django] #12374: QuerySet .iterator() loads everything into memory anyway

[Django]

#12374: QuerySet .iterator() loads everything into memory anyway
---+
  Reporter:  Nick Welch   | Owner:  nobody 
 
Status:  closed| Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.1
 
Resolution:  worksforme|  Keywords:  orm, 
cache, iterator
 Stage:  Unreviewed| Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

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

Comment:

 The most likely cause of problems here is having DEBUG=True enabled; this
 will cause the debug cursor to soak up memory.

 If you can validate that this problem still exists with DEBUG=False (and
 without the MySQL query cache problems), please reopen.

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

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

Re: [Django] #10700: Searching 1.0 docs -- results link to dev docs

[Django]

#10700: Searching 1.0 docs -- results link to dev docs
--+-
  Reporter:  kmtracey | Owner:  jacob
Status:  assigned | Milestone:   
 Component:  Django Web site  |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Comment (by d0ugal):

 Just a note to add I think russ meant to write;

 The "latest" option searches the '''dev''' docs. There's no way to search
 the 1.1 docs specifically.

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

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

Re: [Django] #10700: Searching 1.0 docs -- results link to dev docs

[Django]

#10700: Searching 1.0 docs -- results link to dev docs
--+-
  Reporter:  kmtracey | Owner:  jacob
Status:  assigned | Milestone:   
 Component:  Django Web site  |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Accepted | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Comment (by russellm):

 Additional (but related) problem reported by Dougal Matthews on django-
 dev: The "latest" option searches the 1.1 docs. There's no way to search
 the 1.1 docs specifically.

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

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

Re: [Django] #13014: Cache templatetag is not locale aware

[Django]

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

 IMO, we should simply mention in the docs that this works well:

 {{{
 {% cache 60 welcome request.LANGUAGE_CODE %}
 {% trans "Welcome to zombo.com" %}
 {% endcache %}
 }}}

 It's not exactly the same as the cache/middleware approach, but that's
 true for fragment caching anyway -- it's built to be flexible in contrast
 to out of the box caching of the middleware/decorator mechanism.

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

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

[Django] #13018: Raw request data should be exposed via request object.

[Django]

#13018: Raw request data should be exposed via request object.
--+-
 Reporter:  Damon |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  HTTP handling | Version:  1.1   
 Keywords:  raw request data  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I recently had the need to proxy some requests from some clients to 3rd
 party servers. Trying to avoid skewing stats I tried to replicate the
 clients headers when making the new requests to the 3rd party. Not wanting
 to loop through all items in request.META I looked for a Django property
 that exposed the raw request data. There isn't one.

 I've checked the source of various Django web proxies and they either
 don't try to replicate headers at all or they end up with the approach I
 ultimately had to take - looping over request.META for "HTTP_" prefixed
 keys, changing them to title case and replacing underscores with hyphens.

 Django needs to expose raw request data.

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

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

Re: [Django] #12960: return value (cleaned_data) from clean() method is ignored

[Django]

#12960: return value (cleaned_data) from clean() method is ignored
---+
  Reporter:  krejcik   | Owner:  nobody
Status:  reopened  | Milestone:  1.2   
 Component:  Forms |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by patrys):

 Could we fix it by (re)constructing the instance at the end of
 full_clean()?

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

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

[Django] #13017: generic relation generates needless join

[Django]

#13017: generic relation generates needless join
-+--
 Reporter:  MS   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Database layer (models, ORM) | Version:  SVN   
 Keywords:  database joins generic relation  |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 I have an generic relation, and tries to do some database queries with
 this relation.
 When looking at the generated sql query i saw, that double joins are
 created. This happens
 because generic relations are based on m2m table with a missing database
 table.

 An example for the model:
 {{{
 from django.db import models
 from django.contrib.contenttypes.models import ContentType
 from django.contrib.contenttypes import generic

 class GenericTest(models.Model):
 contentType = models.ForeignKey(ContentType)
 objectId = models.PositiveIntegerField()
 contentObject = generic.GenericForeignKey('contentType', 'objectId')

 class RefTest(models.Model):
 generic = generic.GenericRelation(GenericTest,
 content_type_field='contentType', object_id_field='objectId')
 testdata = models.PositiveIntegerField()
 }}}
 the query:

 {{{GenericTest.objects.filter(reftest__testdata=0)}}}

 as sql:

 {{{('SELECT U0.`id` FROM `test_generictest` U0 INNER JOIN
 `test_generictest` U1 ON (U0.`id` = U1.`id`) INNER JOIN `test_reftest` U2
 ON (U1.`objectId` = U2.`id`) WHERE U2.`testdata` = %s ', (0,))}}}

 With the applied patch, which made the same test, which is done in the
 direct case, the sql query looks like:

 {{{('SELECT U0.`id` FROM `test_generictest` U0 INNER JOIN `test_reftest`
 U1 ON (U0.`id` = U1.`id`) WHERE U1.`testdata` = %s ', (0,))}}}

 For simple databases and simple sql queries, this extra join is no
 problem, but with complex ones, its a huge performance lack.

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

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

[Changeset] r12675 - django/trunk/docs/ref

[noreply]

Author: ubernostrum
Date: 2010-03-03 03:07:36 -0600 (Wed, 03 Mar 2010)
New Revision: 12675

Modified:
   django/trunk/docs/ref/django-admin.txt
Log:
Fixed #12969: Use versionadded directive for the new --symlinks option to the 
makemessages command.

Modified: django/trunk/docs/ref/django-admin.txt
===
--- django/trunk/docs/ref/django-admin.txt  2010-03-03 09:02:53 UTC (rev 
12674)
+++ django/trunk/docs/ref/django-admin.txt  2010-03-03 09:07:36 UTC (rev 
12675)
@@ -476,6 +476,8 @@
 
 .. django-admin-option:: --symlinks
 
+.. versionadded:: 1.2
+
 Use the ``--symlinks`` or ``-s`` option to follow symlinks to directories when
 looking for new translation strings.
 

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

[Changeset] r12674 - django/branches/releases/1.1.X/docs/ref/forms

[noreply]

Author: ubernostrum
Date: 2010-03-03 03:02:53 -0600 (Wed, 03 Mar 2010)
New Revision: 12674

Modified:
   django/branches/releases/1.1.X/docs/ref/forms/fields.txt
Log:
[1.1.X] Fixed #12601: Documented the slug field in the forms module. Backport 
of [12673] from trunk.

Modified: django/branches/releases/1.1.X/docs/ref/forms/fields.txt
===
--- django/branches/releases/1.1.X/docs/ref/forms/fields.txt2010-03-03 
09:01:13 UTC (rev 12673)
+++ django/branches/releases/1.1.X/docs/ref/forms/fields.txt2010-03-03 
09:02:53 UTC (rev 12674)
@@ -643,6 +643,21 @@
 ``error_messages`` argument, passing a dictionary with ``'invalid'`` as a key
 and the error message as the value.
 
+``SlugField``
+~
+
+.. class:: SlugField(**kwargs)
+
+   * Default widget: ``TextInput``
+   * Empty value: ``''`` (an empty string)
+   * Normalizes to: A Unicode object.
+   * Validates that the given value contains only letters, numbers and
+ hyphens.
+   * Error messages: ``required``, ``invalid``
+
+This field is intended for use in representing a model
+:class:`~django.db.models.SlugField` in forms.
+
 ``TimeField``
 ~
 

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

[Changeset] r12673 - django/trunk/docs/ref/forms

[noreply]

Author: ubernostrum
Date: 2010-03-03 03:01:13 -0600 (Wed, 03 Mar 2010)
New Revision: 12673

Modified:
   django/trunk/docs/ref/forms/fields.txt
Log:
Fixed #12601: Documented the slug field in the forms module.

Modified: django/trunk/docs/ref/forms/fields.txt
===
--- django/trunk/docs/ref/forms/fields.txt  2010-03-03 08:52:51 UTC (rev 
12672)
+++ django/trunk/docs/ref/forms/fields.txt  2010-03-03 09:01:13 UTC (rev 
12673)
@@ -659,6 +659,21 @@
 ``error_messages`` argument, passing a dictionary with ``'invalid'`` as a key
 and the error message as the value.
 
+``SlugField``
+~
+
+.. class:: SlugField(**kwargs)
+
+   * Default widget: ``TextInput``
+   * Empty value: ``''`` (an empty string)
+   * Normalizes to: A Unicode object.
+   * Validates that the given value contains only letters, numbers and
+ hyphens.
+   * Error messages: ``required``, ``invalid``
+
+This field is intended for use in representing a model
+:class:`~django.db.models.SlugField` in forms.
+
 ``TimeField``
 ~
 

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