date:20081001

[Django] #9268: Pass custom form values from post-comment to preview-comment

2008-10-01 Thread Django

#9268: Pass custom form values from post-comment to preview-comment
-+--
 Reporter:  taojian  |   Owner:  nobody
   Status:  new  |   Milestone:  post-1.0  
Component:  django.contrib.comments  | Version:  SVN   
 Keywords:  comment preview  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 It's possible to add custom fields to the comment post form (to provide a
 'next' value, or other custom values), but if the user opts to preview
 their comment, those custom values are lost. Currently the only context
 variables being passed to the preview view are the text of the comment and
 the values from the cleaned form (which don't include custom values).
 There may be negative implications I'm not aware of, but couldn't we just
 pass the 'data' variable (containing all the un-cleaned POST data) into
 the preview?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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

2008-10-01 Thread 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):

 Good job on the fixes, msaelices. I'll do another review some time soon.
 Do you visit #django at all? If so, a chat on there might flesh out some
 of the discussions more quickly (or google chat [EMAIL PROTECTED])

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9199: Common middleware PREPEND_WWW broken

2008-10-01 Thread Django

#9199: Common middleware PREPEND_WWW broken
-+--
  Reporter:  gonz| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  1 
Needs_better_patch:  0   |  
-+--
Changes (by gonz):

 * cc: gonz (added)
  * needs_better_patch:  1 => 0
  * needs_tests:  0 => 1

Comment:

 Thank you Malcom, now the problem it's much clear.

 I think we should just move the last resolve. Chris is right and It only
 makes sense to try that resolve if we are adding a trailing slash. I'm
 attaching a new patch.

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

Re: [Django] #8571: comment framework throws obscure exception in {% comment_form_target %}

2008-10-01 Thread Django

#8571: comment framework throws obscure exception in {% comment_form_target %}
--+-
  Reporter:  [EMAIL PROTECTED] | Owner:  nobody 
 
Status:  closed   | Milestone:  post-1.0

 Component:  django.contrib.comments  |   Version:  1.0 

Resolution:  worksforme   |  Keywords:  comment, 
comment_form_target
 Stage:  Unreviewed   | Has_patch:  0   

