Re: [Django] #7770: HttpResponse.set_cookie should accept expires=datetime

[Django]

#7770: HttpResponse.set_cookie should accept expires=datetime
+---
  Reporter:  jdunck | Owner:  nobody
Status:  new| Milestone:
 Component:  HTTP handling  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

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

Comment:

 Ok, here's the patch with tests.

 I should have done this work when I wrote the custom session age stuff...

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9172: CsrfMiddleware breaks django test client

[Django]

#9172: CsrfMiddleware breaks django test client
+---
  Reporter:  gruffudd   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 Replying to [comment:8 davenaff]:
 > Maybe I'm missing something, but I don't see the patch attached to this
 ticket - just a blank diff file.

 This is a common problem with Trac; some patches break the patch viewer.
 If you download the patch, it should be ok.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9197: Add new fieldtype (eg. Extra)

[Django]

#9197: Add new fieldtype (eg. Extra)
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.0   
Resolution:  wontfix   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 You can already write custom field types that end up producing pretty much
 whatever SQL you like (this is how GeoDjango does a lot of stuff, for
 example). Writing custom field classes is documented.

 This doesn't sound like a particularly robust way to do something in
 Django's core, since it's adding something that looks like a model field,
 but isn't really (since setting the attribute value does nothing for
 example). I think this is best done as a third-party field object if
 that's the way you want to work, rather than including it in core. It
 looks a bit too confusing and we already have custom managers and
 `extra()` to do this right now.

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

Re: [Django] #9172: CsrfMiddleware breaks django test client

[Django]

#9172: CsrfMiddleware breaks django test client
+---
  Reporter:  gruffudd   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by davenaff):

 Maybe I'm missing something, but I don't see the patch attached to this
 ticket - just a blank diff file.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9172: CsrfMiddleware breaks django test client

[Django]

#9172: CsrfMiddleware breaks django test client
+---
  Reporter:  gruffudd   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by davenaff):

 * cc: davenaff (added)

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

Re: [Django] #9203: LatestCommentFeed syndicates old comments

[Django]

#9203: LatestCommentFeed syndicates old comments
--+-
  Reporter:  hanksims | Owner:  nobody  
Status:  new  | Milestone:  post-1.0
 Component:  django.contrib.comments  |   Version:  1.0 
Resolution:   |  Keywords:  syndication, rss
 Stage:  Unreviewed   | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by hanksims):

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

Comment:

 LatestCommentFeed? is actually OldestCommentFeed?.

 It selects and returns the 40 oldest comments, ordering them by ascending
 submit_date. It should select and return the 40 newest comments, ordering
 them by descending submit_date.

 Seems to be a cousin of #8917.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9203: LatestCommentFeed syndicates old comments

[Django]

#9203: LatestCommentFeed syndicates old comments
-+--
 Reporter:  hanksims |   Owner:  nobody
   Status:  new  |   Milestone:  post-1.0  
Component:  django.contrib.comments  | Version:  1.0   
 Keywords:  syndication, rss |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 LatestCommentFeed is actually OldestCommentFeed.

 It selects and returns the 40 oldest comments, ordering them by ascending
 submit_date. It should select and return the 40 ''newest'' comments,
 ordering them by ''descending'' submit_date.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3591: add support for custom app_label and verbose_name

[Django]

#3591: add support for custom app_label and verbose_name
-+--
  Reporter:  jkocherhans | Owner:  adrian  
Status:  assigned| Milestone:  post-1.0
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)

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

Re: [Django] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
---+
  Reporter:  ddurham   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.formtools  |   Version:  SVN   
Resolution:|  Keywords:  session wizard
 Stage:  Design decision needed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by edcrypt):

 * cc: [EMAIL PROTECTED] (added)
  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 1
  * needs_docs:  => 1

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

Re: [Django] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
---+
  Reporter:  pixelcort | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by knoffhoff):

 * cc: [EMAIL PROTECTED] (added)

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

Re: [Django] #9154: Huge improvements in templates rendering

[Django]

#9154: Huge improvements in templates rendering
--+-
  Reporter:  msaelices| Owner:  msaelices
Status:  new  | Milestone:   
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Unreviewed   | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Also:
  * The new functionality of a `dirs` argument on `get_template` doesn't
 belong in this ticket
  * And I'm guessing `from_child` argument slipped in there by mistake?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6262: Cache templates

[Django]

#6262: Cache templates
-+--
  Reporter:  SmileyChris | Owner:  SmileyChris
Status:  assigned| Milestone: 
 Component:  Template system |   Version:  SVN
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * status:  new => assigned

Comment:

 Related ticket: #9154

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9154: Huge improvements in templates rendering

[Django]

#9154: Huge improvements in templates rendering
--+-
  Reporter:  msaelices| Owner:  msaelices
