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:  new  | Milestone:  1.1 
 Component:  django.contrib.comments  |   Version:  1.0 
Resolution:   |  Keywords:  comments
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by kkubasik):

  * owner:  nobody => kkubasik

Comment:

 I got this foo.

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

Re: [Django] #10680: contrib.comments documentation for customisation does not work

[Django]

#10680: contrib.comments documentation for customisation does not work
--+-
  Reporter:  jakub_vysoky | Owner:  nobody  
Status:  new  | Milestone:  
 Component:  django.contrib.comments  |   Version:  SVN 
Resolution:   |  Keywords:  comments doc
 Stage:  Unreviewed   | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by jakub_vysoky):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django.contrib.comments
  * needs_tests:  => 0
  * needs_docs:  => 0

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

Re: [Django] #10396: Django File Upload /Image Upload Forms are broken with Safari (3 and beta 4)

[Django]

#10396: Django File Upload /Image Upload Forms are broken with Safari (3 and 
beta
4)
---+
  Reporter:  sir...@gmx.de | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by sir...@gmx.de):

 Yes. needs to be done outside of admin. Please see my sample code provided
 above.

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

[Django] #10688: archive_month generic view next_month is incorrect

[Django]

#10688: archive_month generic view next_month is incorrect
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Generic views  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 This isn't an april fools day joke, I promise. However, I did notice this
 due to me testing my site exactly when the month changed.

 django.generic.views.date_based.archive_month isn't consistent with
 "last_day", which makes next_month incorrect.

 last_day is calculated by first_day.replace(month=first_day.month + 1).
 This makes last_day be the *first* day of the next month, not the last
 day. I think that this is necessary because if the queryset is using
 DateTimeField instead of DateField, it won't compare as less than the last
 day of the month, but will compare as less than the first day of the
 second month. I haven't tested that theory, though.

 Anyway, next_month is then computed as last_day + timedelta(1), which is
 the *second* day of the month, not the first. More importantly, if it is
 the first of the month (as it is today), the test "last_day <
 datetime.date.today()" fails, causing next_month to be None when it should
 be valid.

 The fix is quite simple: set next_month to last_day instead of last_day +
 timedelta(1) and change the above test to test less-than-equal instead of
 just less-than. Patch provided. I would also suggest refactoring last_day
 to something more descriptive, though.

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

Re: [Django] #10672: Proxy Model does not send save signal

[Django]

#10672: Proxy Model does not send save signal
---+
  Reporter:  zbyte64   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by k0001):

 * cc: gnuk0...@gmail.com (added)
  * has_patch:  0 => 1
  * stage:  Accepted => Design decision needed

Comment:

 I've attached a patch that fixes this issue. Notice we must carry around
 the value for the "created" argument of the signal: I thought the cleanest
 (and probably useful) way to do this could be to add a return value to
 save_base as the patch shows.


 Thoughts:

 Shouldn't we send both {{{sender=Test1Model}}} and
 {{{sender=TestProxyModel}}} post_save signals in a situation like the one
 on the given example? If we take this approach, in what order should we
 send the signals?

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

Re: [Django] #10685: markdown line breaks with 80-char wrapped text don't make sense with hanging paragraphs i iug ih

[Django]

#10685: markdown line breaks with 80-char wrapped text don't make sense with
hanging paragraphs i iug ih
---+
  Reporter:  aresnick  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Contrib apps  |   Version:  1.0
   
Resolution:  wontfix   |  Keywords:  markdown, template, 
indent, markup
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Replying to [comment:2 Alex]:
 > I'm going to mark this as wontfix, since this is an issue with the
 Python markdown library, and there's nothing Django can do about it.

 There is a Django piece here -- the django.contrib.markup.markdown filter.
 It isn't at all clear to me from the description that this bit of Django
 is what is causing the problem, but I suppose it's conceivable that it
 could be. Or it could be something about how linebreaks and whitespace are
 handled in templates -- it's hard to tell as the description doesn't
 actually illustrate how this paragraph is being fed through Django's
 markdown filter.

 For figuring out which piece is causing the problem, exact details of how
 the markdown filter is being used to format this text would be helpful.
 Also, something that showed how an alternative way of invoking markdown to
 format this file doesn't exhibit the problem.  That seems to be sort of
 implied by the quote regarding markdown syntax, but it doesn't actually
 spell out "Look, here if I do it this other way markdown doesn't put a
 hard linebreak there, why does markdown when called via the Django
 filter?"

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

Re: [Django] #10034: FormWizard has a security_hash check failure with Textareas with leading/trailing newlines in Safari

[Django]

#10034: FormWizard has a security_hash check failure with Textareas with
leading/trailing newlines in Safari
---+
  Reporter:  danaspiegel   | Owner:  kkubasik   
  
Status:  new   | Milestone:  1.1
  
 Component:  django.contrib.formtools  |   Version:  1.0
  
Resolution:|  Keywords:  security_hash 
textarea formwizard
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  1 |  
---+
Changes (by kkubasik):

  * owner:  nobody => kkubasik
  * needs_better_patch:  0 => 1
  * has_patch:  0 => 1

Comment:

 I have no idea if this patch actually fixes it, but it seems like it
 might.

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

Re: [Django] #3512: Add "required" & "error" CSS classes to form rows in as_* methods

[Django]

#3512: Add "required" & "error" CSS classes to form rows in as_* methods
+---
  Reporter:  Waylan Limberg   | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Forms  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  1  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by liangent):

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

Comment:

 i need this

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

[Django] #10687: request parsing breaks if upload_handlers is empty

[Django]

#10687: request parsing breaks if upload_handlers is empty
--+-
 Reporter:  rfk   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  File uploads/storage  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 If request.upload_handlers is empty, attempts to use MultiPartParser will
 fail with "TypeError: 'long' object is not iterable".  This is caused by
 the use of min() to calculate the parser chunk size; if upload_handlers is
 empty then min() is called with a single argument, which it tries to
 interpret as an iterable.

 The attached patch avoids this error and does what I think is the most
 sensible thing - any file uploads get discarded, but other POST variables
 are parsed correctly.  If this is not desired, perhaps its worth checking
 for an empty upload_handlers and providing a better error message?

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

[Django] #10686: 2 simple improvements to permission inheritance.

[Django]

#10686: 2 simple improvements to permission inheritance.
--+-
 Reporter:  faldridge |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:  permissions inheritance   |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 I've got a patch for a slight behavior modification that I needed and that
 might be useful for others, and I wanted to collect some thoughts on it
 before writing up the regression tests and documentation changes.

 Twice now, I've come across a situation where the default Django behavior
 for inheriting permissions is inappropriate for my security model.

 Here's the situation: I have a permission on an abstract base model class
 that I want all child classes to inherit, and I want to then append
 specific permission(s) to one or more of the children.

 Example:
 {{{
 #!python
 class MyAppBaseModel(models.Model):
 class Meta:
 abstract = True
 permissions = (("view_%(class)s", "Can view %(class)s"),)

 class ChildModel(MyAppBaseModel):
 class Meta:
 permissions =  (("foobar_childmodel", "Can foobar childmodel"),)
 }}}

 Two problems arise:
 1.  Although permissions currently may be inherited, the Options class
 does not currently implement %(class)s replacement like the RelatedField
 class does, so my permissions end up actually being stored in the database
 with %(class)s in the name and codename.
 2.  The way Meta attributes are currently processed in the ModelBase
 metaclass causes inherited permissions to be completely replaced if any
 explicit permissions are defined on the child class.  So instead of
 can_view and can_foobar on ChildModel, I only get can_foobar.


 This patch changes Django's behavior such that any explicit child class
 permissions would be appended to the inherited ones, rather than
 completely replacing them.

 Also, I've added a backwards-compatible flag to the Meta options,
 'inherit_permissions'.  This flag would only be required in the case that
 one wanted Django's current behavior which is to discard base class
 permissions when explicit permissions are declared on the child class.

 Example:
 {{{
 #!python
 class MyAppBaseModel(models.Model):
 class Meta:
 abstract = True
 permissions = (("view_%(class)s", "Can view %(class)s"),)

 class ChildModel(MyAppBaseModel):
 class Meta:
 permissions =  (("foobar_childmodel", "Can foobar childmodel"),)
 inherit_permissions = False
 }}}

 This would result in ChildModel only having the can_foobar permission
 (Django's current behavior).  If you wanted to inherit/append the
 view_class
 permission instead (proposed behavior), you could set the attribute to
 True or leave it out entirely.

 This, of course, assumes that my desired behavior is what most other
 people would want.  I suspect, but am not certain that this is the case.

 Though a small change, I believe it requires a design decision.

 Thanks!

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

Re: [Django] #10685: markdown line breaks with 80-char wrapped text don't make sense with hanging paragraphs i iug ih

[Django]

#10685: markdown line breaks with 80-char wrapped text don't make sense with
hanging paragraphs i iug ih
---+
  Reporter:  aresnick  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Contrib apps  |   Version:  1.0
   
Resolution:  wontfix   |  Keywords:  markdown, template, 
indent, markup
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 I'm going to mark this as wontfix, since this is an issue with the Python
 markdown library, and there's nothing Django can do about it.

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

Re: [Django] #10685: markdown line breaks with 80-char wrapped text don't make sense with hanging paragraphs i iug ih

[Django]

#10685: markdown line breaks with 80-char wrapped text don't make sense with
hanging paragraphs i iug ih
---+
  Reporter:  aresnick  | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Contrib apps  |   Version:  1.0
   
Resolution:|  Keywords:  markdown, template, 
indent, markup
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by alec resnick ):

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

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

[Django] #10685: markdown line breaks with 80-char wrapped text don't make sense with hanging paragraphs i iug ih

[Django]