Needs_docs:  0|   Needs_tests:  0   

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

 After a long absence, this error has reemerged. It alternates between
 "Reverse..." and "No module named urls." This is what I am getting
 currently:

 {{{
 Environment:

 Request Method: GET
 Request URL: http://cmdb-test/helpdesk/68/
 Django Version: 1.1 pre-alpha SVN-9109
 Python Version: 2.4.3
 Installed Applications:
 ['django.contrib.auth',
  'django.contrib.contenttypes',
  'django.contrib.sessions',
  'django.contrib.sites',
  'django.contrib.admin',
  'django.contrib.admindocs',
  'django.contrib.comments',
  'cmdb.main',
  'cmdb.docs',
  'cmdb.cicada',
  'cmdb.helpdesk',
  'cmdb.inventory',
  'cmdb.conf_eval',
  'cmdb.kudos']
 Installed Middleware:
 ('django.middleware.common.CommonMiddleware',
  'django.contrib.sessions.middleware.SessionMiddleware',
  'django.contrib.auth.middleware.AuthenticationMiddleware',
  'django.middleware.doc.XViewMiddleware')


 Template error:
 In template /home/web/cmdb/templates/comments/form.html, error at line 4
Caught an exception while rendering: Reverse for '' with arguments '()' and keyword arguments
 '{}' not found.
1 : Post a comment


2 : {% load comments %}


3 : {% get_comment_form for object as form %}


4 : 


5 : {# built-in hidden spam fields #}


6 : {% for field in form %}


7 :   {% if field.is_hidden %}{{ field }}{% endif %}


8 : {% endfor %}


9 :


10 : {# --- custom fields -- #}


11 : {# hidden 'honeypot' field #}


12 : {{ form.honeypot }}


13 :


14 : {# if user is not logged in, show name and e-mail fields #}


 Traceback:
 File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in
 get_response
   86. response = callback(request, *callback_args,
 **callback_kwargs)
 File "/home/web/cmdb/helpdesk/views.py" in issue_detail
   410. template_name = 'helpdesk/detail.html',
 File "/usr/lib/python2.4/site-
 packages/django/views/generic/list_detail.py" in object_detail
   143. response = HttpResponse(t.render(c), mimetype=mimetype)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   176. return self.nodelist.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   768. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
 render_node
   71. result = node.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/loader_tags.py" in
 render
   97. return compiled_parent.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   176. return self.nodelist.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   768. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
 render_node
   71. result = node.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/loader_tags.py" in
 render
   97. return compiled_parent.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   176. return self.nodelist.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   768. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
 render_node
   71. result = node.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/loader_tags.py" in
 render
   24. result = self.nodelist.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
 render
   768. bits.append(self.render_node(node, context))
 File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
 render_node
   71. result = node.render(context)
 File "/usr/lib/python2.4/site-packages/django/template/loader_tags.py" in
 render
   111. return self.template.render(context)
 File

[Django] #9267: Admin media setup should be referenced from the contrib admin docs.

2008-10-01 Thread Django

#9267: Admin media setup should be referenced from the contrib admin docs.
---+
 Reporter:  SmileyChris|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 While the admin media set up is explained in the webserver setup document,
 it would be nice to have a crosslink from the contrib.admin page. This is
 a very FAQ on IRC.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9038: url tag not working with reverse in 1.0 as it previously did

2008-10-01 Thread Django

#9038: url tag not working with reverse in 1.0 as it previously did
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  mtredinnick 
Status:  closed   | Milestone:  
 Component:  Core framework   |   Version:  1.0 
Resolution:  fixed|  Keywords:  url, reverse
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by kmtracey):

 You are not seeing exactly the same problem, since your exception involves
 no arguments and the initial report had an argument.  Also you haven't
 provided enough information to help figure out what is going wrong, since
 the exception alone without some information on your url patterns is not
 very helpful.  Finally, this is not the right place to figure out what is
 going wrong -- as Malcolm said the error in this ticket, which was very
 specific and not something that covers all "!NoReverseMatch" errors -- has
 been fixed.  The best way to figure out what is going on in your case is
 probably to post on django-users with enough information about your url
 patters and what you are doing to generate the exception to hopefully
 identify if the problem is in your setup or the Django code. If Django
 code, then a new ticket would be appropriate.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9266: Update simplejson to 2.0.1

2008-10-01 Thread Django

#9266: Update simplejson to 2.0.1
---+
 Reporter:  msaelices  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Serialization  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Simplejson library in version 2.0.1 include severals optimizations that
 multiplies encoding/decoding speed. This is
 [http://bob.pythonmac.org/archives/2008/09/29/simplejson-201/ the
 announcement].

 In author words:
 {{{
 Even without the C speedups, it's several times faster. With the C
 speedups, it's WAY faster. I highly recommend that everyone update their
 frameworks to use the latest code.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #6510: get_nodes_by_type refactor for easier extensibility (fixes an underlying bug for IfEqualNode)

2008-10-01 Thread Django

#6510: get_nodes_by_type refactor for easier extensibility (fixes an underlying
bug for IfEqualNode)
-+--
  Reporter:  [EMAIL PROTECTED] | Owner:  SmileyChris   
Status:  assigned| Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:  block ifequals
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by SmileyChris):

  * owner:  nobody => SmileyChris
  * status:  new => assigned
  * summary:  Block inheritance doesn't work within {% ifequal %} tags =>
  get_nodes_by_type refactor for easier
  extensibility (fixes an underlying bug for
  IfEqualNode)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9038: url tag not working with reverse in 1.0 as it previously did

2008-10-01 Thread Django

#9038: url tag not working with reverse in 1.0 as it previously did
--+-
  Reporter:  [EMAIL PROTECTED]  | Owner:  mtredinnick 
Status:  closed   | Milestone:  
 Component:  Core framework   |   Version:  1.0 
Resolution:  fixed|  Keywords:  url, reverse
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by abhi):

 Sorry.. I wanted to mean revision 9087. Even with revision 9087 I see the
 same exception:

 TemplateSyntaxError at /customize/themeeditor/themeoftheday/

 Caught an exception while rendering: Reverse for 'navburner.theme_editor'
 with arguments '()' and keyword arguments '{}' not found.

 Original Traceback (most recent call last):
   File "C:\workspaces\navburner-02\django-
 latest\django\template\debug.py", line 71, in render_node
 result = node.render(context)
   File "C:\workspaces\navburner-02\django-
 latest\django\template\defaulttags.py", line 378, in render
 args=args, kwargs=kwargs)
   File "C:\workspaces\navburner-02\django-
 latest\django\core\urlresolvers.py", line 254, in reverse
 *args, **kwargs)))
   File "C:\workspaces\navburner-02\django-
 latest\django\core\urlresolvers.py", line 243, in reverse
 "arguments '%s' not found." % (lookup_view, args, kwargs))
 NoReverseMatch: Reverse for 'navburner.theme_editor' with arguments '()'
 and keyword arguments '{}' not found.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9246: root documentation url changed

2008-10-01 Thread Django

#9246: root documentation url changed
--+-
  Reporter:  SmileyChris  | Owner:  nobody
Status:  new  | Milestone:
 Component:  Django Web site  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by julien):

  * component:  Documentation => Django Web site