Status:  new  | Milestone:   
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:   
 Stage:  Unreviewed   | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Related ticket: #6262

 Good things:
  * You're getting the cache templates discussion going again :)
  * Nice catch on the template inheritance problem

 Things that need fixing:
  * You're not setting `user_id` under all circumstances in
 `django/contrib/admin/templatetags/log.py`
  * You can't remove `get_parent()` because the parent template could be
 based on a context variable. It needs to be figured out at render time.

 Other considerations:
  * Probably needs a setting to turn off caching if you don't want it. In
 fact, it probably should be off by default to keep full backwards
 compatibility (introduces the need to reset the server after changing
 templates).

 I was thinking that if people were really worried about out-of-date cached
 templates then there could be some a cache which compares file size or
 date of the file. This would obviously be a slight bit slower and is out
 of scope for an initial cut - just writing down my thoughts :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9201: Page is not available

[Django]

#9201: Page is not available
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Django Web site   |   Version:  1.0   
Resolution:  fixed |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Fixed the link to locmem, inline model admin, and Q class docs on the
 backwards incompatible page.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9201: Page is not available

[Django]

#9201: Page is not available
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  Django Web site   |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 This is not a trac auto-generated link.  It's a link into the old docs.
 Specifically it's a link on the backwards-incompatible page that says "use
 this instead of what you were doing".  It's a bit impolite for such a link
 to go nowhere and isn't going to endear Django to anyone trying to use
 that page to help in their porting efforts.  I'll fix the ones I see right
 in that area, if there are others let us know.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9039: Form validation problem for model with ForeignKey having unique=True, blank=True, null=True

[Django]

#9039: Form validation problem for model with ForeignKey having
unique=True,blank=True,null=True
---+
  Reporter:  nategriswold  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by Alex):

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

Comment:

 Ignore that patch, it doesn't work.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9201: Page is not available

[Django]

#9201: Page is not available
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  closed| Milestone:
 Component:  Django Web site   |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ubernostrum):

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

Comment:

 Trac automatically "helpfully" generates a link for any series of
 capitalized words smooshed together as, for example, in a class name,
 assuming that it's a reference to a wiki page. But since Django's
 documentation isn't on the wiki, many of those end up going nowhere. This
 isn't really a bug.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7048: Support clearing FileFields in the admin if blank=True

[Django]

#7048: Support clearing FileFields in the admin if blank=True
---+
  Reporter:  jarrow| Owner:  jarrow  
Status:  new   | Milestone:  post-1.0
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Comment (by jarrow):

 #6405 is about making MultiValueField pass through initial data. Maybe
 this could be closed if a deletable FileField is the only use case.

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

[Django] #9200: Add a session based form wizard

[Django]

#9200: Add a session based form wizard
--+-
 Reporter:  ddurham   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.formtools  | Version:  SVN   
 Keywords:  session wizard|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 The provided patch adds a class that can be extended to create form
 wizards that:

 1) Use GETs for form displays (except in the case of validation errors)
 and POSTs for form submissions.
 2) Successful POSTs are redirected to GET the next page in the wizard.
 This removes the POST from browser history so that back and refresh pretty
 much just work.

 I have provided plenty of methods that can be overridden for customization
 purposes.  Right now, I think I'm probably storing too much info in the
 session scope, in particular request.POST data, cleaned_data, and other
 things.  I have not tested with multipart form data.  I do not have
 documentation or tests, just wanted to see if you're interested in having
 this in contrib.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7949: Better wording/layout for documentation detail pages on how to get help / submit tickets

[Django]

#7949: Better wording/layout for documentation detail pages on how to get help /
submit tickets
+---
  Reporter:  tyson  | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Django Web site|   Version:  SVN 
Resolution: |  Keywords:  docs irc help ticket
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by tyson):

 * cc: [EMAIL PROTECTED] (added)

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

Re: [Django] #7949: Better wording/layout for documentation detail pages on how to get help / submit tickets

[Django]

#7949: Better wording/layout for documentation detail pages on how to get help /
submit tickets
+---
  Reporter:  tyson  | Owner:  nobody  
Status:  reopened   | Milestone:  
 Component:  Django Web site|   Version:  SVN 
Resolution: |  Keywords:  docs irc help ticket
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by tyson):

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

Comment:

 r8925 did not fix this ticket, it does fix the other tickets mentioned
 (#7271, #7459, #7902, #8271, #8845).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9196: admin display multiple fields on the same line

[Django]

#9196: admin display multiple fields on the same line
---+
  Reporter:  __sam | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 This is Python's curse of the missing trailing comma.  Change your spec
 to:

 {{{
 {'fields': (('public_state','private_state'),)})
 }}}

 and the fields will be printed on the same line.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9198: templatetag include adds new line

[Django]

#9198: templatetag include adds new line
-+--
 Reporter:  versae   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Template system  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 If I have a template
 {{{
 # template1.html
 Line 1
 Line 2
 }}}

 And I include this template in other one using templatetag include:
 {{{
 # template2.html
 {% include template1.html %}
 Line 3
 }}}

 The output must be:
 {{{
 # template2.html
 # template1.html
 Line 1
 Line 2
 Line 3
 }}}

 But the actual output is:
 {{{
 # template2.html
 # template1.html
 Line 1
 Line 2

 Line 3
 }}}

 This behavior is particularly annoying when it renders a template
 including JSON.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9195: Paginator.page() should raise PageNotAnInteger when given a NoneType value