#10685: markdown line breaks with 80-char wrapped text don't make sense with
hanging paragraphs i iug ih
+---
 Reporter:  aresnick|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Contrib apps| Version:  1.0   
 Keywords:  markdown, template, indent, markup  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I use emacs to edit my django templates.  When I use fill-paragraph in
 markdown-mode with a hanging paragraph (say, as an element of a list),
 e.g.:
 {{{
 "

 - *bench space* :: Our [space](http://sproutward.org/greenhouse) and
   [equipment]() are available for use by individuals and groups. If
   you or your friends (or your research partners or your classmates or
   your children) want to figure out a way to make a project of yours
   happen at sprout--[let's see how we can make it
   happen](mailto:spr...@sproutward.org).

 "
 }}}

 The HTML output by the markdown filter in the contrib.markup add-on makes
 the line break hard, so that the link in the first line has an unwanted
 whitespace after it is rendered (since the paragraph emacs was wrapped on
 is longer by the length of the included URIs).  That is, as:
 {{{
 "
 bench space :: Our space and
 equipment are available for use by individuals and groups. If you or your
 friends (or your research partners or your classmates or your children)
 want to figure out a way to make a project of yours happen at sprout—let’s
 see how we can make it happen.
 "

 }}}

 But, if you remove the hanging indent, as:
 {{{
 - *bench space* :: Our [space](http://sproutward.org/greenhouse) and
 [equipment]() are available for use by individuals and groups. If you
 or your friends (or your research partners or your classmates or your
 children) want to figure out a way to make a project of yours happen
 at sprout--[let's see how we can make it
 happen](mailto:spr...@sproutward.org).
 }}}
 then the markdown is rendered as expected, namely:
 {{{
 bench space :: Our space and equipment are available for use by
 individuals and groups. If you or your friends (or your research partners
 or your classmates or your children) want to figure out a way to make a
 project of yours happen at sprout—let’s see how we can make it happen.
 }}}

 This is confusing.  It doesn't seem like the hanging indent should make a
 difference, given that Gruber's syntax for Markdown explicitly
 [http://daringfireball.net/projects/markdown/syntax explicitly says]:
 {{{
 "To make lists look nice, you can wrap items with hanging indents: [...]
 But if you want to be lazy, you don’t have to: [...]"
 }}}

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

Re: [Django] #9005: url templatetag incorrectly assumes settings.SETTINGS_MODULE is not set to None

[Django]

#9005: url templatetag incorrectly assumes settings.SETTINGS_MODULE is not set 
to
None
--+-
  Reporter:  metzen   | Owner:  nobody
Status:  new  | Milestone:  1.1   
 Component:  Template system  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  1 
Needs_better_patch:  0|  
--+-
Changes (by ericholscher):

  * needs_tests:  0 => 1

Comment:

 This code needs to have a test associated with it so that this
 functionality doesn't happen again.

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

Re: [Django] #10670: Using a QuerySet in a filter expression can cause later evaluation of the QuerySet to raise ProgrammingError

[Django]

#10670: Using a QuerySet in a filter expression can cause later evaluation of 
the
QuerySet to raise ProgrammingError
---+
  Reporter:  benanhalt | Owner:  Alex
Status:  assigned  | Milestone:  1.1 
 Component:  Database layer (models, ORM)  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Ready for checkin | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * stage:  Accepted => Ready for checkin

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

Re: [Django] #10156: ModelMultipleChoiceField does O(n) queries where O(1) will suffice

[Django]

#10156: ModelMultipleChoiceField does O(n) queries where O(1) will suffice
+---
  Reporter:  Alex   | Owner:  Alex
Status:  assigned   | Milestone:  1.1 
 Component:  Forms  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * stage:  Accepted => Ready for checkin

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

Re: [Django] #10059: New admin formfield_for_dbfield doesn't play nice with subclassing

[Django]

#10059: New admin formfield_for_dbfield doesn't play nice with subclassing
---+
  Reporter:  Alex  | Owner:  Alex
Status:  new   | Milestone:  1.1 
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Ready for checkin | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * stage:  Accepted => Ready for checkin

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

Re: [Django] #9493: Formsets with data that violates unique constraints across forms are not marked invalid

[Django]

#9493: Formsets with data that violates unique constraints across forms are not
marked invalid
+---
  Reporter:  Alex   | Owner:  Alex
Status:  new| Milestone:  1.1 
 Component:  Forms  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * stage:  Accepted => Ready for checkin

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

[Changeset] r10314 - in django/trunk: django/contrib/admin tests/regressiontests/admin_views

[noreply]

Author: jacob
Date: 2009-03-31 22:11:58 -0500 (Tue, 31 Mar 2009)
New Revision: 10314

Modified:
   django/trunk/django/contrib/admin/options.py
   django/trunk/tests/regressiontests/admin_views/models.py
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed #7510: the ModelAdmin now uses `self.queryset` instead of the default 
manager. Thanks, Alex Gaynor.

Modified: django/trunk/django/contrib/admin/options.py
===
--- django/trunk/django/contrib/admin/options.py2009-04-01 03:02:47 UTC 
(rev 10313)
+++ django/trunk/django/contrib/admin/options.py2009-04-01 03:11:58 UTC 
(rev 10314)
@@ -791,7 +791,7 @@
 opts = model._meta
 
 try:
-obj = model._default_manager.get(pk=unquote(object_id))
+obj = self.queryset(request).get(pk=unquote(object_id))
 except model.DoesNotExist:
 # Don't raise Http404 just yet, because we haven't checked
 # permissions yet. We don't want an unauthenticated user to be able
@@ -976,7 +976,7 @@
 app_label = opts.app_label
 
 try:
-obj = self.model._default_manager.get(pk=unquote(object_id))
+obj = self.queryset(request).get(pk=unquote(object_id))
 except self.model.DoesNotExist:
 # Don't raise Http404 just yet, because we haven't checked
 # permissions yet. We don't want an unauthenticated user to be able

Modified: django/trunk/tests/regressiontests/admin_views/models.py
===
--- django/trunk/tests/regressiontests/admin_views/models.py2009-04-01 
03:02:47 UTC (rev 10313)
+++ django/trunk/tests/regressiontests/admin_views/models.py2009-04-01 
03:11:58 UTC (rev 10314)
@@ -262,6 +262,14 @@
 model = Parent
 inlines = [ChildInline]
 
+class EmptyModel(models.Model):
+def __unicode__(self):
+return "Primary key = %s" % self.id
+
+class EmptyModelAdmin(admin.ModelAdmin):
+def queryset(self, request):
+return super(EmptyModelAdmin, self).queryset(request).filter(pk__gt=1)
+
 admin.site.register(Article, ArticleAdmin)
 admin.site.register(CustomArticle, CustomArticleAdmin)
 admin.site.register(Section, inlines=[ArticleInline])
@@ -274,6 +282,7 @@
 admin.site.register(ExternalSubscriber, ExternalSubscriberAdmin)
 admin.site.register(Podcast, PodcastAdmin)
 admin.site.register(Parent, ParentAdmin)
+admin.site.register(EmptyModel, EmptyModelAdmin)
 
 # We intentionally register Promo and ChapterXtra1 but not Chapter nor 
ChapterXtra2.
 # That way we cover all four cases:

Modified: django/trunk/tests/regressiontests/admin_views/tests.py
===
--- django/trunk/tests/regressiontests/admin_views/tests.py 2009-04-01 
03:02:47 UTC (rev 10313)
+++ django/trunk/tests/regressiontests/admin_views/tests.py 2009-04-01 
03:11:58 UTC (rev 10314)
@@ -13,7 +13,7 @@
 from django.utils.html import escape
 
 # local test models
-from models import Article, CustomArticle, Section, ModelWithStringPrimaryKey, 
Person, Persona, FooAccount, BarAccount, Subscriber, ExternalSubscriber, Podcast
+from models import Article, CustomArticle, Section, ModelWithStringPrimaryKey, 
Person, Persona, FooAccount, BarAccount, Subscriber, ExternalSubscriber, 
Podcast, EmptyModel
 
 try:
 set
@@ -963,3 +963,27 @@
 """
 response = self.client.get('/test_admin/admin/admin_views/parent/add/')
 self.failUnlessEqual(response.status_code, 200)
+
+
+class AdminCustomQuerysetTest(TestCase):
+fixtures = ['admin-views-users.xml']
+
+def setUp(self):
+self.client.login(username='super', password='secret')
+self.pks = [EmptyModel.objects.create().id for i in range(3)]
+
+def test_changelist_view(self):
+response = self.client.get('/test_admin/admin/admin_views/emptymodel/')
+for i in self.pks:
+if i > 1:
+self.assertContains(response, 'Primary key = %s' % i)
+else:
+self.assertNotContains(response, 'Primary key = %s' % i)
+
+def test_change_view(self):
+for i in self.pks:
+response = 
self.client.get('/test_admin/admin/admin_views/emptymodel/%s/' % i)
+if i > 1:
+self.assertEqual(response.status_code, 200)
+else:
+self.assertEqual(response.status_code, 404)


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

[Changeset] r10313 - django/branches/releases/1.0.X/docs/ref

[noreply]

Author: jacob
Date: 2009-03-31 22:02:47 -0500 (Tue, 31 Mar 2009)
New Revision: 10313

Modified:
   django/branches/releases/1.0.X/docs/ref/databases.txt
Log:
[1.0.X] Fixed a couple of mistaken bits of the docs in [10312]

Modified: django/branches/releases/1.0.X/docs/ref/databases.txt
===
--- django/branches/releases/1.0.X/docs/ref/databases.txt   2009-04-01 
02:37:04 UTC (rev 10312)
+++ django/branches/releases/1.0.X/docs/ref/databases.txt   2009-04-01 
03:02:47 UTC (rev 10313)
@@ -18,19 +18,6 @@
 PostgreSQL notes
 
 
-PostgreSQL 8.2 to 8.2.4

-
-The implementation of the population statistics aggregates ``STDDEV_POP`` and
-``VAR_POP`` that shipped with PostgreSQL 8.2 to 8.2.4 are `known to be
-faulty`_. Users of these releases of PostgreSQL are advised to upgrade to
-`Release 8.2.5`_ or later. Django will raise a ``NotImplementedError`` if you
-attempt to use the ``StdDev(sample=False)`` or ``Variance(sample=False)``
-aggregate with a database backend that falls within the affected release range.
-
-.. _known to be faulty: 
http://archives.postgresql.org/pgsql-bugs/2007-07/msg00046.php
-.. _Release 8.2.5: 
http://developer.postgresql.org/pgdocs/postgres/release-8-2-5.html
-
 Transaction handling
 -
 
@@ -313,16 +300,11 @@
 SQLite 3.3.6 or newer strongly recommended
 --
 
-Versions of SQLite 3.3.5 and older contains the following bugs:
+Versions of SQLite 3.3.5 and older contains a bug when `handling`_ ``ORDER BY``
+parameters. This can cause problems when you use the ``select`` parameter for
+the ``extra()`` QuerySet method. The bug can be identified by the error message
+``OperationalError: ORDER BY terms must not be non-integer constants``.
 
- * A bug when `handling`_ ``ORDER BY`` parameters. This can cause problems when
-   you use the ``select`` parameter for the ``extra()`` QuerySet method. The 
bug
-   can be identified by the error message ``OperationalError: ORDER BY terms
-   must not be non-integer constants``.
-
- * A bug when handling `aggregation`_ together with DateFields and
-   DecimalFields.
-
 .. _handling: http://www.sqlite.org/cvstrac/tktview?tn=1768
 .. _aggregation: http://code.djangoproject.com/ticket/10031
 
@@ -334,12 +316,6 @@
 SQLite (e.g. the official binary distribution of Python 2.5 for Windows, 2.5.4
 as of this writing, includes SQLite 3.3.4).
 
-As described :ref:`below`, this can be solved
-by downloading and installing a newer version of ``pysqlite2``
-(``pysqlite-2.x.x.win32-py2.5.exe`` in the described case) that includes and
-uses a newer version of SQLite. Python 2.6 for Windows ships with a version of
-SQLite that is not affected by these issues.
-
 Version 3.5.9
 -
 
@@ -369,21 +345,6 @@
 3.6.3 (released September 22, 2008) or later, or downgrade to an earlier
 version of SQLite.
 
-.. _using-newer-versions-of-pysqlite:
-
-Using newer versions of the SQLite DB-API 2.0 driver
-
-
-.. versionadded:: 1.1
-
-For versions of Python 2.5 or newer that include ``sqlite3`` in the standard
-library Django will now use a ``pysqlite2`` interface in preference to
-``sqlite3`` if it finds one is available.
-
-This provides the ability to upgrade both the DB-API 2.0 interface or SQLite 3
-itself to versions newer than the ones included with your particular Python
-binary distribution, if needed.
-
 .. _oracle-notes:
 
 Oracle notes


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

[Changeset] r10312 - in django/branches/releases/1.0.X: . docs/ref docs/topics

[noreply]

Author: jacob
Date: 2009-03-31 21:37:04 -0500 (Tue, 31 Mar 2009)
New Revision: 10312

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/ref/databases.txt
   django/branches/releases/1.0.X/docs/topics/install.txt
Log:
[1.0.X] Fixed #10031: updated SQLite database docs to more strongly indicate 
the problems with versions before 3.3.6. Thanks, ramiro. Backport of r10311 
from trunk.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283,10303-10304,10309
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283,10303-10304,10309,10311

Modified: django/branches/releases/1.0.X/docs/ref/databases.txt
===
--- django/branches/releases/1.0.X/docs/ref/databases.txt   2009-04-01 
01:36:44 UTC (rev 10311)
+++ django/branches/releases/1.0.X/docs/ref/databases.txt   2009-04-01 
02:37:04 UTC (rev 10312)
@@ -13,6 +13,33 @@
 usage. Of course, it is not intended as a replacement for server-specific
 documentation or reference manuals.
 
+.. _postgresql-notes:
+
+PostgreSQL notes
+
+
+PostgreSQL 8.2 to 8.2.4
+---
+
+The implementation of the population statistics aggregates ``STDDEV_POP`` and
+``VAR_POP`` that shipped with PostgreSQL 8.2 to 8.2.4 are `known to be
+faulty`_. Users of these releases of PostgreSQL are advised to upgrade to
+`Release 8.2.5`_ or later. Django will raise a ``NotImplementedError`` if you
+attempt to use the ``StdDev(sample=False)`` or ``Variance(sample=False)``
+aggregate with a database backend that falls within the affected release range.
+
+.. _known to be faulty: 
http://archives.postgresql.org/pgsql-bugs/2007-07/msg00046.php
+.. _Release 8.2.5: 
http://developer.postgresql.org/pgdocs/postgres/release-8-2-5.html
+
+Transaction handling
+-
+
+:ref:`By default `, Django starts a transaction when a
+database connection is first used and commits the result at the end of the
+request/response handling. The PostgreSQL backends normally operate the same
+as any other Django backend in this respect.
+
+
 .. _mysql-notes:
 
 MySQL notes
@@ -163,7 +190,7 @@
 Connecting to the database
 --
 
-Refer to the :ref:`settings documentation `. 
+Refer to the :ref:`settings documentation `.
 
 Connection settings are used in this order:
 
@@ -183,7 +210,7 @@
   DATABASE_ENGINE = "mysql"
   DATABASE_OPTIONS = {
   'read_default_file': '/path/to/my.cnf',
-  }
+  }
 
   # my.cnf
   [client]
@@ -221,9 +248,7 @@
   creating your tables::
 
   DATABASE_OPTIONS = {
-  # ...
  "init_command": "SET storage_engine=INNODB",
-  # ...
   }
 
   This sets the default storage engine 

Re: [Django] #8999: ModelAdmin.get_form and get_formset will overwrite self.exclude with a kwargs exclude

[Django]

#8999: ModelAdmin.get_form and get_formset will overwrite self.exclude with a
kwargs exclude
---+
  Reporter:  seanl | Owner:  jkocherhans
Status:  assigned  | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by jkocherhans):

 Yeah, the apparent intention of the existing code is the wrong thing to do
 IMO. Just look at what a subtle bug it produced! ;)

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

Re: [Django] #10593: Brazilian portuguese translation of POT files for 1.1

[Django]

#10593: Brazilian portuguese translation of POT files for 1.1
--+-
  Reporter:  Guilherme Gondim   | Owner:  
nobody
Status:  new  | Milestone:  
1.1   
 Component:  Translations |   Version:  
SVN   
Resolution:   |  Keywords:  
pt_BR 
 Stage:  Accepted | Has_patch:  
1 
Needs_docs:  0|   Needs_tests:  
0 
Needs_better_patch:  0|  
--+-
Changes (by Guilherme Gondim ):

  * has_patch:  0 => 1

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

Re: [Django] #8999: ModelAdmin.get_form and get_formset will overwrite self.exclude with a kwargs exclude

[Django]

#8999: ModelAdmin.get_form and get_formset will overwrite self.exclude with a
kwargs exclude
---+
  Reporter:  seanl | Owner:  jkocherhans
Status:  assigned  | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by seanl):

 OK, that also makes sense as behaviour, but the current code looks like it
 intends to combine the values, but due to a subtlety kwargs takes
 precedence. (that the 'exclude' kwarg if present is left in the kwargs
 dict, and thus overrides when you come to defaults.update(kwargs) ). If
 the current behaviour is what is intended, then the whole 'excludes' line
 in the defaults dictionary literal should be removed, and the behaviour
 will be the same, but with the code reflecting the intent.

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

[Changeset] r10311 - in django/trunk/docs: ref topics

[noreply]

Author: jacob
Date: 2009-03-31 20:36:44 -0500 (Tue, 31 Mar 2009)
New Revision: 10311

Modified:
   django/trunk/docs/ref/databases.txt
   django/trunk/docs/topics/install.txt
Log:
Fixed #10031: updated SQLite database docs to more strongly indicate the 
problems with versions before 3.3.6. Thanks, ramiro.

Modified: django/trunk/docs/ref/databases.txt
===
--- django/trunk/docs/ref/databases.txt 2009-04-01 01:34:49 UTC (rev 10310)
+++ django/trunk/docs/ref/databases.txt 2009-04-01 01:36:44 UTC (rev 10311)
@@ -351,44 +351,44 @@
 
 .. _documented at sqlite.org: http://www.sqlite.org/faq.html#q18
 
-Versions prior to 3.3.6
-
+SQLite 3.3.6 or newer strongly recommended
+--
 
-Versions of SQLite 3.3.5 and older `contain a bug`_ when handling ``ORDER BY``
-parameters. This can cause problems when you use the ``select`` parameter for
-the ``extra()`` QuerySet method. The bug can be identified by the error message
-``OperationalError: ORDER BY terms must not be non-integer constants``. The
-problem can be solved updating SQLite to version 3.3.6 or newer, possibly also
-updating the ``pysqlite2`` Python module in the process.
+Versions of SQLite 3.3.5 and older contains the following bugs:
 
-.. _contain a bug: http://www.sqlite.org/cvstrac/tktview?tn=1768
+ * A bug when `handling`_ ``ORDER BY`` parameters. This can cause problems when
+   you use the ``select`` parameter for the ``extra()`` QuerySet method. The 
bug
+   can be identified by the error message ``OperationalError: ORDER BY terms
+   must not be non-integer constants``.
 
-This has a very low impact because 3.3.6 was released in April 2006, so most
-current binary distributions for different platforms include newer version of
-SQLite usable from Python through either the ``pysqlite2`` or the ``sqlite3``
-modules.
+ * A bug when handling `aggregation`_ together with DateFields and
+   DecimalFields.
 
-However, in the case of Windows, the official binary distribution of the stable
-release of Python 2.5 (2.5.2, as of this writing) includes SQLite 3.3.4, so 
the bug can
-make itself evident in that platform. There are (as of Django 1.0) even three
-tests in the Django test suite that will fail when run under this setup.  As
-described above, this can be solved by downloading and installing a newer
-version of ``pysqlite2`` (``pysqlite-2.x.x.win32-py2.5.exe``) that includes and
-uses a newer version of SQLite. Python 2.6 ships with a newer version of
-SQLite and is not affected by this issue.
+.. _handling: http://www.sqlite.org/cvstrac/tktview?tn=1768
+.. _aggregation: http://code.djangoproject.com/ticket/10031
 
-If you are on such a platform and find yourself needing to update
-``pysqlite``/SQLite, you will also need to manually modify the
-``django/db/backends/sqlite3/base.py`` file in the Django source tree so it
-attempts to import ``pysqlite2`` before ``sqlite3`` and so it can take
-advantage of the new ``pysqlite2``/SQLite versions.
+SQLite 3.3.6 was released in April 2006, so most current binary distributions
+for different platforms include newer version of SQLite usable from Python
+through either the ``pysqlite2`` or the ``sqlite3`` modules.
 
+However, some platform/Python version combinations include older versions of
+SQLite (e.g. the official binary distribution of Python 2.5 for Windows, 2.5.4
+as of this writing, includes SQLite 3.3.4). There are (as of Django 1.1) even
+some tests in the Django test suite that will fail when run under this setup.
+
+As described :ref:`below`, this can be solved
+by downloading and installing a newer version of ``pysqlite2``
+(``pysqlite-2.x.x.win32-py2.5.exe`` in the described case) that includes and
+uses a newer version of SQLite. Python 2.6 for Windows ships with a version of
+SQLite that is not affected by these issues.
+
 Version 3.5.9
 -
 
-The Ubuntu "Intrepid Ibex" SQLite 3.5.9-3 package contains a bug that causes
-problems with the evaluation of query expressions. If you are using Ubuntu
-"Intrepid Ibex", you will need to find an alternate source for SQLite
+The Ubuntu "Intrepid Ibex" (8.10) SQLite 3.5.9-3 package contains a bug that
+causes problems with the evaluation of query expressions. If you are using
+Ubuntu "Intrepid Ibex", you will need to update the package to version
+3.5.9-3ubuntu1 or newer (recommended) or find an alternate source for SQLite
 packages, or install SQLite from source.
 
 At one time, Debian Lenny shipped with the same malfunctioning SQLite 3.5.9-3
@@ -411,6 +411,21 @@
 3.6.3 (released September 22, 2008) or later, or downgrade to an earlier
 version of SQLite.
 
+.. _using-newer-versions-of-pysqlite:
+
+Using newer versions of the SQLite DB-API 2.0 driver
+
+
+.. versionadded:: 1.1
+
+For versions of Python 2.5 or newer that include ``sqlite3`` in the standard
+library Django 

[Changeset] r10310 - in django/branches/releases/1.0.X: . docs/ref/contrib

[noreply]

Author: jkocherhans
Date: 2009-03-31 20:34:49 -0500 (Tue, 31 Mar 2009)
New Revision: 10310

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/ref/contrib/admin.txt
Log:
[1.0.x] Fixed #9452. InlineModelAdmin docs now mention the right default for 
'form'. Backport of r10309 from trunk. Forgot to thank patrickk. Sorry about 
that.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283,10303-10304
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283,10303-10304,10309

Modified: django/branches/releases/1.0.X/docs/ref/contrib/admin.txt
===
--- django/branches/releases/1.0.X/docs/ref/contrib/admin.txt   2009-04-01 
01:29:30 UTC (rev 10309)
+++ django/branches/releases/1.0.X/docs/ref/contrib/admin.txt   2009-04-01 
01:34:49 UTC (rev 10310)
@@ -733,7 +733,7 @@
 ``form``
 
 
-The value for ``form`` is inherited from ``ModelAdmin``. This is what is
+The value for ``form`` defaults to ``BaseModelForm``. This is what is
 passed through to ``formset_factory`` when creating the formset for this
 inline.
 


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

[Changeset] r10309 - django/trunk/docs/ref/contrib/admin

[noreply]

Author: jkocherhans
Date: 2009-03-31 20:29:30 -0500 (Tue, 31 Mar 2009)
New Revision: 10309

Modified:
   django/trunk/docs/ref/contrib/admin/index.txt
Log:
Fixed #9452. InlineModelAdmin docs now mention the right default for 'form'.

Modified: django/trunk/docs/ref/contrib/admin/index.txt
===
--- django/trunk/docs/ref/contrib/admin/index.txt   2009-04-01 00:10:40 UTC 
(rev 10308)
+++ django/trunk/docs/ref/contrib/admin/index.txt   2009-04-01 01:29:30 UTC 
(rev 10309)
@@ -887,7 +887,7 @@
 ``form``
 
 
-The value for ``form`` is inherited from ``ModelAdmin``. This is what is
+The value for ``form`` defaults to ``BaseModelForm``. This is what is
 passed through to ``formset_factory`` when creating the formset for this
 inline.
 


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

Re: [Django] #10396: Django File Upload /Image Upload Forms are broken with Safari (3 and beta 4)

[Django]

#10396: Django File Upload /Image Upload Forms are broken with Safari (3 and 
beta
4)
---+
  Reporter:  sir...@gmx.de | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  File uploads/storage  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kkubasik):

 Hmmm... I cannot replicate in admin, or does it need to be done outside of
 that?

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

[Changeset] r10308 - django/branches/releases/1.0.X

[noreply]

Author: jacob
Date: 2009-03-31 19:10:40 -0500 (Tue, 31 Mar 2009)
New Revision: 10308

Modified:
   django/branches/releases/1.0.X/
Log:
Marked r10303-10304 as applied to 1.0.X.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283,10303-10304


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

[Changeset] r10307 - django/branches/releases/1.0.X/docs/ref

[noreply]

Author: jacob
Date: 2009-03-31 19:08:48 -0500 (Tue, 31 Mar 2009)
New Revision: 10307

Modified:
   django/branches/releases/1.0.X/docs/ref/databases.txt
Log:
[1.0.X] Fixed a silly typo in databases ref. Thanks, Alex. Backport of r10304 
from trunk.

Modified: django/branches/releases/1.0.X/docs/ref/databases.txt
===
--- django/branches/releases/1.0.X/docs/ref/databases.txt   2009-04-01 
00:08:34 UTC (rev 10306)
+++ django/branches/releases/1.0.X/docs/ref/databases.txt   2009-04-01 
00:08:48 UTC (rev 10307)
@@ -18,10 +18,10 @@
 MySQL notes
 ===
 
-Django expects the database to support transactions, referential integrity,
-and Unicode support (UTF-8 encoding). Fortunately, MySQL_ has all these
-features as available as far back as 3.23. While it may be possible to use
-3.23 or 4.0, you'll probably have less trouble if you use 4.1 or 5.0.
+Django expects the database to support transactions, referential integrity, and
+Unicode (UTF-8 encoding). Fortunately, MySQL_ has all these features as
+available as far back as 3.23. While it may be possible to use 3.23 or 4.0,
+you'll probably have less trouble if you use 4.1 or 5.0.
 
 MySQL 4.1
 -


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

[Changeset] r10306 - in django/branches/releases/1.0.X: . docs docs/faq docs/howto docs/howto/deployment docs/intro docs/ref docs/ref/contrib docs/ref/contrib/comments docs/ref/contrib/formtools docs/

[noreply]

Author: jacob
Date: 2009-03-31 19:08:34 -0500 (Tue, 31 Mar 2009)
New Revision: 10306

Modified:
   django/branches/releases/1.0.X/AUTHORS
   django/branches/releases/1.0.X/docs/conf.py
   django/branches/releases/1.0.X/docs/faq/usage.txt
   django/branches/releases/1.0.X/docs/glossary.txt
   django/branches/releases/1.0.X/docs/howto/deployment/fastcgi.txt
   django/branches/releases/1.0.X/docs/howto/deployment/index.txt
   django/branches/releases/1.0.X/docs/howto/deployment/modpython.txt
   django/branches/releases/1.0.X/docs/howto/static-files.txt
   django/branches/releases/1.0.X/docs/intro/tutorial03.txt
   django/branches/releases/1.0.X/docs/ref/contrib/admin.txt
   django/branches/releases/1.0.X/docs/ref/contrib/comments/index.txt
   django/branches/releases/1.0.X/docs/ref/contrib/contenttypes.txt
   django/branches/releases/1.0.X/docs/ref/contrib/formtools/form-wizard.txt
   django/branches/releases/1.0.X/docs/ref/databases.txt
   django/branches/releases/1.0.X/docs/ref/django-admin.txt
   django/branches/releases/1.0.X/docs/ref/forms/fields.txt
   django/branches/releases/1.0.X/docs/ref/models/fields.txt
   django/branches/releases/1.0.X/docs/ref/models/querysets.txt
   django/branches/releases/1.0.X/docs/ref/models/relations.txt
   django/branches/releases/1.0.X/docs/ref/signals.txt
   django/branches/releases/1.0.X/docs/topics/auth.txt
   django/branches/releases/1.0.X/docs/topics/http/shortcuts.txt
   django/branches/releases/1.0.X/docs/topics/http/urls.txt
   django/branches/releases/1.0.X/docs/topics/testing.txt
Log:
[1.0.X] A whole lotta documentation fixes, backported from r10303 on trunk.

I got my commit message cut off the first try, but luckily I get to still thank 
Kevin Kubasik for rolling all these fixes up into a single easy patch.

Modified: django/branches/releases/1.0.X/AUTHORS
===
--- django/branches/releases/1.0.X/AUTHORS  2009-03-31 23:54:13 UTC (rev 
10305)
+++ django/branches/releases/1.0.X/AUTHORS  2009-04-01 00:08:34 UTC (rev 
10306)
@@ -233,6 +233,7 @@
 kon...@gwu.edu
 knox 
 David Krauth
+Kevin Kubasik 
 kurt...@meetro.com
 Denis Kuzmichyov 
 Panos Laganakos 

Modified: django/branches/releases/1.0.X/docs/conf.py
===
--- django/branches/releases/1.0.X/docs/conf.py 2009-03-31 23:54:13 UTC (rev 
10305)
+++ django/branches/releases/1.0.X/docs/conf.py 2009-04-01 00:08:34 UTC (rev 
10306)
@@ -68,6 +68,11 @@
 # The name of the Pygments (syntax highlighting) style to use.
 pygments_style = 'trac'
 
+# Sphinx will recurse into subversion configuration folders and try to read  
+# any document file within. These should be ignored. 
+# Note: exclude_dirnames is new in Sphinx 0.5 
+exclude_dirnames = ['.svn']
+
 # Options for HTML output
 # ---
 

Modified: django/branches/releases/1.0.X/docs/faq/usage.txt
===
--- django/branches/releases/1.0.X/docs/faq/usage.txt   2009-03-31 23:54:13 UTC 
(rev 10305)
+++ django/branches/releases/1.0.X/docs/faq/usage.txt   2009-04-01 00:08:34 UTC 
(rev 10306)
@@ -67,3 +67,13 @@
Django. For example, if your :class:`~django.db.models.ImageField` is
called ``mug_shot``, you can get the absolute URL to your image in a
template with ``{{ object.mug_shot.url }}``.
+
+How do I make a variable available to all my templates?
+---
+
+Sometimes your templates just all need the same thing. A common example would
+be dynamically-generated menus. At first glance, it seems logical to simply
+add a common dictionary to the template context.
+
+The correct solution is to use a ``RequestContext``. Details on how to do this
+are here: :ref:`subclassing-context-requestcontext`.

Modified: django/branches/releases/1.0.X/docs/glossary.txt
===
--- django/branches/releases/1.0.X/docs/glossary.txt2009-03-31 23:54:13 UTC 
(rev 10305)
+++ django/branches/releases/1.0.X/docs/glossary.txt2009-04-01 00:08:34 UTC 
(rev 10306)
@@ -13,8 +13,8 @@
 See :ref:`topics-db-models`.
 
 generic view
-A higher-order :term:`view` function that abstracts common idioms and 
patterns
-found in view development and abstracts them.
+A higher-order :term:`view` function that provides an abstract/generic
+implementation of a common idiom or pattern found in view development.
 
 See :ref:`ref-generic-views`.
 
@@ -71,8 +71,9 @@
 the last bit (``spring``) is the slug.
 
 template
-A chunk of text that separates the presentation of a document from its
-data.
+A chunk of text that acts as formatting for representing data. A
+  

Re: [Django] #10359: Feed class reference contains false info

[Django]

#10359: Feed class reference contains false info
+---
  Reporter:  minder | Owner:  nobody
Status:  reopened   | Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

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

[Changeset] r10305 - in django/branches/releases/1.0.X: . docs/topics

[noreply]

Author: jacob
Date: 2009-03-31 18:54:13 -0500 (Tue, 31 Mar 2009)
New Revision: 10305

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/topics/cache.txt
Log:
Made a bunch of edits to docs/topics/cache.txt, mostly based on stuff from the 
Django Book. Backport of [10055] from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283

Modified: django/branches/releases/1.0.X/docs/topics/cache.txt
===
--- django/branches/releases/1.0.X/docs/topics/cache.txt2009-03-31 
23:46:37 UTC (rev 10304)
+++ django/branches/releases/1.0.X/docs/topics/cache.txt2009-03-31 
23:54:13 UTC (rev 10305)
@@ -50,7 +50,7 @@
 performance; yes, some cache types are faster than others.
 
 Your cache preference goes in the ``CACHE_BACKEND`` setting in your settings
-file. Here's an explanation of all available values for CACHE_BACKEND.
+file. Here's an explanation of all available values for ``CACHE_BACKEND``.
 
 Memcached
 -
@@ -58,18 +58,18 @@
 By far the fastest, most efficient type of cache available to Django, Memcached
 is an entirely memory-based cache framework originally developed to handle high
 loads at LiveJournal.com and subsequently open-sourced by Danga Interactive.
-It's used by sites such as Slashdot and Wikipedia to reduce database access and
+It's used by sites such as Facebook and Wikipedia to reduce database access and
 dramatically increase site performance.
 
 Memcached is available for free at http://danga.com/memcached/ . It runs as a
 daemon and is allotted a specified amount of RAM. All it does is provide an
-interface -- a *lightning-fast* interface -- for adding, retrieving and
-deleting arbitrary data in the cache. All data is stored directly in memory,
-so there's no overhead of database or filesystem usage.
+fast interface for adding, retrieving and deleting arbitrary data in the cache.
+All data is stored directly in memory, so there's no overhead of database or
+filesystem usage.
 
 After installing Memcached itself, you'll need to install the Memcached Python
-bindings. Two versions of this are available. Choose and install *one* of the
-following modules:
+bindings, which are not bundled with Django directly. Two versions of this are
+available. Choose and install *one* of the following modules:
 
 * The fastest available option is a module called ``cmemcache``, available
   at http://gijsbert.org/cmemcache/ .
@@ -93,19 +93,29 @@
 CACHE_BACKEND = 'memcached://127.0.0.1:11211/'
 
 One excellent feature of Memcached is its ability to share cache over multiple
-servers. To take advantage of this feature, include 

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

[noreply]

Author: jacob
Date: 2009-03-31 18:46:37 -0500 (Tue, 31 Mar 2009)
New Revision: 10304

Modified:
   django/trunk/docs/ref/databases.txt
Log:
Fixed a silly typo in databases ref. Thanks, Alex.

Modified: django/trunk/docs/ref/databases.txt
===
--- django/trunk/docs/ref/databases.txt 2009-03-31 23:34:03 UTC (rev 10303)
+++ django/trunk/docs/ref/databases.txt 2009-03-31 23:46:37 UTC (rev 10304)
@@ -86,10 +86,10 @@
 MySQL notes
 ===
 
-Django expects the database to support transactions, referential integrity,
-and Unicode support (UTF-8 encoding). Fortunately, MySQL_ has all these
-features as available as far back as 3.23. While it may be possible to use
-3.23 or 4.0, you'll probably have less trouble if you use 4.1 or 5.0.
+Django expects the database to support transactions, referential integrity, and
+Unicode (UTF-8 encoding). Fortunately, MySQL_ has all these features as
+available as far back as 3.23. While it may be possible to use 3.23 or 4.0,
+you'll probably have less trouble if you use 4.1 or 5.0.
 
 MySQL 4.1
 -


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

Re: [Django] #9061: formsets with can_delete=True shouldn't add delete field to extra forms

[Django]

#9061: formsets with can_delete=True shouldn't add delete field to extra forms
---+
  Reporter:  gsf   | Owner:  nobody
Status:  closed| Milestone:
 Component:  Forms |   Version:  SVN   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by jkocherhans):

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

Comment:

 I don't think this is the case on trunk anymore. I don't see delete
 checkboxes for "add" forms.

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

Re: [Django] #8160: ModelFormset ignores form properties

[Django]

#8160: ModelFormset ignores form properties
+---
  Reporter:  andrew.mcmu...@ifi.uio.no  | Owner:  jkocherhans
Status:  assigned   | Milestone: 
 Component:  Forms  |   Version:  SVN
Resolution: |  Keywords:  formset
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  1  
Needs_better_patch:  0  |  
+---
Changes (by jkocherhans):

  * owner:  justinf => jkocherhans
  * status:  new => assigned

Comment:

 Taking this on with a few other related issues.

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

Re: [Django] #8999: ModelAdmin.get_form and get_formset will overwrite self.exclude with a kwargs exclude

[Django]

#8999: ModelAdmin.get_form and get_formset will overwrite self.exclude with a
kwargs exclude
---+
  Reporter:  seanl | Owner:  jkocherhans
Status:  assigned  | Milestone: 
 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 jkocherhans):

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

Comment:

 I don't think we should be combining anything here. If someone passes
 {{{exclude}}} to {{{get_form}}}, that value should override
 {{{self.exclude}}}. If someone wants different behavior, they can override
 the {{{get_form}}} method. I need to think about this a bit more in the
 context of a few other related issues though.

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

Re: [Django] #10056: Problem with non-ASCII characters in FilePathField in contrib.admin

[Django]

#10056: Problem with non-ASCII characters in FilePathField in contrib.admin
+---
  Reporter:  andrew.mcmu...@ifi.uio.no  | Owner:  nobody
Status:  closed | Milestone:  1.1   
 Component:  django.contrib.admin   |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kkubasik):

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

Comment:

 We don't want to be limiting the possible files to select, if you want,
 FilePathField takes a regex to determine which files should be displayed,
 so you could hide the non-ascii files. Or, if you want to allow them, you
 could subclass the Form's clean() method and change the validation rules.
 Overall, the opinion appears to be that we can't allow filenames that
 filesystems don't support, and we don't want to limit which files you see
 in the dropdown (by default).

 I'm going to close this, but feel free to reopen if I'm super-wrong or
 totally off-base.

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

Re: [Django] #10445: Custom comment form example doesn't show submit button

[Django]

#10445: Custom comment form example doesn't show submit button
+---
  Reporter:  nab| Owner:  kkubasik   
Status:  closed | Milestone:  1.1
 Component:  Documentation  |   Version:  1.0
Resolution:  fixed  |  Keywords:  kkmegapatch
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  1  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #10207: Simple enhancements for Queryset API: Search

[Django]

#10207: Simple enhancements for Queryset API: Search
-+--
  Reporter:  Seamus   | Owner:  
kkubasik   
Status:  closed  | Milestone:  1.1  
  
 Component:  Documentation   |   Version:  1.0  
  
Resolution:  fixed   |  Keywords:  
kkmegapatch
 Stage:  Accepted| Has_patch:  1
  
Needs_docs:  0   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #10416: Add reference to the Cherokee Web Server in the documention

[Django]

#10416: Add reference to the Cherokee Web Server in the documention
+---
  Reporter:  stephaner  | Owner:  kkubasik   
Status:  closed | Milestone:  1.1
 Component:  Documentation  |   Version:  SVN
Resolution:  fixed  |  Keywords:  kkmegapatch
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #10394: AdminSite.urls should replace AdminSite.root in the documentation

[Django]

#10394: AdminSite.urls should replace AdminSite.root in the documentation
+---
  Reporter:  whiskybar  | Owner:  kkubasik   
Status:  closed | Milestone:  1.1
 Component:  Documentation  |   Version:  SVN
Resolution:  fixed  |  Keywords:  kkmegapatch
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #10213: Static Files doc improvement

[Django]

#10213: Static Files doc improvement
+---
  Reporter:  preds  | Owner:  kkubasik  
Status:  closed | Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution:  fixed  |  Keywords:  pycamp2009 kkmegapatch
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #10138: Documentation should mention that loaddata does not call custom save or pre_save signals

[Django]

#10138: Documentation should mention that loaddata does not call custom save or
pre_save signals
+---
  Reporter:  varikin| Owner:  kkubasik   
Status:  closed | Milestone:  1.1
 Component:  Documentation  |   Version:  SVN
Resolution:  fixed  |  Keywords:  kkmegapatch
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #10116: Documentation about serving media files should mention Nginx

[Django]

#10116: Documentation about serving media files should mention Nginx
+---
  Reporter:  Uninen | Owner:  kkubasik  

Status:  closed | Milestone:  1.1   

 Component:  Documentation  |   Version:  SVN   

Resolution:  fixed  |  Keywords:  media, docs, nginx 
kkmegapatch
 Stage:  Accepted   | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

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

Comment:

 Fixed by [10303].

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

Re: [Django] #9987: get_profile documentation: Autocreate by signal

[Django]

#9987: get_profile documentation: Autocreate by signal
+---
  Reporter:  guettli| Owner:  kkubasik  
Status:  closed | Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution:  fixed  |  Keywords:  profile signal kkmegapatch
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303];

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

Re: [Django] #10111: InlineModelAdmin documentation is confusing

[Django]

#10111: InlineModelAdmin documentation is confusing
+---
  Reporter:  medhat | Owner:  kkubasik   
Status:  closed | Milestone:  1.1
 Component:  Documentation  |   Version:  1.0
Resolution:  fixed  |  Keywords:  kkmegapatch
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303].

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

Re: [Django] #9766: Improving "template" and "generic view" definitions in glossary.txt

[Django]

#9766: Improving "template" and "generic view" definitions in glossary.txt
--+-
  Reporter:  Horst Gutmann   | Owner:  
kkubasik
Status:  closed   | Milestone:  1.1 

 Component:  Documentation|   Version:  1.0 

Resolution:  fixed|  Keywords:  
glossary kkmegapatch
 Stage:  Accepted | Has_patch:  1   

Needs_docs:  0|   Needs_tests:  0   

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

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

Comment:

 Fixed by [10303].

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

Re: [Django] #9635: Better documentation for render_to_response

[Django]

#9635: Better documentation for render_to_response
+---
  Reporter:  zgoda  | Owner:  kkubasik 
Status:  closed | Milestone:  1.1  
 Component:  Documentation  |   Version:  SVN  
Resolution:  fixed  |  Keywords:  shortcuts kkmegapatch
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by jacob):

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

Comment:

 Fixed by [10303]; not sure what happened to my commit message.

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

[Changeset] r10303 - in django/trunk: . docs docs/faq docs/howto docs/howto/deployment docs/intro docs/ref docs/ref/contrib docs/ref/contrib/admin docs/ref/contrib/comments docs/ref/contrib/formtools

[noreply]

Author: jacob
Date: 2009-03-31 18:34:03 -0500 (Tue, 31 Mar 2009)
New Revision: 10303

Modified:
   django/trunk/AUTHORS
   django/trunk/docs/conf.py
   django/trunk/docs/faq/usage.txt
   django/trunk/docs/glossary.txt
   django/trunk/docs/howto/deployment/fastcgi.txt
   django/trunk/docs/howto/deployment/index.txt
   django/trunk/docs/howto/deployment/modpython.txt
   django/trunk/docs/howto/static-files.txt
   django/trunk/docs/intro/tutorial03.txt
   django/trunk/docs/ref/contrib/admin/index.txt
   django/trunk/docs/ref/contrib/comments/index.txt
   django/trunk/docs/ref/contrib/contenttypes.txt
   django/trunk/docs/ref/contrib/formtools/form-wizard.txt
   django/trunk/docs/ref/databases.txt
   django/trunk/docs/ref/django-admin.txt
   django/trunk/docs/ref/forms/fields.txt
   django/trunk/docs/ref/models/fields.txt
   django/trunk/docs/ref/models/querysets.txt
   django/trunk/docs/ref/models/relations.txt
   django/trunk/docs/ref/signals.txt
   django/trunk/docs/topics/auth.txt
   django/trunk/docs/topics/http/shortcuts.txt
   django/trunk/docs/topics/http/urls.txt
   django/trunk/docs/topics/testing.txt
Log:
A whole lotta documentation fixes: Fixes #8704, #8826, #8980, #9243, #9343, 
#9529,

Modified: django/trunk/AUTHORS
===
--- django/trunk/AUTHORS2009-03-31 22:41:43 UTC (rev 10302)
+++ django/trunk/AUTHORS2009-03-31 23:34:03 UTC (rev 10303)
@@ -242,6 +242,7 @@
 kon...@gwu.edu
 knox 
 David Krauth
+Kevin Kubasik 
 kurt...@meetro.com
 Denis Kuzmichyov 
 Panos Laganakos 

Modified: django/trunk/docs/conf.py
===
--- django/trunk/docs/conf.py   2009-03-31 22:41:43 UTC (rev 10302)
+++ django/trunk/docs/conf.py   2009-03-31 23:34:03 UTC (rev 10303)
@@ -70,6 +70,11 @@
 # The name of the Pygments (syntax highlighting) style to use.
 pygments_style = 'trac'
 
+# Sphinx will recurse into subversion configuration folders and try to read  
+# any document file within. These should be ignored. 
+# Note: exclude_dirnames is new in Sphinx 0.5 
+exclude_dirnames = ['.svn']
+
 # Options for HTML output
 # ---
 

Modified: django/trunk/docs/faq/usage.txt
===
--- django/trunk/docs/faq/usage.txt 2009-03-31 22:41:43 UTC (rev 10302)
+++ django/trunk/docs/faq/usage.txt 2009-03-31 23:34:03 UTC (rev 10303)
@@ -67,3 +67,13 @@
Django. For example, if your :class:`~django.db.models.ImageField` is
called ``mug_shot``, you can get the absolute URL to your image in a
template with ``{{ object.mug_shot.url }}``.
+
+How do I make a variable available to all my templates?
+---
+
+Sometimes your templates just all need the same thing. A common example would
+be dynamically-generated menus. At first glance, it seems logical to simply
+add a common dictionary to the template context.
+
+The correct solution is to use a ``RequestContext``. Details on how to do this
+are here: :ref:`subclassing-context-requestcontext`.

Modified: django/trunk/docs/glossary.txt
===
--- django/trunk/docs/glossary.txt  2009-03-31 22:41:43 UTC (rev 10302)
+++ django/trunk/docs/glossary.txt  2009-03-31 23:34:03 UTC (rev 10303)
@@ -13,8 +13,8 @@
 See :ref:`topics-db-models`.
 
 generic view
-A higher-order :term:`view` function that abstracts common idioms and 
patterns
-found in view development and abstracts them.
+A higher-order :term:`view` function that provides an abstract/generic
+implementation of a common idiom or pattern found in view development.
 
 See :ref:`ref-generic-views`.
 
@@ -71,8 +71,9 @@
 the last bit (``spring``) is the slug.
 
 template
-A chunk of text that separates the presentation of a document from its
-data.
+A chunk of text that acts as formatting for representing data. A
+template helps to abstract the presentation of data from the data
+itself.
 
 See :ref:`topics-templates`.
 

Modified: django/trunk/docs/howto/deployment/fastcgi.txt
===
--- django/trunk/docs/howto/deployment/fastcgi.txt  2009-03-31 22:41:43 UTC 
(rev 10302)
+++ django/trunk/docs/howto/deployment/fastcgi.txt  2009-03-31 23:34:03 UTC 
(rev 10303)
@@ -288,6 +288,19 @@
 specifying multiple entries in the ``fastcgi.server`` directive. Add one
 FastCGI host for each.
 
+Cherokee setup
+==
+
+Cherokee is a very fast, flexible and easy to configure Web Server. It
+supports the widespread technologies nowadays: FastCGI, SCGI, PHP, CGI, SSI,
+TLS and SSL 

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: 
  
 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 ramiro):

  * has_patch:  0 => 1

Comment:

 Updated patch also extends fixes to two recently added templates:
 delete_selected_confirmation.html (added in r10121) and
 change_password.html (added in r10234)

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

Re: [Django] #10358: manage.py sqlall is not truncating long table names for ManyToManyField

[Django]

#10358: manage.py sqlall is not truncating long table names for ManyToManyField
+---
  Reporter:  jb0t   | Owner:  deadwisdom
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by deadwisdom):

  * has_patch:  0 => 1

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

Re: [Django] #10358: manage.py sqlall is not truncating long table names for ManyToManyField

[Django]

#10358: manage.py sqlall is not truncating long table names for ManyToManyField
+---
  Reporter:  jb0t   | Owner:  deadwisdom
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by deadwisdom):

  * owner:  nobody => deadwisdom

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

Re: [Django] #8748: Problems in admin/form with primary keys in an abstract superclass

[Django]

#8748: Problems in admin/form with primary keys in an abstract superclass
-+--
  Reporter:  tr...@meditec-gmbh.com  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jkocherhans):

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

Comment:

 This is working in the most recent version of trunk. r10283. I removed
 editable=True from your pkey field and used str(random.random()) to
 generate its value in save. If you have  amore specific set of models that
 triggers this issue, please re-open this ticket.

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

Re: [Django] #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: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  blocktrans trans 
app_label breadcrumbs capfirst title
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Old description:

> Having
>
> {{{
> {% blocktrans with app.name as name %}{{ name }}{% endblocktrans %}
> }}}
>
> as we currently do in some admin templates shows a decision has been made
> to provide developers the means to translate application names. The
> problem is this feature was DOA (r3270,
> `django/contrib/admin/templates/admin/index.html`, similar template code
> was copied since then to another file: r8474, `app_index.html`)
>
> See relevant [http://groups.google.com/group/django-
> users/browse_frm/thread/f8fcbe25e3327c5d django-users] and
> [http://groups.google.com/group/Django-
> I18N/browse_frm/thread/bdcdaf433bfcd144 django-i18n] threads for the
> details.
>
> The attached patch implements the manual steps outlined by the user
> ''patrikk'' in the first thread with the following enhancements:
>
>  * `index`, `app_index`: Moved the markup-as-translatable of app names
> from the template to the view code so the translators don't need to
> translate a second title()'d version of every app name.
>  * Consistent use of the capfirst filter over the app names in the
> breadcrumbs of the different views
>  * Don't touch `base_site.html` in order to provide for translatability
> of the app name in the  HTML tag for the application-specific
> model list view, implement the needed change in the relevant view
> (`app_index`) instead (replacing a "%s administration" msgid with a more
> translator-friendly "%(app_label)s administration" one in the process).
> This spare translators the need to translate both a "flatpages" and a
> "flatpages administration" literal.
>  * Extended fixes to other templates that also need them
> (`delete_confirm.html`,  `object_history.html`)
>
> '''Note 1:''' The `change_form.html` template ran the app label (in
> addition to the `capfirst` filter) through the `escape` filter. This has
> been dropped because it seems inconsistent with what is done in rest of
> the templates, and because the app name isn't user-provided content.
>
> '''Note 2:''' There seems to be some inconsistency on how the app name is
> .title()'d for the name that appear in the caption of model tables
> (`index` and `app_index` views`) and `|capfirst`'d for use in HTML title
> and breadcrumbs. This has been left untouched to avoid introducing a
> backward incompatible change.
>
> Note that several of the problems exposed above had already been reported
> in #9273 and that some of the presentation-related (like calling .title()
> and/or capfirst() in view code could be moved to templates if/when #5972
> gets committed (will try to work on adding test+docs to it.)

New description:

 Having

 {{{
 {% blocktrans with app.name as name %}{{ name }}{% endblocktrans %}
 }}}

 as we currently do in some admin templates shows a decision has been made
 to provide developers the means to translate application names.

 Problem is this feature was DOA (r3270,
 `django/contrib/admin/templates/admin/index.html`, similar template code
 was copied since then to another file: r8474, `app_index.html`)

 See relevant [http://groups.google.com/group/django-
 users/browse_frm/thread/f8fcbe25e3327c5d django-users] and
 [http://groups.google.com/group/Django-
 I18N/browse_frm/thread/bdcdaf433bfcd144 django-i18n] threads for the
 details.

 The attached patch implements as a fix the awkward manual steps needed to
 workaround this bug outlined by the user ''patrikk'' in the first thread
 with the following enhancements:

  * `index`, `app_index`: Moved the markup-as-translatable of app names
 from the template to the view code so the translators don't need to
 translate a second title()'d version of every app name.
  * Consistent use of the capfirst filter over the app names in the
 breadcrumbs of the different views.
  * Don't touch `base_site.html` in order to provide for translatability of
 the app name in the  HTML tag for the application-specific model
 list view. Implement the needed change in the relevant view (`app_index`)
 instead (replacing a "%s administration" msgid with a more 

Re: [Django] #8538: Document when process_response and process_exception middleware is invoked

[Django]

#8538: Document when process_response and process_exception middleware is 
invoked
+---
  Reporter:  TP | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  middleware
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by deadwisdom):

  * owner:  deadwisdom => nobody

Comment:

 Ah, sorry hadn't updated and just did this.  Go ahead programmerq, if you
 want to take from the book.

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

Re: [Django] #8538: Document when process_response and process_exception middleware is invoked

[Django]

#8538: Document when process_response and process_exception middleware is 
invoked
+---
  Reporter:  TP | Owner:  deadwisdom
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:  middleware
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by deadwisdom):

  * owner:  nobody => deadwisdom
  * has_patch:  0 => 1

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

Re: [Django] #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.1   
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kkubasik):

 This patch will conflict with the js patch in #9983, however. The patch
 there has been updated to include this fix.

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

Re: [Django] #8521: admindocs: sidebar alignment incorrect in Windows firefox

[Django]

#8521: admindocs: sidebar alignment incorrect in Windows firefox
---+
  Reporter:  ametts| Owner:  kkubasik   
  
Status:  closed| Milestone:  1.1
  
 Component:  django.contrib.admin  |   Version:  1.0-beta-1 
  
Resolution:  invalid   |  Keywords:  admin, admindocs, 
css
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by kkubasik):

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

Comment:

 Cannot reproduce. Reopen if you can reliably reproduce.

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

Re: [Django] #10529: Generic Inline fails (unexpected keyword argument `prefix`)

[Django]

#10529: Generic Inline fails (unexpected keyword argument `prefix`)
-+--
  Reporter:  leitjohn| Owner:  leitjohn
Status:  closed  | Milestone:  
 Component:  Forms   |   Version:  SVN 
Resolution:  invalid |  Keywords:  
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by earthman):

 I am receiving the same error after upgrading to trunk...with inline
 forms.

 Was there a solution you found, Leitjohn?  What was the 'mistake' you
 fixed, please? perhaps it is the same in mine.

 Thanks!

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

Re: [Django] #10300: Custom File Storage Backend broken by recent SVN commit.

[Django]

#10300: Custom File Storage Backend broken by recent SVN commit.
---+
  Reporter:  erikcw| Owner:  nobody 
   
Status:  new   | Milestone:  1.1
   
 Component:  File uploads/storage  |   Version:  SVN
   
Resolution:|  Keywords:  file upload 
storage s3
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by erikcw):

 Thanks for the patch kmtracey!  I applied it to my svn checkout and it
 seems to have fixed the problem.  I'm going to keep an eye on it for a few
 days to make sure everything is behaving correctly.

 Like you said, there could still be some other side-effects from r9766 --
 hopefully the maintainer of this area of the branch will take a look and
 give the final sign-off for this fix.

 I'll report if I notice any oddities...

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

[Changeset] r10302 - django/branches/releases/1.0.X

[noreply]

Author: kmtracey
Date: 2009-03-31 17:41:43 -0500 (Tue, 31 Mar 2009)
New Revision: 10302

Modified:
   django/branches/releases/1.0.X/
Log:
[1.0.X]  Remove the block on r10055.  Per note from Adrian this one should be 
merged to the branch but he hasn't done it yet and I haven't gotten around to 
asking him why or if he just wants me to do it.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275,10281
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275,10281


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

Re: [Django] #7631: Model backward inheritance in newforms admin

[Django]

#7631: Model backward inheritance in newforms admin
-+--
  Reporter:  occul...@gmail.com  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  fixed   |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jkocherhans):

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

Comment:

 There are some typos in these models, but I did my best to re-create them,
 and they work with django trunk as of r10283. Please re-open with more
 details if this isn't fixed.

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

Re: [Django] #10682: The latest MySQLdb breaks Django

[Django]

#10682: The latest MySQLdb breaks Django
---+
  Reporter:  twleung   | Owner:  nobody
Status:  closed| Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 Not MysqlDB nor MySQLDB but MySQLdb.  I can never remember which letters
 get capped.

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

Re: [Django] #6033: validation shouldn't take place when deleting inline objects

[Django]

#6033: validation shouldn't take place when deleting inline objects
-+--
  Reporter:  akaihola| Owner:  nobody   

Status:  closed  | Milestone:   

 Component:  django.contrib.admin|   Version:  newforms-admin   

Resolution:  fixed   |  Keywords:  nfa-someday 
inline delete validation newforms
 Stage:  Design decision needed  | Has_patch:  1

Needs_docs:  0   |   Needs_tests:  0

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

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

Comment:

 This was fixed in [10283].

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

Re: [Django] #10682: The latest MySQLdb breaks Django

[Django]

#10682: The latest MySQLdb breaks Django
---+
  Reporter:  twleung   | Owner:  nobody
Status:  closed| Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  duplicate |  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Django hasn't run on "latest trunk" MysqlDB for a long time.  There is
 some considerable restructuring going on in that code and until it gets
 near to a release point it doesn't seem to make a lot of sense to chase
 it.  #9274 is open to track whatever needs to be done to get Django
 running on the next release of MySQLDB.

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

Re: [Django] #4507: Adding form save hooks to newforms admin

[Django]

#4507: Adding form save hooks to newforms admin
+---
  Reporter:  Stas Shtin   | Owner:  nobody

Status:  closed | Milestone:

 Component:  django.contrib.admin   |   Version:  
newforms-admin
Resolution:  fixed  |  Keywords:  
nfa-someday   
 Stage:  Design decision needed | Has_patch:  1 

Needs_docs:  0  |   Needs_tests:  0 

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

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

Comment:

 This has been fixed at some point. See save_form, save_model, and
 save_formset on the ModelAdmin class.

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

Re: [Django] #10684: update name in AUTHORS

[Django]

#10684: update name in AUTHORS
+---
  Reporter:  carljm | Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

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

[Django] #10684: update name in AUTHORS

[Django]

#10684: update name in AUTHORS
---+
 Reporter:  carljm |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+


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

[Changeset] r10301 - django/branches/releases/1.0.X

[noreply]

Author: jacob
Date: 2009-03-31 17:07:15 -0500 (Tue, 31 Mar 2009)
New Revision: 10301

Modified:
   django/branches/releases/1.0.X/
Log:
Blocked [10281] from 1.0.X.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275,10281


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

[Changeset] r10300 - in django/branches/releases/1.0.X: . docs/howto/deployment

[noreply]

Author: jacob
Date: 2009-03-31 17:06:06 -0500 (Tue, 31 Mar 2009)
New Revision: 10300

Added:
   django/branches/releases/1.0.X/docs/howto/deployment/modwsgi.txt
Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/docs/howto/deployment/index.txt
Log:
[1.0.X] Fixed #9970: added mod_wsgi docs. Thanks, Alex Gaynor. Backport of 
r10280 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10279,10282-10283
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10280,10282-10283

Modified: django/branches/releases/1.0.X/docs/howto/deployment/index.txt
===
--- django/branches/releases/1.0.X/docs/howto/deployment/index.txt  
2009-03-31 22:04:15 UTC (rev 10299)
+++ django/branches/releases/1.0.X/docs/howto/deployment/index.txt  
2009-03-31 22:06:06 UTC (rev 10300)
@@ -11,23 +11,17 @@
 .. toctree::
:maxdepth: 1

+   modwsgi
modpython
fastcgi

-:ref:`Deploying under mod_python ` is the
-recommended deployment method; start there if you're not sure which path you'd
-like to go down.
+If you're new to deploying Django and/or Python, we'd recommend you try
+:ref:`mod_wsgi ` first. In most cases it'll be the 
easiest,
+fastest, and most stable deployment choice.
 
 .. seealso::
 
 * `Chapter 20 of The Django Book`_ discusses deployment and especially
   scaling in more detail.
   
-* `mod_wsgi`_ is a newcomer to the Python deployment world, but it's 
rapidly
-  gaining traction. Currently there's a few hoops you have to jump through 
to
-  `use mod_wsgi with Django`_, but mod_wsgi tends to get rave reviews from
-  those who use it.
-
 .. _chapter 20 of the django book: http://djangobook.com/en/1.0/chapter20/
-.. _mod_wsgi: http://code.google.com/p/modwsgi/
-.. _use mod_wsgi with Django: 
http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango
\ No newline at end of file

Copied: django/branches/releases/1.0.X/docs/howto/deployment/modwsgi.txt (from 
rev 10280, django/trunk/docs/howto/deployment/modwsgi.txt)
===
--- django/branches/releases/1.0.X/docs/howto/deployment/modwsgi.txt
(rev 0)
+++ django/branches/releases/1.0.X/docs/howto/deployment/modwsgi.txt
2009-03-31 22:06:06 UTC (rev 10300)
@@ -0,0 +1,68 @@
+.. _howto-deployment-modwsgi:
+
+==
+How to use Django with Apache and mod_wsgi
+==
+
+Deploying Django with Apache_ and `mod_wsgi`_ is the recommended way to get
+Django into production.
+
+.. _Apache: http://httpd.apache.org/
+.. _mod_wsgi: http://code.google.com/p/modwsgi/
+
+mod_wsgi is an Apache module which 

[Changeset] r10299 - in django/branches/releases/1.0.X: . django/template tests/regressiontests/defaultfilters

[noreply]

Author: jacob
Date: 2009-03-31 17:04:15 -0500 (Tue, 31 Mar 2009)
New Revision: 10299

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/template/defaultfilters.py
   django/branches/releases/1.0.X/tests/regressiontests/defaultfilters/tests.py
Log:
[1.0.X] Fixed #10513: floatformat now works with floatish things, not just real 
floats. Thanks, Alex. Backport of [10278] from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10277,10279,10282-10283
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10279,10282-10283

Modified: django/branches/releases/1.0.X/django/template/defaultfilters.py
===
--- django/branches/releases/1.0.X/django/template/defaultfilters.py
2009-03-31 22:02:37 UTC (rev 10298)
+++ django/branches/releases/1.0.X/django/template/defaultfilters.py
2009-03-31 22:04:15 UTC (rev 10299)
@@ -149,7 +149,9 @@
 except InvalidOperation:
 if input_val in special_floats:
 return input_val
-else:
+try:
+d = Decimal(force_unicode(float(text)))
+except (ValueError, InvalidOperation, TypeError, UnicodeEncodeError):
 return u''
 try:
 p = int(arg)

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/defaultfilters/tests.py
===
--- 
django/branches/releases/1.0.X/tests/regressiontests/defaultfilters/tests.py
2009-03-31 22:02:37 UTC (rev 10298)
+++ 
django/branches/releases/1.0.X/tests/regressiontests/defaultfilters/tests.py
2009-03-31 22:04:15 UTC (rev 10299)
@@ -35,8 +35,8 @@
 u''
 >>> floatformat(13.1031, u'bar')
 u'13.1031'
->>> floatformat(18.125, 2) 
-u'18.13' 
+>>> floatformat(18.125, 2)
+u'18.13'
 >>> floatformat(u'foo', u'bar')
 u''
 >>> floatformat(u'¿Cómo esta usted?')
@@ -53,6 +53,15 @@
 >>> floatformat(nan) == unicode(nan)
 True
 
+>>> class FloatWrapper(object):
+... def __init__(self, value):
+... self.value = value
+... def __float__(self):
+... return self.value
+
+>>> floatformat(FloatWrapper(11.01), -2)
+u'11.00'
+
 >>> addslashes(u'"double quotes" and \'single quotes\'')
 u'\\"double quotes\\" and \\\'single quotes\\\''
 
@@ -180,23 +189,23 @@
 u'http://31characteruri.com/test/; rel="nofollow">...'
 
 # Check normal urlize
->>> urlize('http://google.com') 
+>>> urlize('http://google.com')
 u'http://google.com; rel="nofollow">http://google.com'
 
->>> urlize('http://google.com/') 
+>>> urlize('http://google.com/')
 u'http://google.com/; rel="nofollow">http://google.com/'
 
->>> urlize('www.google.com') 
+>>> urlize('www.google.com')
 u'http://www.google.com; rel="nofollow">www.google.com'
 
->>> 

[Changeset] r10298 - in django/branches/releases/1.0.X: . django/utils docs/ref tests/regressiontests/datastructures

[noreply]

Author: jacob
Date: 2009-03-31 17:02:37 -0500 (Tue, 31 Mar 2009)
New Revision: 10298

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/utils/datastructures.py
   django/branches/releases/1.0.X/docs/ref/request-response.txt
   django/branches/releases/1.0.X/tests/regressiontests/datastructures/tests.py
Log:
[1.0.X] Fixed #8847, #10370: added some missing methods to MultiValueDict after 
[8399]. Thanks, James Turk and rfk. Backport of r10241 from trunk.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10240,10242-10247,10250-10257,10259-10270,10273-10274,10276-10277,10279,10282-10283
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10247,10250-10257,10259-10270,10273-10274,10276-10277,10279,10282-10283

Modified: django/branches/releases/1.0.X/django/utils/datastructures.py
===
--- django/branches/releases/1.0.X/django/utils/datastructures.py   
2009-03-31 22:00:46 UTC (rev 10297)
+++ django/branches/releases/1.0.X/django/utils/datastructures.py   
2009-03-31 22:02:37 UTC (rev 10298)
@@ -294,10 +294,19 @@
 """Returns a list of (key, list) pairs."""
 return super(MultiValueDict, self).items()
 
+def iterlists(self):
+"""Yields (key, list) pairs."""
+return super(MultiValueDict, self).iteritems()
+
 def values(self):
 """Returns a list of the last value on every key list."""
 return [self[key] for key in self.keys()]
-
+
+def itervalues(self):
+"""Yield the last value on every key list."""
+for key in self.iterkeys():
+yield self[key]
+
 def copy(self):
 """Returns a copy of this object."""
 return self.__deepcopy__()

Modified: django/branches/releases/1.0.X/docs/ref/request-response.txt
===
--- django/branches/releases/1.0.X/docs/ref/request-response.txt
2009-03-31 22:00:46 UTC (rev 10297)
+++ django/branches/releases/1.0.X/docs/ref/request-response.txt
2009-03-31 22:02:37 UTC (rev 10298)
@@ -14,11 +14,11 @@
 
 When a page is requested, Django creates an :class:`HttpRequest` object that
 contains metadata about the request. Then Django loads the appropriate view,
-passing the :class:`HttpRequest` as the first argument to the view function. 
Each
-view is responsible for returning an :class:`HttpResponse` object.
+passing the :class:`HttpRequest` as the first argument to the view function.
+Each view is responsible for returning an :class:`HttpResponse` object.
 
-This document explains the APIs for :class:`HttpRequest` and 
:class:`HttpResponse`
-objects.
+This document explains the APIs for :class:`HttpRequest` and
+:class:`HttpResponse` objects.
 
 HttpRequest objects
 ===
@@ -103,7 +103,8 @@
   

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.1 
 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 kkubasik):

  * has_patch:  0 => 1

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

Re: [Django] #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.1 
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by kkubasik):

 Ok, I have a patch for a bit of a dual-fix.

 1) Listens to both events so that mouse or keyboard will get the
 autopopulation of the field.
 2) Handle the 'choice' instance by using the name and not the value of the
 select box.

 Let me know if it looks good.

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

[Changeset] r10297 - in django/branches/releases/1.0.X: . django/contrib/admin/templates/admin/auth/user

[noreply]

Author: jacob
Date: 2009-03-31 17:00:46 -0500 (Tue, 31 Mar 2009)
New Revision: 10297

Modified:
   django/branches/releases/1.0.X/
   
django/branches/releases/1.0.X/django/contrib/admin/templates/admin/auth/user/change_password.html
Log:
[1.0.X] Fixed #8749: add better breadcrumbs in the change password template. 
Thanks, SmileyChris. Backport of r10234 from trunk.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10233,10236-10240,10242-10247,10250-10257,10259-10270,10273-10274,10276-10277,10279,10282-10283
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10234,10236-10240,10242-10247,10250-10257,10259-10270,10273-10274,10276-10277,10279,10282-10283

Modified: 
django/branches/releases/1.0.X/django/contrib/admin/templates/admin/auth/user/change_password.html
===
--- 
django/branches/releases/1.0.X/django/contrib/admin/templates/admin/auth/user/change_password.html
  2009-03-31 21:59:09 UTC (rev 10296)
+++ 
django/branches/releases/1.0.X/django/contrib/admin/templates/admin/auth/user/change_password.html
  2009-03-31 22:00:46 UTC (rev 10297)
@@ -8,6 +8,7 @@
 {% block breadcrumbs %}{% if not is_popup %}
 
  {% trans "Home" %} 
+ {{ opts.app_label|capfirst|escape }} 
  {{ opts.verbose_name_plural|capfirst }} 
  {{ original|truncatewords:"18" }} 
  {% trans 'Change password' %}


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

[Changeset] r10296 - django/branches/releases/1.0.X

[noreply]

Author: jacob
Date: 2009-03-31 16:59:09 -0500 (Tue, 31 Mar 2009)
New Revision: 10296

Modified:
   django/branches/releases/1.0.X/
Log:
Block the rest of the 1.1 features to date from 1.0.X.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235,10248-10249,10258,10271-10272,10275


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

[Changeset] r10295 - django/branches/releases/1.0.X

[noreply]

Author: jacob
Date: 2009-03-31 16:58:14 -0500 (Tue, 31 Mar 2009)
New Revision: 10295

Modified:
   django/branches/releases/1.0.X/
Log:
Marked the rest of the revs already integreated into [1.0.X]


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10226,10230-10233,10236-10237,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10228,10230-10233,10236-10240,10242-10247,10250-10257,10259-10270,10273-10274,10276-10277,10279,10282-10283


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

Re: [Django] #10682: The latest MySQLdb breaks Django

[Django]

#10682: The latest MySQLdb breaks Django
---+
  Reporter:  twleung   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 I can't find any references to mysql.base in Django, can you post a full
 traceback so we can make sure it's not an issue with MySQLdb.

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

Re: [Django] #10682: The latest MySQLdb breaks Django

[Django]

#10682: The latest MySQLdb breaks Django
---+
  Reporter:  twleung   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Database layer (models, ORM)
  * needs_tests:  => 0
  * milestone:  => 1.1
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

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

[Changeset] r10294 - in django/branches/releases/1.0.X: . django/forms tests/modeltests/model_forms

[noreply]

Author: jacob
Date: 2009-03-31 16:48:29 -0500 (Tue, 31 Mar 2009)
New Revision: 10294

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/forms/models.py
   django/branches/releases/1.0.X/tests/modeltests/model_forms/models.py
Log:
[1.0.X] Fixed #8746: Check data in raw_id_fields more closely. Thanks, dgouldin

Backport of r10233 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10226,10230-10232,10236-10237,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10226,10230-10233,10236-10237,10239-10240

Modified: django/branches/releases/1.0.X/django/forms/models.py
===
--- django/branches/releases/1.0.X/django/forms/models.py   2009-03-31 
21:42:47 UTC (rev 10293)
+++ django/branches/releases/1.0.X/django/forms/models.py   2009-03-31 
21:48:29 UTC (rev 10294)
@@ -740,6 +740,7 @@
 'list': _(u'Enter a list of values.'),
 'invalid_choice': _(u'Select a valid choice. %s is not one of the'
 u' available choices.'),
+'invalid_pk_value': _(u'"%s" is not a valid value for a primary key.')
 }
 
 def __init__(self, queryset, cache_choices=False, required=True,
@@ -762,6 +763,8 @@
 obj = self.queryset.get(pk=val)
 except self.queryset.model.DoesNotExist:
 raise ValidationError(self.error_messages['invalid_choice'] % 
val)
+except ValueError:
+raise ValidationError(self.error_messages['invalid_pk_value'] 
% val)
 else:
 final_values.append(obj)
 return final_values

Modified: django/branches/releases/1.0.X/tests/modeltests/model_forms/models.py
===
--- django/branches/releases/1.0.X/tests/modeltests/model_forms/models.py   
2009-03-31 21:42:47 UTC (rev 10293)
+++ django/branches/releases/1.0.X/tests/modeltests/model_forms/models.py   
2009-03-31 21:48:29 UTC (rev 10294)
@@ -813,6 +813,10 @@
 Traceback (most recent call last):
 ...
 ValidationError: [u'Enter a list of values.']
+>>> f.clean(['fail'])
+Traceback (most recent call last):
+...
+ValidationError: [u'"fail" is not a valid value for a primary key.']
 
 # Add a Category object *after* the ModelMultipleChoiceField has already been
 # instantiated. This proves clean() checks the database during clean() rather


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

Re: [Django] #10683: The latest MySQLdb breaks Django

[Django]

#10683: The latest MySQLdb breaks Django
+---
  Reporter:  twleung| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

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

Comment:

 Dupe of #10682

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

[Django] #10683: The latest MySQLdb breaks Django

[Django]

#10683: The latest MySQLdb breaks Django
---+
 Reporter:  twleung|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I installed the trunk of MySQLdb, and when I run manage.py, I get the
 following message:

 Error: No module named mysql.base

 I'm on django 1.0.2

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

[Django] #10682: The latest MySQLdb breaks Django

[Django]

#10682: The latest MySQLdb breaks Django
---+
 Reporter:  twleung|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I installed the trunk of MySQLdb, and when I run manage.py, I get the
 following message:

 Error: No module named mysql.base

 I'm on django 1.0.2

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

Re: [Django] #5335: Add an append method to ErrorDict

[Django]

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

 Component:  Forms |   Version:  SVN

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

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by simon29):

 Definitely. Often views need to perform more involved steps *after* the
 form is validated; which may fail, and ultimately mean there was a problem
 with what was entered in the form.

 There needs to be an easy, documented, encouraged way of appending errors
 to NON_FIELD_ERRORS as well as to specific fields; post-validation (ie
 from the view).

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

[Changeset] r10293 - in django/branches/releases/1.0.X: . django/contrib/contenttypes django/db/models/fields tests/modeltests/many_to_many tests/modeltests/many_to_one

[noreply]

Author: jacob
Date: 2009-03-31 16:42:47 -0500 (Tue, 31 Mar 2009)
New Revision: 10293

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/contrib/contenttypes/generic.py
   django/branches/releases/1.0.X/django/db/models/fields/related.py
   django/branches/releases/1.0.X/tests/modeltests/many_to_many/models.py
   django/branches/releases/1.0.X/tests/modeltests/many_to_one/models.py
Log:
[1.0.X] Fixed #10413: RelatedManager.add no longer fails silenty when trying to 
add an object of the wrong type. Thanks, dgouldin.

Backport of r10226 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10225,10230-10232,10236-10237,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10226,10230-10232,10236-10237,10239-10240

Modified: django/branches/releases/1.0.X/django/contrib/contenttypes/generic.py
===
--- django/branches/releases/1.0.X/django/contrib/contenttypes/generic.py   
2009-03-31 21:40:40 UTC (rev 10292)
+++ django/branches/releases/1.0.X/django/contrib/contenttypes/generic.py   
2009-03-31 21:42:47 UTC (rev 10293)
@@ -253,6 +253,8 @@
 
 def add(self, *objs):
 for obj in objs:
+if not isinstance(obj, self.model):
+raise TypeError, "'%s' instance expected" % 
self.model._meta.object_name
 setattr(obj, self.content_type_field_name, self.content_type)
 setattr(obj, self.object_id_field_name, self.pk_val)
 obj.save()

Modified: django/branches/releases/1.0.X/django/db/models/fields/related.py
===
--- django/branches/releases/1.0.X/django/db/models/fields/related.py   
2009-03-31 21:40:40 UTC (rev 10292)
+++ django/branches/releases/1.0.X/django/db/models/fields/related.py   
2009-03-31 21:42:47 UTC (rev 10293)
@@ -325,6 +325,8 @@
 
 def add(self, *objs):
 for obj in objs:
+if not isinstance(obj, self.model):
+raise TypeError, "'%s' instance expected" % 
self.model._meta.object_name
 setattr(obj, rel_field.name, instance)
 obj.save()
 add.alters_data = True
@@ -445,11 +447,14 @@
 
 # If there aren't any objects, there is nothing to do.
 if objs:
+from django.db.models.base import Model
 # Check that all the objects are of the right type
 new_ids = set()
 for obj in objs:
 if isinstance(obj, self.model):
 new_ids.add(obj._get_pk_val())
+elif isinstance(obj, Model):
+raise TypeError, "'%s' instance expected" % 
self.model._meta.object_name
 else:
 

Re: [Django] #10670: Using a QuerySet in a filter expression can cause later evaluation of the QuerySet to raise ProgrammingError

[Django]

#10670: Using a QuerySet in a filter expression can cause later evaluation of 
the
QuerySet to raise ProgrammingError
---+
  Reporter:  benanhalt | Owner:  Alex
Status:  assigned  | Milestone:  1.1 
 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 Alex):

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

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

[Changeset] r10292 - in django/branches/releases/1.0.X: . django/utils

[noreply]

Author: jacob
Date: 2009-03-31 16:40:40 -0500 (Tue, 31 Mar 2009)
New Revision: 10292

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/utils/html.py
Log:
[1.0.X] Fixed #9883: no longer do strange things with whitespace in the 
linebreaks filter. Thanks, keithb.

Backport of r10225 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10224,10230-10232,10236-10237,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10225,10230-10232,10236-10237,10239-10240

Modified: django/branches/releases/1.0.X/django/utils/html.py
===
--- django/branches/releases/1.0.X/django/utils/html.py 2009-03-31 21:15:55 UTC 
(rev 10291)
+++ django/branches/releases/1.0.X/django/utils/html.py 2009-03-31 21:40:40 UTC 
(rev 10292)
@@ -46,9 +46,9 @@
 value = re.sub(r'\r\n|\r|\n', '\n', force_unicode(value)) # normalize 
newlines
 paras = re.split('\n{2,}', value)
 if autoescape:
-paras = [u'%s' % escape(p.strip()).replace('\n', '') for 
p in paras]
+paras = [u'%s' % escape(p).replace('\n', '') for p in 
paras]
 else:
-paras = [u'%s' % p.strip().replace('\n', '') for p in 
paras]
+paras = [u'%s' % p.replace('\n', '') for p in paras]
 return u'\n\n'.join(paras)
 linebreaks = allow_lazy(linebreaks, unicode)
 


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

Re: [Django] #9969: Admin changelist table field and list_filter section broken when field value has been chosen from a choices named group

[Django]

#9969: Admin changelist table field and list_filter section broken when field
value has been chosen from a choices named group
---+
  Reporter:  ramiro| Owner:  ramiro 

Status:  new   | Milestone:  1.1

 Component:  django.contrib.admin  |   Version:  SVN

Resolution:|  Keywords:  change list 
choices columns (None) named groups select dropdown
 Stage:  Ready for checkin | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * stage:  Accepted => Ready for checkin

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

Re: [Django] #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.1 
 Component:  django.contrib.admin  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by kkubasik):

  * owner:  nobody => kkubasik

Comment:

 Fixing it.

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

Re: [Django] #10672: Proxy Model does not send save signal

[Django]

#10672: Proxy Model does not send save signal
---+
  Reporter:  zbyte64   | Owner:  nobody
Status:  new   | Milestone:  1.1   
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by zbyte64):

 Replying to [comment:2 medhat]:
 > the last line should be: self.assertRaises(Exception, tp.save())

 You're not suppose to call the function in the parameter, or else the
 function won't catch the exception, here's a simple example:

 {{{
 import unittest

 def raise_error():
 assert False

 class AssertErrorTestCase(unittest.TestCase):
 def test_if_callable(self):
 self.assertRaises(AssertionError, raise_error)

 def test_if_inline_call(self):
 self.assertRaises(AssertionError, raise_error())

 if __name__ == '__main__':
 unittest.main()
 }}}

 The result is "test_if_inline_call" fails while "test_if_callable" passes.

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

[Changeset] r10291 - in django/branches/releases/1.0.X: . django/db/models/fields tests/modeltests/one_to_one

[noreply]

Author: jacob
Date: 2009-03-31 16:15:55 -0500 (Tue, 31 Mar 2009)
New Revision: 10291

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/db/models/fields/related.py
   django/branches/releases/1.0.X/tests/modeltests/one_to_one/models.py
Log:
[1.0.X] Fixed #10157: correctly set the related objects pk when assigning a 
reverse OneToOne. Thanks, dgouldin.

Backport of r10224 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223,10230-10232,10236-10237,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223-10224,10230-10232,10236-10237,10239-10240

Modified: django/branches/releases/1.0.X/django/db/models/fields/related.py
===
--- django/branches/releases/1.0.X/django/db/models/fields/related.py   
2009-03-31 21:14:39 UTC (rev 10290)
+++ django/branches/releases/1.0.X/django/db/models/fields/related.py   
2009-03-31 21:15:55 UTC (rev 10291)
@@ -203,8 +203,8 @@
 (value, instance._meta.object_name,
  self.related.get_accessor_name(), 
self.related.opts.object_name))
 
-# Set the value of the related field
-setattr(value, self.related.field.rel.get_related_field().attname, 
instance)
+# Set the value of the related field to the value of the related 
object's related field
+setattr(value, self.related.field.attname, getattr(instance, 
self.related.field.rel.get_related_field().attname))
 
 # Since we already know what the related object is, seed the related
 # object caches now, too. This avoids another db hit if you get the

Modified: django/branches/releases/1.0.X/tests/modeltests/one_to_one/models.py
===
--- django/branches/releases/1.0.X/tests/modeltests/one_to_one/models.py
2009-03-31 21:14:39 UTC (rev 10290)
+++ django/branches/releases/1.0.X/tests/modeltests/one_to_one/models.py
2009-03-31 21:15:55 UTC (rev 10291)
@@ -79,6 +79,8 @@
 
 >>> r.place
 
+>>> p2.id
+2
 
 # Set the place back again, using assignment in the reverse direction.
 >>> p1.restaurant = r


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

Re: [Django] #10180: Fixed bug saving inlineformset_factory formsets

[Django]

#10180: Fixed bug saving inlineformset_factory formsets
---+
  Reporter:  simon29   | Owner:  nobody
Status:  closed| Milestone:  1.1   
 Component:  Forms |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by jkocherhans):

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

Comment:

 If I understand your example correctly, you should be doing this instead:

 {{{ formset = AppMemberFormSet(request.POST, instance=app) }}}

 If you have a reason for assigning formset.instance, or if I'm
 misunderstanding your problem, please reopen this ticket with more
 details.

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

[Changeset] r10290 - in django/branches/releases/1.0.X: . django/utils

[noreply]

Author: jacob
Date: 2009-03-31 16:14:39 -0500 (Tue, 31 Mar 2009)
New Revision: 10290

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/utils/cache.py
Log:
[1.0.X] Fixed #10387: removed some code duplication in django.utils.cache. 
Thanks, Travis Swicegood.

Backport of r10223 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10230-10232,10236-10237,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10223,10230-10232,10236-10237,10239-10240

Modified: django/branches/releases/1.0.X/django/utils/cache.py
===
--- django/branches/releases/1.0.X/django/utils/cache.py2009-03-31 
20:49:37 UTC (rev 10289)
+++ django/branches/releases/1.0.X/django/utils/cache.py2009-03-31 
21:14:39 UTC (rev 10290)
@@ -146,6 +146,11 @@
 return 'views.decorators.cache.cache_page.%s.%s.%s' % (
key_prefix, iri_to_uri(request.path), ctx.hexdigest())
 
+def _generate_cache_header_key(key_prefix, request):
+"""Returns a cache key for the header cache."""
+return 'views.decorators.cache.cache_header.%s.%s' % (
+key_prefix, iri_to_uri(request.path))
+
 def get_cache_key(request, key_prefix=None):
 """
 Returns a cache key based on the request path. It can be used in the
@@ -158,8 +163,7 @@
 """
 if key_prefix is None:
 key_prefix = settings.CACHE_MIDDLEWARE_KEY_PREFIX
-cache_key = 'views.decorators.cache.cache_header.%s.%s' % (
-key_prefix, iri_to_uri(request.path))
+cache_key = _generate_cache_header_key(key_prefix, request)
 headerlist = cache.get(cache_key, None)
 if headerlist is not None:
 return _generate_cache_key(request, headerlist, key_prefix)
@@ -183,8 +187,7 @@
 key_prefix = settings.CACHE_MIDDLEWARE_KEY_PREFIX
 if cache_timeout is None:
 cache_timeout = settings.CACHE_MIDDLEWARE_SECONDS
-cache_key = 'views.decorators.cache.cache_header.%s.%s' % (
-key_prefix, iri_to_uri(request.path))
+cache_key = _generate_cache_header_key(key_prefix, request)
 if response.has_header('Vary'):
 headerlist = ['HTTP_'+header.upper().replace('-', '_')
   for header in cc_delim_re.split(response['Vary'])]


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

Re: [Django] #10668: Django Pony Missing

[Django]

#10668: Django Pony Missing
+---
  Reporter:  dougn  | Owner:  jacob   
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  1.0 
Resolution:  fixed  |  Keywords:  pony missing
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by anonymous):

 Sounds like someone was watching the MailChimp heist from the Webmaster
 Jam Session

 http://www.mailchimp.com/blog/have-you-seen-this-chimp/

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

[Changeset] r10289 - django/branches/releases/1.0.X

[noreply]

Author: jacob
Date: 2009-03-31 15:49:37 -0500 (Tue, 31 Mar 2009)
New Revision: 10289

Modified:
   django/branches/releases/1.0.X/
Log:
Blocked some more revs from 1.0.X. Isn't this fun?


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-blocked
   - 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191
   + 
/django/trunk:9098,9103,9110,9112,9145,9152,9157,9160,9188,9248,9263,9278,9299-9300,9303-9304,9332,9344,9346,9348-9349,9353-9354,9397-9398,9463-9465,9470,9489-9490,9527-9528,9530-9532,9537-9538,9551-9555,9558,9561,9569,9592-9594,9620,9625,9637,9643,9646,9690,9700-9702,9707-9708,9714-9715,9724,9727-9729,9739,9742-9749,9752-9756,9759-9760,9763-9766,9769,9781,9785-9788,9791-9792,9799-9800,9803-9805,9808,9814-9820,9838-9841,9844-9846,9860,9862,9876,9882,9888-9898,9904-9905,9910-9911,9913,9915,9918,9921,9928,9930,9938,9940-9941,9944,9951-9952,9955,9963-9965,9978,9985,9989,10002,10005-10006,10008,10011-10012,10018,10021,10026-10030,10032-10035,10042-10048,10053,10055,10062-10065,10070,10077,10080-10084,10088-10103,10105,10107-10124,10128-10135,10137,10141-10142,10144,10148,10161-10162,10168-10169,10171-10172,10174,10177-10179,10181-10184,10186-10188,10190-10191,10197,10222,10229,10235


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

[Changeset] r10288 - django/branches/releases/1.0.X

[noreply]

Author: jacob
Date: 2009-03-31 15:48:06 -0500 (Tue, 31 Mar 2009)
New Revision: 10288

Modified:
   django/branches/releases/1.0.X/
Log:
Marked some more revs as integrated into 1.0.X.


Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10239-10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10195-10196,10198-10221,10230-10232,10236-10237,10239-10240


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

Re: [Django] #9370: UnicodeDecodeError when serving binary static files through GZipMiddleWare

[Django]

#9370: UnicodeDecodeError when serving binary static files through 
GZipMiddleWare
-+--
  Reporter:  kikko   | Owner:  kkubasik
Status:  closed  | Milestone:  1.1 
 Component:  Core framework  |   Version:  1.0 
Resolution:  invalid |  Keywords:  
 Stage:  Accepted| Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by kkubasik):

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

Comment:

 I cannot reproduce this against current trunk. Please reopen if you can
 create a test case which is reliably reproducible.

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

[Changeset] r10287 - in django/branches/releases/1.0.X: . django/forms tests/regressiontests/admin_views

[noreply]

Author: jkocherhans
Date: 2009-03-31 15:39:54 -0500 (Tue, 31 Mar 2009)
New Revision: 10287

Modified:
   django/branches/releases/1.0.X/
   django/branches/releases/1.0.X/django/forms/models.py
   django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py
   django/branches/releases/1.0.X/tests/regressiontests/admin_views/tests.py
Log:
[1.0.X] Fixed #9863. A ForeignKey with editable=False to the parent in an 
inline no longer raises an exception. Thanks to keithb for the test case and 
Alex Gaynor for the patch. Backport of r10239 from trunk.



Property changes on: django/branches/releases/1.0.X
___
Name: svnmerge-integrated
   - 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10240
   + 
/django/trunk:1-9097,9099-9102,9104-9109,9111,9113-9144,9146-9151,9153-9156,9158-9159,9161-9187,9189-9247,9249-9262,9264-9277,9279-9298,9301-9302,9305-9331,9333-9343,9345,9347,9350-9352,9355-9396,9399-9462,9466-9469,9471-9488,9491-9526,9529,9533-9536,9539-9550,9556-9557,9559-9560,9562-9568,9570-9591,9595-9619,9621-9624,9626-9636,9638-9642,9644-9645,9647-9689,9691-9699,9703-9706,9709-9713,9716-9723,9725-9726,9730-9738,9740-9741,9750-9751,9757-9758,9761-9762,9767-9768,9770-9780,9782-9784,9789-9790,9793-9798,9801-9802,9806-9807,9809-9813,9821-9837,9842-9843,9847-9859,9861,9863-9875,9877-9881,9883-9887,9899-9903,9906-9909,9912,9914,9916-9917,9919-9920,9922-9927,9929,9931-9937,9939,9942-9943,9945-9950,9953-9954,9956-9962,9966-9977,9979-9984,9986-9988,9990,9992,9994,9996-9998,10003,10007,10009,10013,10015,10017,10022,10024,10031,10036-10037,10040,10049,10051,10054,10056-10058,10071,10073-10074,10078,10104,10125,10136,10139,10143,10145-10147,10149-10152,10170,10175,10193,10239-10240

Modified: django/branches/releases/1.0.X/django/forms/models.py
===
--- django/branches/releases/1.0.X/django/forms/models.py   2009-03-31 
20:30:05 UTC (rev 10286)
+++ django/branches/releases/1.0.X/django/forms/models.py   2009-03-31 
20:39:54 UTC (rev 10287)
@@ -519,7 +519,11 @@
 if self._pk_field == self.fk:
 form.fields[self._pk_field.name] = 
InlineForeignKeyField(self.instance, pk_field=True)
 else:
-form.fields[self.fk.name] = InlineForeignKeyField(self.instance, 
label=form.fields[self.fk.name].label)
+# The foreign key field might not be on the form, so we poke at the
+# Model field to get the label, since we need that for error 
messages.
+form.fields[self.fk.name] = InlineForeignKeyField(self.instance,
+label=getattr(form.fields.get(self.fk.name), 'label', 
capfirst(self.fk.verbose_name))
+)
 
 def _get_foreign_key(parent_model, model, fk_name=None):
 """

Modified: 
django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py
===
--- django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py  
2009-03-31 20:30:05 UTC (rev 10286)
+++ django/branches/releases/1.0.X/tests/regressiontests/admin_views/models.py  
2009-03-31 20:39:54 UTC (rev 10287)
@@ -177,6 +177,20 @@
 BarAccountAdmin
 )
 
+class Parent(models.Model):
+name = models.CharField(max_length=128)
+
+class Child(models.Model):
+parent = models.ForeignKey(Parent, editable=False)
+name = models.CharField(max_length=30, blank=True)
+
+class ChildInline(admin.StackedInline):
+model = Child
+
+class ParentAdmin(admin.ModelAdmin):
+model = Parent
+inlines = [ChildInline]
+
 admin.site.register(Article, ArticleAdmin)
 admin.site.register(CustomArticle, CustomArticleAdmin)
 admin.site.register(Section, inlines=[ArticleInline])
@@ -184,6 +198,7 @@
 admin.site.register(Color)
 admin.site.register(Thing, ThingAdmin)
 admin.site.register(Persona, PersonaAdmin)
+admin.site.register(Parent, ParentAdmin)
 
 # We intentionally register Promo and ChapterXtra1 but not Chapter nor 
ChapterXtra2.
 # 

[Changeset] r10286 - in django/branches/releases/1.0.X: django/forms tests/modeltests/model_formsets tests/regressiontests/inline_formsets

[noreply]

Author: jkocherhans
Date: 2009-03-31 15:30:05 -0500 (Tue, 31 Mar 2009)
New Revision: 10286

Modified:
   django/branches/releases/1.0.X/django/forms/forms.py
   django/branches/releases/1.0.X/django/forms/formsets.py
   django/branches/releases/1.0.X/django/forms/models.py
   django/branches/releases/1.0.X/tests/modeltests/model_formsets/models.py
   
django/branches/releases/1.0.X/tests/regressiontests/inline_formsets/models.py
Log:
[1.0.X] Forms in model formsets and inline formsets can now be deleted even if 
they don't validate. Related to #9587. Backport of r10283 from trunk.


Modified: django/branches/releases/1.0.X/django/forms/forms.py
===
--- django/branches/releases/1.0.X/django/forms/forms.py2009-03-31 
20:04:55 UTC (rev 10285)
+++ django/branches/releases/1.0.X/django/forms/forms.py2009-03-31 
20:30:05 UTC (rev 10286)
@@ -205,6 +205,15 @@
 """
 return self.errors.get(NON_FIELD_ERRORS, self.error_class())
 
+def _raw_value(self, fieldname):
+"""
+Returns the raw_value for a particular field name. This is just a
+convenient wrapper around widget.value_from_datadict.
+"""
+field = self.fields[fieldname]
+prefix = self.add_prefix(fieldname)
+return field.widget.value_from_datadict(self.data, self.files, prefix)
+
 def full_clean(self):
 """
 Cleans all of self.data and populates self._errors and

Modified: django/branches/releases/1.0.X/django/forms/formsets.py
===
--- django/branches/releases/1.0.X/django/forms/formsets.py 2009-03-31 
20:04:55 UTC (rev 10285)
+++ django/branches/releases/1.0.X/django/forms/formsets.py 2009-03-31 
20:30:05 UTC (rev 10286)
@@ -216,9 +216,8 @@
 # more code than we'd like, but the form's cleaned_data will
 # not exist if the form is invalid.
 field = form.fields[DELETION_FIELD_NAME]
-prefix = form.add_prefix(DELETION_FIELD_NAME)
-value = field.widget.value_from_datadict(self.data, 
self.files, prefix)
-should_delete = field.clean(value)
+raw_value = form._raw_value(DELETION_FIELD_NAME)
+should_delete = field.clean(raw_value)
 if should_delete:
 # This form is going to be deleted so any of its errors
 # should not cause the entire formset to be invalid.

Modified: django/branches/releases/1.0.X/django/forms/models.py
===
--- django/branches/releases/1.0.X/django/forms/models.py   2009-03-31 
20:04:55 UTC (rev 10285)
+++ django/branches/releases/1.0.X/django/forms/models.py   2009-03-31 
20:30:05 UTC (rev 10286)
@@ -408,16 +408,22 @@
 existing_objects[obj.pk] = obj
 saved_instances = []
 for form in self.initial_forms:
-obj = existing_objects[form.cleaned_data[self._pk_field.name]]
-if self.can_delete and form.cleaned_data[DELETION_FIELD_NAME]:
-self.deleted_objects.append(obj)
-obj.delete()
-else:
-if form.changed_data:
-self.changed_objects.append((obj, form.changed_data))
-saved_instances.append(self.save_existing(form, obj, 
commit=commit))
-if not commit:
-self.saved_forms.append(form)
+ pk_name = self._pk_field.name
+ raw_pk_value = form._raw_value(pk_name)
+ pk_value = form.fields[pk_name].clean(raw_pk_value)
+ obj = existing_objects[pk_value]
+ if self.can_delete:
+ raw_delete_value = form._raw_value(DELETION_FIELD_NAME)
+ should_delete = 
form.fields[DELETION_FIELD_NAME].clean(raw_delete_value)
+ if should_delete:
+ self.deleted_objects.append(obj)
+ obj.delete()
+ continue
+ if form.changed_data:
+ self.changed_objects.append((obj, form.changed_data))
+ saved_instances.append(self.save_existing(form, obj, 
commit=commit))
+ if not commit:
+ self.saved_forms.append(form)
 return saved_instances
 
 def save_new_objects(self, commit=True):
@@ -427,8 +433,11 @@
 continue
 # If someone has marked an add form for deletion, don't save the
 # object.
-if self.can_delete and form.cleaned_data[DELETION_FIELD_NAME]:
-continue
+if self.can_delete:
+raw_delete_value = form._raw_value(DELETION_FIELD_NAME)
+should_delete = 
form.fields[DELETION_FIELD_NAME].clean(raw_delete_value)
+if should_delete:
+