Comment:

 #9250, #9251 and #9265 were dupes.

 I think the reason why this has been reported multiple times is because it
 was in the wrong component.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #6510: Block inheritance doesn't work within {% ifequal %} tags

2008-10-01 Thread Django

#6510: Block inheritance doesn't work within {% ifequal %} tags
-+--
  Reporter:  [EMAIL PROTECTED] | Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:  block ifequals
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by SmileyChris):

 PS: I just updated the patch to latest trunk.

 And to anyone reviewing this ticket - note that the ticket description is
 a red herring. This is a valid bug even without a repeated `{% block %}`
 tag

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9002: Easy way to create mock Request objects for testing views

2008-10-01 Thread Django

#9002: Easy way to create mock Request objects for testing views
+---
  Reporter:  simon  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Testing framework  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by zellyn):

 ps. it appears I accidentally messed with the needs_better_patch,
 needs_tests, and needs_docs settings - how do I tell what they were
 originally?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9002: Easy way to create mock Request objects for testing views

2008-10-01 Thread Django

#9002: Easy way to create mock Request objects for testing views
+---
  Reporter:  simon  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Testing framework  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by zellyn):

 After more experimentation it appears that a more complicated refactoring
 is necessary if this is to work with sessions, etc. The request middleware
 needs to run.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9076: Inline forms can result in a "Please correct the errors below." message with no errors listed.

2008-10-01 Thread Django

#9076: Inline forms can result in a "Please correct the errors below." message
with no errors listed.
-+--
  Reporter:  coady   | Owner:  nobody
Status:  reopened| 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 kmishler):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 We had this problem too and fixed it by adding ordering to the model.  Of
 course it only happened in production, and not in our development or test
 environments.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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

2008-10-01 Thread 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 msaelices):

 @mtredinnick, @SmileyChris, This is my honest opinion: I think that
 optimizations in #6262 are overdesign. I think using Django cache system
 is too hard only for caching compiled templates because:
  * It's simpler use a simple global dictionary, like urlresolvers does
 (done exactly in [5516]). Common sense said me that a simple solution win
 over complex one.
  * It's faster that all kinds of cache. memcached can be very fast
 compared with a complex SQL in a remote database, locmem can be fast also,
 but you will share this with a bunch of cache keys. Database and
 filesystem cache can be hundreds of times slower. Also it seems that in
 #6262 even with memcached there is no performance improvements.
  * Cache system needs templates can be pickable, why you have to add a
 requirement not needed at all?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8122: Better way of testing for cookies