[Django]

#9195: Paginator.page() should raise PageNotAnInteger when given a NoneType 
value
-+--
  Reporter:  [EMAIL PROTECTED] | Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  Uncategorized   |   Version:  1.0 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 I'm not sure this is such a common thing, I think it is more likely that
 programmers have protected against 'page' not being in the search string
 by specifying a sensible default on the get, e.g. `request.GET.get('page',
 1)`.  Technically changing the exception raised would be backwards-
 incompatible (though I doubt anyone has written code that depends on this
 behavior...still, it's impossible to know for sure).  I'd be inclined to
 adjust the doc instead of the code to address this.

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

[Django] #9197: Add new fieldtype (eg. Extra)

[Django]

#9197: Add new fieldtype (eg. Extra)
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 If I need often call QuerySets' .extra it is more convinient to add new
 field type Extra. Ie if I'd like to compute ABS value then instead of
 {{{
 #!python
 Model.object.extra(select={'abs_value':'ABS(value)'})
 }}}
 every time  it would be nice to add to Model new attribute,something like
 this:

 {{{
 #!python
   abs_value = model.Extra('ABS(value)')
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9180: Low-level cache interface incorrectly tries to typecast bytestring

[Django]

#9180: Low-level cache interface incorrectly tries to typecast bytestring
---+
  Reporter:  p | Owner:  nobody
Status:  new   | Milestone:
 Component:  Cache system  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by AdamG):

 See also #5589. I would greatly prefer the `raw` kwarg, as using the
 1-tuple solution would mean that Python pickles are actually being cached,
 which would mean that the cache can only be primed by Python code - and
 when using something like memcached, that's not always the case. For
 example, I often put output from imagemagick into memcached; right now,
 that's innaccessible from `django.core.cache.cache` due to this issue.

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

Re: [Django] #689: Honor Web server provided authentication

[Django]

#689: Honor Web server provided authentication
+---
  Reporter:  [EMAIL PROTECTED]| Owner:  telenieko
Status:  assigned   | Milestone:   
 Component:  Core framework |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)

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

[Django] #9195: Paginator.page() should raise PageNotAnInteger when given a NoneType value

[Django]

#9195: Paginator.page() should raise PageNotAnInteger when given a NoneType 
value
-+--
 Reporter:  [EMAIL PROTECTED]  |   Owner:  nobody
   Status:  new  |   Milestone:  post-1.0  
Component:  Uncategorized| Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The documentation suggests that Paginator.page() raises PageNotAnInteger
 for non-integer values, however passing it None raises a TypeError. I
 would imagine this is a fairly common use case. If a URL optionally has a
 search string that specifies a page number (eg. ?page=3) you would want to
 pass request.GET.get('page') to Paginator.page. However, if the request
 lacks the search string, page() should logically return the
 PageNotAnInteger exception.

 {{{
 >>> from django.core.paginator import Paginator
 >>> objects = ['john', 'paul', 'george', 'ringo']
 >>> p = Paginator(objects, 2)
 >>> p.page(1)
 
 >>> p.page("Pete Best")
 Traceback (most recent call last):
   File "", line 1, in 
   File
 "/home2/ether2/webapps/migration/lib/python2.5/django/core/paginator.py",
 line 37, in page
 number = self.validate_number(number)
   File
 "/home2/ether2/webapps/migration/lib/python2.5/django/core/paginator.py",
 line 25, in validate_number
 raise PageNotAnInteger('That page number is not an integer')
 PageNotAnInteger: That page number is not an integer
 >>> p.page(None)
 Traceback (most recent call last):
   File "", line 1, in 
   File
 "/home2/ether2/webapps/migration/lib/python2.5/django/core/paginator.py",
 line 37, in page
 number = self.validate_number(number)
   File
 "/home2/ether2/webapps/migration/lib/python2.5/django/core/paginator.py",
 line 23, in validate_number
 number = int(number)
 TypeError: int() argument must be a string or a number, not 'NoneType'
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9194: Allow additional hashing algorithms for passwords

[Django]

#9194: Allow additional hashing algorithms for passwords
+---
 Reporter:  dcramer |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Authentication  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 A useful addition to the auth contrib application would be the ability to
 pass in additional hashing algorithms for the password.

 e.g.

 AUTH_PASSWORD_ALGORITHMS = {
 'sha': 'django.contrib.auth.blah.ShaHashThing',
 'md5': '...',
 'myalgo': '...',
 }

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9193: Mac Documentation Issue

[Django]

#9193: Mac Documentation Issue
---+
 Reporter:  jlev   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The advice to set DYLD_LIBRARY_PATH=/opt/local/lib on Mac OS X is really
 bad. Because MacPorts has several old and incompatible versions of widely
 used libraries (libJPEG, libTIFF, and others), setting this in the
 bash_profile can make all sorts of applications crash. If the library path
 needs to be set, do it before application start, but not system wide.

 http://discussions.apple.com/thread.jspa?threadID=1108472

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---