2008-10-01 Thread Django

#8122: Better way of testing for cookies
--+-
  Reporter:  jcassee  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.sessions  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by jcassee):

 I agree that the difference between the session key being {{{None}}} and
 being {{{""}}} is a subtle one, yet it is a useful distinction here. I
 wrote tests precisely to check whether I did the tests right!

 The tests were written before I noticed how other middleware was tested. I
 agree that changing it to just calling the middleware directly would be
 nice.

 I will post a message about this ticket on django-dev, as you suggested.
 Thanks for looking at 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8122: Better way of testing for cookies

2008-10-01 Thread Django

#8122: Better way of testing for cookies
--+-
  Reporter:  jcassee  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.sessions  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Ah, I understand now - I was just a bit worried that it would be picking
 up that the key wasn't `None` and doing something with it. After a closer
 look at the session innards I see this isn't the case.

 This ticket looks good - why don't you raise it on the django-dev group?

 Of minor importance - the Django test client isn't really necessary here
 is it? (it's a lot slower than the testcase one) and wouldn't it be better
 to use the proper testcase assertions rather than just `assert` (but I'm
 not sure if it really matters)?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9263: Missing bold lines in Tutorial #2

2008-10-01 Thread Django

#9263: Missing bold lines in Tutorial #2
+---
  Reporter:  a2 | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  worksforme |  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:  => worksforme
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I don't have the exact combination you do, but they're bold for me on
 Firefox 2.0.0.17 on Ubuntu and Firefox 3.03 on Windows.  Do a View->Page
 Source and you should see three lines enclosed in :

 {{{
 # Uncomment the next two lines to enable the admin:
 from django.contrib import admin
 admin.autodiscover()

 urlpatterns = patterns('',
 # Example:
 # (r'^mysite/', include('mysite.foo.urls')),

 # Uncomment the admin/doc line below and add
 'django.contrib.admindocs'
 # to INSTALLED_APPS to enable admin documentation:
 # (r'^admin/doc/', include('django.contrib.admindocs.urls')),

 # Uncomment the next line to enable the admin:
 (r'^admin/(.*)', admin.site.root),
 )
 }}}

 Perhaps you've got an override for what  does in your
 userChrome.css 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] #9265: double slashes in docs home url

2008-10-01 Thread Django

#9265: double slashes in docs home url
--+-
  Reporter:  dvainsencher | Owner:  nobody
Status:  closed   | Milestone:
 Component:  Django Web site  |   Version:  1.0   
Resolution:  duplicate|  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:  => duplicate
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 This has been reported multiple times and is being worked on. In the
 future, please search for existing tickets before filing a new one.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9265: double slashes in docs home url

2008-10-01 Thread Django

#9265: double slashes in docs home url
-+--
 Reporter:  dvainsencher |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Django Web site  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 this url shows a 404 error:
 http://docs.djangoproject.com/en/dev/

 but this don't:
 http://docs.djangoproject.com/en/dev//

 The documentation link in home is redirecting to the second one.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9002: Easy way to create mock Request objects for testing views

2008-10-01 Thread Django

#9002: Easy way to create mock Request objects for testing views
+---
  Reporter:  simon  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Testing framework  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by zellyn):

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

Comment:

 I'd suggest creating new methods (preferably on the existing Client class
 - it's just a refactoring of the initial code from the existing methods),
 so that it would be easy to intermix use of the normal get() and post()
 methods and the new variations while sharing the same session data.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #8122: Better way of testing for cookies

2008-10-01 Thread Django

#8122: Better way of testing for cookies
--+-
  Reporter:  jcassee  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.sessions  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by jcassee):

 The idea is that every session has a session cookie so that you avoid the
 need to call {{{set_test_cookie()}}} (which sets the cookie by added to
 the session). The session cookie is empty if the session is not yet
 modified to avoid a call to the session backend.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8122: Better way of testing for cookies

2008-10-01 Thread Django

#8122: Better way of testing for cookies
--+-
  Reporter:  jcassee  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django.contrib.sessions  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Design decision needed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Why the change in behaviour to set an initial session cookie for an
 unmodified session (if it wasn't found)?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9256: Let the template parser remember it's root nodelist

2008-10-01 Thread Django

#9256: Let the template parser remember it's root nodelist
--+-
  Reporter:  SmileyChris  | Owner:  SmileyChris
Status:  assigned | Milestone: 
 Component:  Template system  |   Version:  1.0
Resolution:   |  Keywords: 
 Stage:  Unreviewed   | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * owner:  nobody => SmileyChris
  * needs_better_patch:  => 0
  * status:  new => assigned
  * 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

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

2008-10-01 Thread Django

#7770: HttpResponse.set_cookie should accept expires=datetime
+---
  Reporter:  jdunck | Owner:  SmileyChris
Status:  assigned   | 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):

  * owner:  nobody => SmileyChris
  * 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9076: Inline forms can result in a "Please correct the errors below." message with no errors listed.

2008-10-01 Thread Django

#9076: Inline forms can result in a "Please correct the errors below." message
with no errors listed.
-+--
  Reporter:  coady   | Owner:  nobody
Status:  reopened| 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 jashugan):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 I had this issue as well. As bthomas pointed out, adding some type of
 ordering to the model makes it 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] #7270: selected_related() can not follow reverse relations of OneToOne.

2008-10-01 Thread Django

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  [EMAIL PROTECTED]  | Owner:  gav   
 
Status:  new   | Milestone:  post-1.0   

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

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

 How would I go about making the patch use LEFT JOIN (or LEFT OUTER JOIN)
 instead of INNER JOIN?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9262: Memory leak in django.utils.version.get_svn_revision

2008-10-01 Thread Django

#9262: Memory leak in django.utils.version.get_svn_revision
---+
 Reporter:  semenov|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 django.utils.version.get_svn_revision suffers from a memory leak: it opens
 a file without closing it. I'm attaching the trivial patch.

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

[Django] #9261: http://www.djangoproject.com/download/ needs updating

2008-10-01 Thread Django

#9261: http://www.djangoproject.com/download/ needs updating
-+--
 Reporter:  kmtracey |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Django Web site  | Version:  1.0   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 This page lists 2 options (latest official or latest development -- trunk)
 for downloading.  I think the latest micro-release branch should be
 mentioned as an option -- it should provide bug fixes with less risk of
 instability due to new features coming in.

 Also under "Which version is better?" it still says backwards-incompatible
 changes may be made in latest development.  That should not be the case
 until 2.0 is on the horizon, right?  Currently as trunk is working on 1.1
 there should be no backwards-incompatible changes made even on trunk.

 Finally, only 0.96 is listed as a previous supported release, whereas I
 thought "current and two previous" mentioned in contributing doc would
 mean 0.95 would still be eligible for security fixes.  The last security
 fix, just prior to 1.0 going out, had fixes made to trunk, 0.96, 0.95, and
 0.91.  Shouldn't only 0.91 have gotten bumped down to "unsupported" when
 1.0 went out?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #6510: Block inheritance doesn't work within {% ifequal %} tags

2008-10-01 Thread Django

#6510: Block inheritance doesn't work within {% ifequal %} tags
-+--
  Reporter:  [EMAIL PROTECTED] | Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:  block ifequals
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Hystrix):

 * cc: [EMAIL PROTECTED] (added)

Comment:

 I've just been biten by this bug and I have to say it took me more than a
 day to find out why the child template didn't show up on the parent. If it
 won't be resolved at least it should be noted on the docs that you can't
 expect block tags to work inside ifequal.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

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

2008-10-01 Thread noreply


Author: kmtracey
Date: 2008-10-01 12:26:40 -0500 (Wed, 01 Oct 2008)
New Revision: 9109

Modified:
   django/branches/releases/1.0.X/setup.py
Log:
Fixed #9260: [1.0.X] Correct version calculation code so setup.py works on 
1.0.X branch.  Thanks for the report Warren.


Modified: django/branches/releases/1.0.X/setup.py
===
--- django/branches/releases/1.0.X/setup.py 2008-10-01 01:23:55 UTC (rev 
9108)
+++ django/branches/releases/1.0.X/setup.py 2008-10-01 17:26:40 UTC (rev 
9109)
@@ -66,7 +66,7 @@
 file_info[0] = '\\PURELIB\\%s' % file_info[0]
 
 # Dynamically calculate the version based on django.VERSION.
-version_tuple = __import__('django').get_version()
+version = __import__('django').get_version()
 if u'SVN' in version:
 version = ' '.join(version.split(' ')[:-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 [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

2008-10-01 Thread 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 hinnerk):

 * 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

2008-10-01 Thread 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:  0 
Needs_better_patch:  1 |  
---+
Changes (by [EMAIL PROTECTED]):

 * 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] #9260: Changeset 9108 breaks setup.py in 1.0.x branch

2008-10-01 Thread Django

#9260: Changeset 9108 breaks setup.py in 1.0.x branch
---+
 Reporter:  [EMAIL PROTECTED]  |   Owner:  nobody
   Status:  new|   Milestone:  post-1.0  
Component:  Uncategorized  | Version:  1.0   
 Keywords:  setup  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 It appears that the changes in [9107] were not cleanly applied to the
 1.0.x branch in [9108].

 Specifically, the assignment to "version_tuple" instead of "version" at
 line 69 causes "NameError: name 'version' is not defined" at line 70.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #6045: Many2Many manager and “TypeError: filter() keywords must be strings”

2008-10-01 Thread Django

#6045: Many2Many manager and “TypeError: filter() keywords must be strings”
---+
  Reporter:  proxor| Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.0
  
Resolution:|  Keywords:  many2many, 
related, unicode easy-pickings
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * has_patch:  0 => 1
  * needs_tests:  0 => 1

Comment:

 State of the ticket is still new, never fixed, so yes it's quite likely
 this problem still exists.  Restoring prior flags since I don't see any
 reason they were deleted.  The ticket has a patch but no test -- a test
 (one that fails with current code and passes with the fix) would be useful
 in moving this ticket along in the process, if anyone encountering this
 problem would care to provide one.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8733: filesizeformat filter units unclear

2008-10-01 Thread Django

#8733: filesizeformat filter units unclear
-+--
  Reporter:  akaihola| Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  Template system |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by Daniel Pope <[EMAIL PROTECTED]>):

 @Semmel: The SI version is the decimal scale. IEC is the binary scale.

 It's not "plain" wrong to display the binary scale with the decimal units:
 Windows does this and it's Wikipedia policy too. Wikipedia editors
 reckoned that it was more important to be understood by the ignorant than
 to be unambiguous.

 However, the correct format for file sizes is the SI scale. Only
 addressable space should be measured with the IEC scale. You have modified
 the file size function in exactly the wrong way for formatting file sizes:
 it is neither correct nor has historical precedent.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #6045: Many2Many manager and “TypeError: filter() keywords must be strings”

2008-10-01 Thread Django

#6045: Many2Many manager and “TypeError: filter() keywords must be strings”
---+
  Reporter:  proxor| Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  Database layer (models, ORM)  |   Version:  1.0
  
Resolution:|  Keywords:  many2many, 
related, unicode easy-pickings
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by joaoolavo):

  * needs_better_patch:  1 => 0
  * has_patch:  1 => 0
  * version:  SVN => 1.0
  * needs_tests:  1 => 0

Comment:

 This same problem stills happening in version 1.0. If I use an Unicode
 string in the parameter "related_name" in ManyToManyField, I got the prior
 error.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8127: CSRF + AJAX

2008-10-01 Thread Django

#8127: CSRF + AJAX
-+--
  Reporter:  xlax| Owner:  nobody   
Status:  new | Milestone:   
 Component:  Contrib apps|   Version:  SVN  
Resolution:  |  Keywords:  CSRF AJAX
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  1
Needs_better_patch:  0   |  
-+--
Changes (by carljm):

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

2008-10-01 Thread Django

#3566: Proposal: ORM aggregation support
+---
  Reporter:  Honza Král <[EMAIL PROTECTED]>  | Owner:  russellm 
   
Status:  assigned   | Milestone:
  
 Component:  Database layer (models, ORM)   |   Version:  SVN   
  
Resolution: |  Keywords:  orm 
aggregation group by
 Stage:  Someday/Maybe  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  1 
  
Needs_better_patch:  1  |  
+---
Comment (by anonymous):

 Possibility of creating a supported branch of this to test?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8733: filesizeformat filter units unclear

2008-10-01 Thread Django

#8733: filesizeformat filter units unclear
-+--
  Reporter:  akaihola| Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  Template system |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by Semmel):

 I've added a little patch that fixes the behaviour. It also makes the
 function more readable.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #8733: filesizeformat filter units unclear

2008-10-01 Thread Django

#8733: filesizeformat filter units unclear
-+--
  Reporter:  akaihola| Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  Template system |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by Semmel):

 It should display the SI version of the value - anything other is just
 plain wrong (and shouldn't be used since years). The name
 {{{filesizeformat}}} is okay for me - but maybe another version of
 {{{filesizeformat}}} displaying the binary representation would be a great
 idea.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9257: Incorrect description of urls.py contents

2008-10-01 Thread Django

#9257: Incorrect description of urls.py contents
+---
  Reporter:  a2 | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution: |  Keywords:  urls.py
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  1  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by badri):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * version:  1.0 => SVN
  * needs_docs:  => 1
  * has_patch:  1 => 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9199: Common middleware PREPEND_WWW broken

2008-10-01 Thread Django

#9199: Common middleware PREPEND_WWW broken
-+--
  Reporter:  gonz| Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Comment (by SmileyChris):

 Oops, I brushed over the details and put my foot in it. Malcolm's right
 that this isn't the correct fix - but the issue is definitely around this
 line.

 The whole logic being used here is a bit messed up. That resolve depends
 on needing a slash to be entered - it could just be a www change which is
 needed.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #9258: Admin ForeignKeyRawIdWidget uses wrong manager for label lookup

2008-10-01 Thread Django

#9258: Admin ForeignKeyRawIdWidget uses wrong manager for label lookup
+---
  Reporter:  nullie | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by brosner):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #9258: Admin ForeignKeyRawIdWidget uses wrong manager for label lookup

2008-10-01 Thread Django

#9258: Admin ForeignKeyRawIdWidget uses wrong manager for label lookup
---+
 Reporter:  nullie |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 It results in exception when trying to edit object which has overriden
 objects managers.

 Here's the patch:

 {{{
 --- django.orig/contrib/admin/widgets.py2008-09-04
 03:16:05.0 +0600
 +++ django/contrib/admin/widgets.py 2008-10-01 12:32:18.0
 +0600
 @@ -146,7 +146,7 @@

  def label_for_value(self, value):
  key = self.rel.get_related_field().name
 -obj = self.rel.to.objects.get(**{key: value})
 +obj = self.rel.to._default_manager.get(**{key: value})
  return '%s' % truncate_words(obj, 14)

  class ManyToManyRawIdWidget(ForeignKeyRawIdWidget):
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

45 matches

Mail list logo